Overbridge 2.0.11 Public Beta - Plugins, Drivers and Firmware

Overbridge 2.0.11 Public Beta


There is a new version available below.

  • We have done performance related improvements in the macOS driver. If you have had issues with dropouts and working with multiple units I would be really interested in hearing if this version is an improvement or not.

  • The updated driver for Windows, includes improvements to parameter data sent to and from the plugin.

  • The macOS kernel extension is now signed by Elektron Music Machines

  • The GUI framework has been updated both in macOS and Windows.

This is a public beta, as opposed to a stable release. As a result, we encourage you to submit any queries or issues to our support channels. The public beta will continue until we are in a position to release a stable version. Make sure you read the manual, the topic How to report issues and the section below with Known Issues.

Each Elektron Overbridge device typically exposes all individual track/voice channels as separate USB Audio channels, for multi-track recording into DAWs. Some Elektron Overbridge devices such as the Analog Rytm and Analog Four also allow you to route audio from a computer host into individual track audio paths for intricate processing. The Analog Heat acts entirely as a sound processing unit. The plugin routes audio from your computer host, through the effects chain and back into the host. All Elektron Overbridge devices allow you to play audio from the computer host directly to the device’s main output, making the device act as a sound card for playing back music etc. The Overbridge Control Panel application is bundled together with the drivers, providing a simple channel monitor for your devices.

The suite includes

  • Audio over USB functionality for all Overbridge-enabled devices
  • Overbridge Control Panel
  • Overbridge Engine
  • Standalone Editor for Analog Four, Analog Heat, Analog Keys, Analog Rytm and Digitakt
  • VST Plugin, Mac and Windows for Analog Four, Analog Heat, Analog Keys, Analog Rytm and Digitakt
  • Digitone Standalone Editor and Plugin are currently in development and will be released at a later date.

USB Audio drivers for Windows and macOS
The USB Audio Drivers will expose Audio and MIDI-interfaces for Elektron Overbridge devices.
On Windows, WDM and ASIO audio interfaces are provided.
On macOS, HAL and CoreAudio audio interfaces are provided.

Standalone Editor for Windows and macOS
The Standalone Editor allows for controlling the Overbridge enabled devices parameters via a GUI desktop application and also managing sounds and samples on the device.
The Overbridge Engine handles all USB communication between your connected Elektron device and the standalone editor.

VST Plugin for Windows and macOS
The Plugin allows for controlling the Overbridge enabled devices and stream audio via a VST Plugin. This makes it possible to sequence, sync and automate the device with your DAW. Audio will be streamed to the plugin making it possible to use your audio interface of choice in your DAW while still receiving audio from your unit.
The Overbridge Engine handles all USB communication between your connected Elektron device and the VST Plugin.

Total Recall
This feature lets you save projects from Overbridge enabled devices into your DAW’s project.

Total Recall can be enabled by pressing its icon in the plugin. The unit will then sync the project files with the DAW. When opening a DAW project that has Total Recall enabled and a synced project the unit will ask you to confirm that you want to transfer the project from the DAW to the unit’s active project. Any unsaved projects will be lost.

This beta release requires you to have the listed firmware installed on respective units. These are beta OSs and are not guaranteed to work in any other setup.

  • Analog Four mkI/mkII running OS 1.36_BETA2
  • Analog Keys running OS 1.36_BETA2
  • Analog Rytm mkI/mkII running OS 1.46_BETA1
  • Analog Heat mkI/mkII running OS 1.11_BETA3
  • Digitakt running OS 1.11_BETA6
  • Digitone running OS 1.11_BETA1

Minimum Computer Requirements
Overbridge 2.0 requires a high-performance computer optimized for audio production. Elektron recommends the below specs as minimum specs.

  • At least 8GB of RAM.
  • At least Intel Core i5 CPU.
  • OpenGL 3.2 capable GPU.
  • Dedicated USB host port for each Overbridge hardware device. USB Hubs are generally not supported and may cause problems with both connectivity and performance.
  • Windows 10/macOS 10.12

The specs are not the only thing necessary to have a smooth experience. Real-time performance of the system is equally important. This is affected by other running processes and by different manufacturers of computer hardware. There are tools available to analyze systems.

DAW Support
This version will work best with Ableton Live. But other DAWs will be supported as the beta progresses.
AU plugins are not yet available, so if Logic is your DAW of choice, use the standalone version to record with and then import the tracks manually to Logic. Or select the unit as your audio interface. Or use an aggregated device.

Changes from to

New driver for macOS(major performance update)
New driver for Win(minor update)
macOS kernel extension is now signed by Elektron Music Machines

Updated framework for GUI


Elektron_Overbridge_2.0.11.2_Beta.dmg (51 MB)

