Hello
After upgrading to 1.20B I’m experiencing some problems with tempo sync. When the A4 is slaved to Ableton (or to the Rytm), when transport starts I can see in the display (and hear) a 6 bpm “jump” in the A4. It’s just a moment and after that it gets to the right bpm again, but everytime I start the sequencer the A4 does this.
Anyone with the same problem? Could it be a bug in the new OS?
Thanks in advance!
…sounds like the start command searches its way through your midi-setup 
Do you use the ‘naked’ A4-USB-midi or the OB-plugin?
i see the same tempo blip when running a very direct setup using OB with a simple midi start command - the tempo consistently but momentarily registers 124, then sits nicely at 120 - this was discussed in the first public beta iirc
I use the “naked” usb connection, without overbridge. No more machines connected, just A4.
And it does the same if I connect the Rytm as master and the A4 as slave with a midi cable.
sounds like a bug…
damn theres quite a few…
how do sync Live? which interface do you use? wich OS?
This problem occurs when a computer is involved, A4+AR run perfectly snyced over midi i/o. I guess the latency of the midi-start command is responsible for that, running from Live, through the OS, through the interface and the cable.
your guess is not based on good theory
latency wont cause tempo to change, this is a midi clock issue of some sort
and according to the OP, the issue occurs with a standard MIDI cable from AR to A4… is this correct? replicating the issue is pretty key to troubleshooting it
ok, call it ‘time the midi signal needs’ instead of latency - a common well known issue
a little bitt of theory, here: midi clock signal:
Same problem here. My Ak clock jumps with latest ob firmware, when connected via usb, clocked by ableton. In ob mode the clock is 100% spot on.
…
sorry, you’re clueless
I think this is not Ableton related. Before installing the last firmware in A4 transport sync with Ableton and 4 was right, not clock jumps.
And in a configuration without computer, Analog Rytm as master and A4 as slave, connected via midi cable, there is the same clock jump.
It seemed to me that it didn’t happened when trying sync with overbridge opened, but I could try it only once, soo little time lately to play with the machines:-(
this is happening to me also.
the ONLY thing that has changed in my setup is the A4 OS.
Therefore, I’d think it’s safe to conclude that it’s the A4’s fault, a not Ableton / Logic.
Thanks Elektron !
Hello,
I’ve seen the same problem yesterday, using A4 sync via usb to my MPC software (mpc renaissance), A4 used as audio interface (no OB)
I found the sync OK after re-adressing sync command in the daw.
I suppose it’s a bug of the latest firmware, cause everything worked fine before.
Hope this will be fixed soon !
Yep, it’s a bug. We’re on it!
1 Like
bug in beta ! gosh, dark days in the first world
This has been a bug that I’ve encountered with the A4 for a long time. It can be heard especially if you’re using delays since the tempo shift throws the delay pitch noticeably out.
The best solution is to have the a4 receive transport start / stop but not tempo. Then set the tempo manually.
You think this a helpful attitude?
[quote=““invisible acropolis””]
[quote=“avantronica”]bug in beta ! gosh, dark days in the first world
[/quote]
You think this a helpful attitude?[/quote]
Ahh my bad, thought you said bass bin !!!
[quote=““invisible acropolis””]
[quote=“avantronica”]bug in beta ! gosh, dark days in the first world
[/quote]
You think this a helpful attitude?[/quote]
i do if it helps stop the negative nonsense