I have finally downloaded OB for the DTII and oh my, it’s stunning! 16 stereo audio tracks all piped into Ableton Live with a single USB cable. I’m not an expert but I can only imagine how tough this was to code, not least with all the different versions of the plugin and with the Mac/Windows versions. And for no extra cost!
I’ve got it all set up in my Ableton Live template now and I still can’t quite believe it’s real!
Hi! Search on youtube for „flstudio patcher midi cc“.
I can’t help more on this, but this is the direction.
Using my Rytm mki1 in parallel it’s also nice that with the newer model(s) I don’t need to worry as much about syncing with OB.
The Rytm was my first experience with Overbridge - could not believe an analogue synth could be used like a plugin. Still amazed by how well it works. 
When I copy a track instrument with Track+Track number+Copy and paste it to another track, the track level doesn’t get copies.
Is that intentional? I would prefer if it would copy the level as well, when I am reorganising my tracks.
Was that always the copy behaviour on the old DT as well?
Edit: would be great if there was a track swap function, which would swap track and sequencer content in one go…
Any latency?
As always. 
I haven’t adjusted Live to compensate though, I just recorded long stems in Arranger view and cut an equal amount off the beginning of each clip.
the new operating system crashes. my user scenario is as follows:
digitakt 2 acting as MIDI controller + sequencer / daw is used as sound module
digitakt is in overbridge mode / daw: reaper / realearn is used for parameter feedback for the CC knobs
after recording a few tracks of midi information (note only, no CCs yet), the machine freezes and needs to be rebooted. please test this setup, where digitakt is mainly used as a midi brain, as it seems to be unstable at the moment. the box has a lot of potential if the bugs can be ironed out.
Having a nightmare with DT2/Overbridge
Instant crash without warning… DigitaktII freezes with meters in DAW pinned, screaming feedback style noise with throw your headphones off your head in shock max volume.
Using LUNA/OS 1.03A and Overbridge 2.13
Rebooting DAW doesn’t help, only rebooting DT2.
Has happened 3 times now.
Have created a ticket.
Anyone else having this?
Is it possible to use overbridge and have the sound go out from the main out in the same time?
As soon as I load overbridge the main out goes quiet.
I want to record with overbridge in ableton, having monitor off.
I would like to listen through my audio interface.
USB set to EXT doesn’t work anymore with 1.03A.
Had to downgrade.
Someone more experienced than me will tell you how to manage monitoring in the best way, but there is still a simple way to listen to the Elektrons with their outputs and keep Overbridge: you can use your Elektron as a sound card for Ableton. In the Elektron settings keep the “usb Overbridge” setting and when you open the hardware settings of your sound card in Ableton you will see that Overbridge opens. From the Ableton Master track you will hear the sound of your outputs on the Elektron , and you will be able to open all the tracks related to the sounds, effects and inputs of the Elektron . With this system you also get around the problem of the maximum number of 16 tracks that can be used in a plugin inside Ableton. If you use your Elektron as a sound card you will be able to open ALL the tracks that Overbridge offers.
Sounds like a midi loop to me! Maybe you should filter the midi coming back to DT? Seems to me that you send Musi to the computer which sends back the same midi to Digitakt and so on! I’ve had this in the past with clock and other thing, and filtering what comes back or sent from the DT solved it
thanks for the suggestion.
i disabled midi clock send and receive + disabled incoming note information in the system settings to narrow down the probable cause of this problem. realearn has additional options to prevent echo feedback of midi cc information. i’m pretty sure it’s not a feedback loop problem and haven’t monitored any suspicious outgoing or incoming midi information from the dt2.
the sequencer usually plays for about 10 minutes and then the machine freezes and needs to be restarted. my guess is that my use case is rare and therefore hasn’t been thoroughly tested. can happen - it’s a pretty sophisticated machine with a lot of code in it …
We don’t like bugs either and want to fix them all, but even so it can be hard to fully reach 100% at all times. We always try to prioritize bugs so that major ones are fixed first. And the easier we can reproduce them, the faster they can be fixed. We also have extensive beta test groups, all to make sure that the products are stable. But even with those actions, some bugs can unfortunately slip through.
Well, some of them can actually be my fault 
However, adding features to one device doesn’t mean that bugs are not fixed for other devices. Some development is done in parallel to others, some is done well in advance but gets finalized at a later point as certain synchronization might be required.
The preferred way of submitting bugs and checking their status is to use our Support, but as I’m already replying here let’s go:
This is a known bug that will be fixed in a future release.
Are you sure this is after freezing, and not just exiting the Euclidian mode? If freezing is not involved, this is as expected - as the p-locked notes are stored in the regular trigs starting from 1. A button press is the same as adding a trig, just like in GRID REC mode.
This one has been very hard to reproduce, but we did find a way which will be fixed in a future release. If you have other methods to reproduce, please let our support know.
This was resolved in DT2 1.02 and the updated Transfer that was released at the same time.
Hi Thomas,
The reason I asked here is because it’s a topic about the 1.03 firmware and I’d like to avoid upgrading to a new firmware too soon, at the risk of breaking existing workflows. I also value the practical workarounds and confirmation of issues coming from the user base in general. I greatly appreciate the reply and context, thanks again for your hard work.
I’ve spent a lot of time troubleshooting and describing steps to reproduce bugs over the years, and will continue to do so as I encounter them. I’ve never written into support without trying my best to frame the bug report as best as I can. Sometimes the loop is never closed and I don’t see anything relevant in the changelogs, and I have to ask elsewhere.
I’ll double check this, but if what you say is the expected behavior, I’m still a bit confused - as it doesn’t show the pressed trigs as active in the Euclidean mode of course. Perhaps I’ve misunderstood the intended result. IIRC, what was happening was that any pressed trig would start to fill trigs “invisibly” in the background while in Euclidean mode, and you would only see them once switching out of Euclidean mode. I think you might be correct about this not applying to the “freeze” process.
I am still unable to preview a sample when using overbridge and I’ve muted the plugin.
Unmuting the plugin track fixes this; but I did not have to do this with the DT1.
The latest version of Firmware is 1.03A — does this newer version fix the bugs?
You can check release notes…