Elektron_Overbridge_2.0.11.2_Beta.zip (44 MB)

Analog Four/Keys MKI:
Analog-Four_Analog-Keys_OS1.36_BETA2.zip (870.4 KB)

Analog Four MKII:
Analog-Four_MKII_OS1.36_BETA2.zip (905.0 KB)

Analog Heat MKI:
Analog-Heat_OS1.11_BETA3.zip (485.3 KB)

Analog Heat MKII:
Analog-Heat_MKII_OS1.11_BETA3.zip (494.2 KB)

Analog Rytm MKI:
Analog-Rytm_OS1.46_BETA1.zip (1.1 MB)

Analog Rytm MKII:
Analog-Rytm_MKII_OS1.46_BETA1.zip (1.2 MB)

Digitakt_OS1.11_BETA6.zip (800.8 KB)

Digitone_OS1.11_BETA1.zip (896.4 KB)

Overbridge User Manual_2.0_Beta.pdf (5.4 MB)

Update Notifications

Run the Overbridge Control Panel application regularly to ensure you get automatic notifications about the availability of software updates directly from Elektron.

Upgrading from previous Overbridge versions

If upgrading from Overbridge 1.15 or earlier, note that a complete uninstall of the previous version will be performed first. This means you will lose any previously installed Overbridge plugins and Overbridge drivers if you install the Overbridge 2.0 Public Beta.

Known issues

  • In some occasions there are dropouts when using multiple Overbridge devices, even at lower loads.
  • Higher loads on the CPU may cause dropouts when using the units as Audio Interfaces.
  • Unit selection list in the plugin stays visible when hiding the plugin if it has been left open.
  • Issue with latency for MIDI when sending MIDI from the device to another external device.
  • On some systems, Bit Accurate driver is not showing any channels in Studio One and Bitwig.
  • Stability issues.
  • VST plugin does not utilize retina resolution (Windows).

To think about when using an Overbridge unit as a sound card:

Most Overbridge enabled devices can be used as 2 in 2 out interfaces in addition to the audio over USB for each individual voice. This means that if you are not careful with your routing and where/what you are monitoring, you might get feedback or voice doubling. Especially when software monitoring in your DAW.

In the Digitakt, doubling of audio can be prevented by turning off all internal audio sent to the mains out on the Digitakt. This is done by changing Settings > System > USB config > “Int to Main” to “Off”. Auto has no effect when using the Standalone Editor.

The Heat is a 4 in 4 out interface and will not be affected by the issue described above. If you still experience issues, check in the Heat manual that you have set up the routing correctly.


Thanks @Olle! Is it possible to explain the difference or advantages/disadvantages of using Bit Accurate, please? I’ve been using it with absolutely no problems. Just wanted to know which option is optimal. Cheers


In Mojave I had to allow the new signed kernel extension, which mojave requires a restart for, which it couldnt do bec the installation-process was still active. No biggy, but a bit messy :slight_smile:


Thanks for your hard work, guys.
Is there any way to use the “sidechain” inputs (AR/A4) in the standalone applications? I haven’t figured out how to do it on Windows.

1 Like

Coreaudio is used by the system and allows for the unit to be used by it. For example aggrigated device, default audio device for the system. But adds another layer between the unit and the DAW resulting in slightly higher latency and a different resampler for the audio stream. It will give you the option to for example in the Digitakt sample from youtube or any other source on the computer. Bitaccurate(HAL) is one less layer but only works with software that supports it for example most DAWs. When using the plugin this is the one used in the background. One is not really better than the other but will behave differently on different system and have different uses.


Hmm, not sure if both the system and the standalone app can use the same audio interface in windows when it’s ASIO. Could be wrong as I’m not that familiar with it. Send audio on channel numbers higher than 2 and they should pass into the tracks of the AR/Rytm.

1 Like

Thanks for that explanation. I’d always assumed the closer you are to the h/w the better. But reality is always more nuanced. I been using BA mode mostly though. Chugs along fine on my i5 Mac, I do have 16gb ram if that helps. Haven’t had any issues with the beta :yum:

1 Like

Ableton seems to see the plug in but upon double clicking it doesn’t start it??? anyone else? standalone works fine

osx HS

@phasingtomsolo, since I can’t reply in the other topic, I’d like to continue here.

Buffer settings everywhere are at 64. Thanks for mentioning the standalone Digitakt editor, the driver type was set to Windows Audio, I changed that to ASIO, and then selected my Focusrite ASIO driver. I don’t think my recording settings are the cause, never changed those and didn’t have a problem before.

Thanks, set those to stereo, good observation.

