Digitakt 2 overbridge not working

I installed latest Digitakt 2 and overbridge version but the overbridge app doesn’t recognise the DT although the transfer app does work.(Mac os 14.7.1)
The overbridge setting on the DT is on
The DT accesssibility on my system settings is granted.
Any idea why this is not working?

Overbridge engine is on and connected?

If you’ve ever had OB working on this computer in the past, and you’ve just now updated and the behavior has changed (it’s not detecting DT2) this may have to do with uninstall of the old OB version, or it could potentially be current OB compatibility with your OS but I don’t know enough about Mac to determine that.

I would talk to support by filling out the contact form in your elektron.se account, I’ve read several instances of them giving someone a bunch of detailed instructions which were similar to wiping the registries on a PC, so whatever the Mac equivalent of finding and removing the residual path is, may be necessary.

I’m just taking a guess because it sounds like you did your part correctly, if transfer recognizes the device then both transfer and the DT2 have to be talking, so I would guess that this is specifically an issue with overbridge and or your computer.

The only thing I might do at this point is try it in a new project after power cycling, and I might switch overbridge mode off in the DT2 menu and then connect to transfer and then turn overbridge mode back on and try connecting to OB again. This is merely to confirm that it’s not stuck in usb audio mode, it should not be but bugs aren’t always predictable.

I would definitely get the contact form process started now, the sooner the better. Good luck.

Okay Thx …I will contact support

Thx a lot PrinceEcho…it was the engine,set it up in my privacy settings and it works :slight_smile:

1 Like

Can I ask how you did this specifically? :slight_smile: I have the same exact problem, and I am not sure what you mean.

Based on new version release notes the issue with installing overbridge might’ve been fixed …

The reference to the System Extention approval location was incorrect for MacOS Sequoia since

it is moved to a new location