CheapEdge
Member
This could be a bug, and it's centrainly a whish for a change, the sooner the better .
I get the impression that the Axe 3 randomly syncs it's tempo to either the rising or the falling edge of a midi tempo signal, both if you use a CC for it and if you use a MIDI clock signal.
Normally that would not be a problem, as long as the tempo is correct everything is fine.
But if you want the LFO-phase to be correct it's definitely a problem, because every time the Axe syncs differently you have to adjust the LFO1B phase knob on and on and on. Not very nice ...
Never had this problem with the Axe 2, so my impression is that something has changed here in the Axe 3, and although I am generally very very happy with Axe 3, this one is not a change for the better I'm afraid.
I'm sending either a midi-pulse (CC-command) or a MIDI clock signal from a BT in Ableton Live 9.
I have tested with both options that the Axe follows tempo changes in Ableton perfectly, so I'm sure it's "connected". However sometimes on the rising edge and sometimes on the falling edge.
Just to make sure: can this be reproduced in the development center of FA? Is there perhaps some setting that I have'nt found yet, and that could adjust for this?
Using AxeFX 3 with FW Ares 2.02, Ableton LIVE 9 and Windows 10.
Hope to hear from you.
Keep the good works goin'!
I get the impression that the Axe 3 randomly syncs it's tempo to either the rising or the falling edge of a midi tempo signal, both if you use a CC for it and if you use a MIDI clock signal.
Normally that would not be a problem, as long as the tempo is correct everything is fine.
But if you want the LFO-phase to be correct it's definitely a problem, because every time the Axe syncs differently you have to adjust the LFO1B phase knob on and on and on. Not very nice ...
Never had this problem with the Axe 2, so my impression is that something has changed here in the Axe 3, and although I am generally very very happy with Axe 3, this one is not a change for the better I'm afraid.
I'm sending either a midi-pulse (CC-command) or a MIDI clock signal from a BT in Ableton Live 9.
I have tested with both options that the Axe follows tempo changes in Ableton perfectly, so I'm sure it's "connected". However sometimes on the rising edge and sometimes on the falling edge.
Just to make sure: can this be reproduced in the development center of FA? Is there perhaps some setting that I have'nt found yet, and that could adjust for this?
Using AxeFX 3 with FW Ares 2.02, Ableton LIVE 9 and Windows 10.
Hope to hear from you.
Keep the good works goin'!