They were initially set to the default setting, then changed them to input stereo channel 5 + 6 (the channels that my Digitakt are connected to on my audio interface). Now changed them to None, but it doesn’t solve the problem. I’m feeling I’m missing something quite obvious but unfortunately I lack Reaper skills to find out what. Will continue to look. Many thanks for your help anyway!

1 Like



downloaded twice.

On Windows 10 really stable and tight, thank you.
Rytm and A4 is there any chance to calibrate levels of the analog outs to overbridge?
Analog outs are a way louder this is a good thing regarding signal to noise ratio especially for rytm. To increase volume with utility in Ableton isnt a good workaround due to increase the noise level. Prefer to come hot as possible to inputs and reduce the level before processing if required from some analog emus.
In case of the rytm I found especially for kicks or other bassheavy stuff to gainstage it a bit quieter and still get enough coloration from the machine that I really like😀 Combination of hard outs and overbridge my way to go at the moment, love it!
A4 the same if you want a bit cleaner sounds or add color with other stuff its to quiet for overbridge.

Yeah reinstalled and vst simply isn’t working on 10.13.6

DTOB-2INs.RPP (9.2 KB)

If this attachment works, maybe it’ll help? It’s a Reaper project template
I just updated to the new Overbridge 2.0.11 Public Beta driver, so start with doing that first

This is just a really basic layout, I rearranged things a little. Tracks 1-8, FX Main, L Input, R Input, Overbridge. All tracks are set up to record in “stereo”. The Overbridge track won’t record an empty file when you record (it’s set up to monitor only)

This may have my tempo and time sig settings embedded, look out for that

So far on the new OB it seems my pitch variation is cleared up from bar one on, but I still get a glitch bomb on that bar. It’s a good idea to get in the habit of not recording from the zero point anyway…I’ll plan an empty couple of bars into my recordings until I can update to an new W10 machine.

I’m making some progress with midi pan control, but it gets really weird fast. More on that later

Volume control: with midi I think you’ll be able to dedicate an encoder to control a reaper track fader. So if you take all your audio out of the main mix and send everything to a master Digitakt Audio Buss track you’ll have somewhat of a solution? You should get good recordings first though…

You never had problems before ever trying to integrate the Overbridge driver and Digitakt into your existing system that is using another ASIO driver… but now you need everything to communicate to function
-What are your other soundcard/reaper settings? Buffer? Bit Rate? Sample Rate?
I believe the Digitakt is operating at 24bit/48, you might have to have it all set the same, maybe?

You may have been looking in a different area of Reaper than I was suggesting, not sure.
If that project template works for you then perhaps those settings will address that concern anyway?

Good luck!

EDIT: just to mention, on my W7 machine the Digitakt plug in in Reaper has improved a little as far as performance goes.
The stand alone Control Panel and the Digitakt editor aren’t formatting properly. The image is there, and all the controls are too, but they aren’t attached to each other, you have to go hunting in empty space to find them, clicking, right clicking.
Wonder if this is happening for W10 users?
This wasn’t happening with the previous beta

1 Like

Thanks @Olle, do you know if the occasional pitch and tempo glitches on macOS have anything to do with the addressed performance issues?

No not this time, that is a different issue that we are working on. It occurs for some users when using large buffer sizes and when using loop points or during the first bar when pressing play in your DAW. It differs from DAW to DAW and from system to system. Not everyone is affected.

The performance issues addressed are for dropouts on systems that has less real-time processing power. Occurring more often when running more than one unit.

Hey good people! After a few hiccups, this version seems a tad, wee bit more stable than last one. But I have a more general problem with the plugins!

How do you write the automation in Ableton? Normally I would grab a parameter in Ableton, and the right automation lane would show in the arranger window. But with the VST (let’s say; Analog 4), nothing happens! The automation gest recorded if i turn encoders manually, but A4 doesnt seem to respond to the automation anyways! Regular midi tracks without the plugin works just fine, like they always have. But I would be so happy to have automation and everything in one Track to rule them all.

Hi All. I have installed overbridge for Digitakt only ( on my mac and installed the new OS on Digitakt (1.11) and hooked up via USB
I can use the Digitakt as an I/O but when I go to launch Logic Pro X, Electron does not appear in the plug-ins (instrument) option. Could anyone help me understand why? Thanks


AU plugins are not yet available.

Just a few lines above where you downloaded the driver in this thread it says:

DAW Support
This version will work best with Ableton Live . But other DAWs will be supported as the beta progresses.
AU plugins are not yet available , so if Logic is your DAW of choice, use the standalone version to record with and then import the tracks manually to Logic. Or select the unit as your audio interface. Or use an aggregated device.


Thank you for the quick response. Just found I could record audio via OB so all good, thanks for the help.