Yeah there are a bunch of posts about it (happens on A4 too), some of us have tickets in and bug confirmed by support. Awaiting (likely post Digitakt release) fix. Super annoying. 
2 Likes
annoying indeed… yeah suppose this won’t get priority-fixed lol… sent in another report, can’t hurt…
2 Likes
My chain of tickets went like this Sent in report, confirmed bug, offered fix soon, fix delayed, told to roll back OS, :crickets:
1 Like
ah ok - do you happen to know which version was the last one where it worked…? if it’s not too old, might try and roll back… but also need the old OB version then… guess Rytm OS 1.30D and OB 1.1.0 would be worth a try?
Yup, and that screws OB on OSX to some degree, also LFO bugs.
2 Likes
Edit: )topic merge confusion)… I only rolled back my A4 though (same issue) since I have too many Rytm sounds that would get mangled by the LFO bugs in 1.30D.
1 Like
hmmmm yea… not optimal!
but personally, could live with that for now…
just wanna experiment with a thing, but need working sync and audio from rytm…
if anyone has the filez for Rytm OS 1.30D and OB 1.1.0 for Mac, pls share! thx
Support provided me with an attachment on my ticket, ask them I guess. I don’t want to upload it elsewhere in case it has other more serious bugs 
Good luck during Superbooth though 
2 Likes
will do! but yeah, Simon is here in Berlin rn lol. will press the issue tonight.
2 Likes
Buy him a beer first!
2 Likes
Just wondering if this ever got fixed, I’m having some trouble syncing my rytm to ableton live.
Hello,
I really love my AR, simply the best sequencer on a drum machine I ever used. Incorporating the AR into my workflow completely changed my way of programming drums, but there is a “but”:
I’ve been working (should I say struggling) hard on making the sync with Ableton (being master) work fine but I am still not completely satisfied by the situation I have. I send the sync signal over MIDI (not USB) and use the OS1.30 (No OverBridge). It is fine in the studio but it is simply not acceptable to face the bugs I had no later than yesterday on stage: To summarize the different bugs to which I’ve been exposed (over the last months):
- Loss of sync on tricky pattern changes (in particular when the machine is stopped and a different pattern change is sent right when starting again) (I found a work around for this one)
- Seqencer Stops with no identified reason…wouaouhh
- Interface frozen (pads, buttons…), not reproducible, audio is still output
Of course, the last two occur very sparingly, but it is already too much, specially on stage. (I let you imagine how I freak before each gig due to these technical non musical issues) ==> I seriously (sadly) think of an alternate solution, unless someone having experimented the same issues finally solved everything to make this installation definitely stable.
Looking forward to hearing your thoughts about this.
Thanks.
Hello everyone,
just to say that the usb MIDI sync on my AR is screwed aswell with the new OS 1.31b upgrade. Same problem with regular midi sync. This is quiet annoying… I can’t use the machine in conjunction with any other software/hardware device 
I’ll post another ticket. Hope they will fix this pretty quick !
Seriously five month, come on do something
3 Likes
Looks like there’s no interest for anyone to even respond to this. Right now the only way I can get usb midi to work is if I’m not using overbridge as an input to my daw. I doubt there’s no room on the USB bus for midi and at least the L/R outs.
It’s been a while since I have not updated my black boxes, I have done well to come here before.
List of changes from OS 1.30D to 1.31 Changes
The lowest required Overbridge Software Suite version is now 1.15.0. Should you want to keep support for Overbridge 1.10.x, you must stay on OS 1.30D.
*> The unit will no longer react to MIDI transport (or MIDI clock) when synced via the Overbridge plugin. The old behavior was confusing to many users and didn’t work well with certain DAWs.
Lol I just sold my USAMO after realising I could clock the Rytm accurately from Overbridge. This worked fine when I was on 1.20D. Very confusing!
Close to one year later and this issue is still not solved. I sent a support ticket last year but the best answer they could give was to downgrade the firmware. (Which I have bad experience with since my projects were altered in the new firmware)
Did anyone else make a support ticket about the missing midi clock over USB and what was response?
Just curious if there is any time to expect a fix or start reprogramming my whole set.
Can anyone confirm this post below? I’d like to upgrade to 1.31 but I find the statement in the release notes confusing.
The unit will no longer react to MIDI transport (or MIDI clock) when synced via the Overbridge plugin. The old behavior was confusing to many users and didn’t work well with certain DAWs.
My units currently sync via OB. I have another device connected via the RYTM MIDI Out.
Everything currently starts/stops in sync with the transport on my computer (Ableton). Will that change if I upgrade?
That would be a blocker!
Thanks
To answer my owner question, it still works as I expect post upgrade.