Overbridge 2.0.24 Public Beta

Overbridge 2.0.24 Public Beta

This release brings support for the new Analog Four, Keys and Rytm firmware as well as a few fixes. Unfortunately no Catalina support yet.

Improvements since last version (2.0.21)


  • Support for Analog Four MKI/MKII 1.40A
  • Support for Analog Keys 1.40A
  • Support for Analog Rytm MKI/MKII 1.50
  • Fixed an issue where the audio stream went silent when automating parameters in Logic.
  • Fixed an issue where the parameter would jump erratically and cause audio glitches in Logic when automating in Read and Touch mode.
  • Fixed an issue where the software was not signed properly on Windows.
  • Fixed possible crash in Audio Wave Scroller
  • Fixed possible crash in VST interface


  • Added rectangular tooltips in Control Panel and Engine

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

  • Analog Four mkI/mkII running OS 1.40A NEW
  • Analog Keys running OS 1.40A NEW
  • Analog Rytm mkI/mkII running OS 1.50 NEW
  • Analog Heat mkI/mkII running OS 1.20
  • Digitakt running OS 1.11
  • Digitone and Digitone Keys running OS 1.21

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, Digitakt and Digitone
  • VST Plugin macOS and Windows for Analog Four, Analog Heat, Analog Keys, Analog Rytm, Digitakt and Digitone
  • AU Plugin for Analog Four, Analog Heat, Analog Keys, Analog Rytm, Digitakt and Digitone

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 VST/AU for 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/AU 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.40
  • Analog Keys running OS 1.40
  • Analog Rytm mkI/mkII running OS 1.50
  • Analog Heat mkI/mkII running OS 1.20
  • Digitakt running OS 1.11
  • Digitone and Digitone Keys running OS 1.21

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 and Bitwig. But other DAWs will be supported as the beta progresses.


Elektron_Overbridge_2.0.24.11_Beta.dmg (69.6 MB)

Elektron_Overbridge_2.0.24.11_Beta.zip (52.2 MB)

Analog Four/Keys MKI:
Analog-Four_Analog-Keys_OS1.40A.zip (824.0 KB)

Analog Four MKII:
Analog-Four_MKII_OS1.40A.zip (845.0 KB)

Analog Heat MKI:
Analog-Heat_OS1.20.zip (452.8 KB)

Analog Heat MKII:
Analog-Heat_MKII_OS1.20.zip (463.6 KB)

Analog Rytm MKI:
Analog-Rytm_OS1.50A.zip (1.1 MB)

Analog Rytm MKII:
Analog-Rytm_MKII_OS1.50A.zip (1.1 MB)

Digitakt_OS1.11.zip (745.3 KB)

Digitone and Digitone Keys:
Digitone_and_Digitone_Keys_OS1.21.zip (1.0 MB)

Overbridge User Manual_2.0_Beta.pdf (1.0 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

  • Automation using external MIDI CC or using Overbridge may slowdown the units GUI.
  • 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.


Overbridge 2.0.24 Public Beta



Does this version include “stuck notes” fix for Digitone? Did anyone checked yet? Thanks!


Analog Keys MK2 confirmed!)))


Hehe unfortunately not, will fix that typo. Copy/Paste isn’t always your friend… :diddly:



Looking forward to the catalina update.
But thank you regardless
Keep up the good work :slight_smile:

1 Like

Just to note I needed to disable my antivirus to install .24
Guessing it was a false positive…


Like @PlombirSound asked… When can we expect a stucked note fix for Digitone?
Kind regards, Sander

I’ll investigate. Thanks for reporting.

1 Like

so first time the update was a failure for me, digitone still works BUT analog 4 mkii and RYTM mkii

Doesn’t recognise any midi controllers in standalone app but makes sound when pressing virtual keys on it or its on board triggers

Any ideas?

VST/AU plugin Still not working on my Digitakt macos Mojave Ableton. Standalone works

1 Like

Hi Olle, thanks for the update. I’ve raised tickets about the following which I think must’ve been missed because it’s been a few months now. Can I just get some clarification on the following please before I upgrade…

I put off using the Public beta of OB and went back to using the Closed beta because the updated version ran automatic latency compensation when first opened, this was a problem as I send all midi clock from my Audio interface, this requires fine tuning midi clock delay to get everything in sync but this latency compensation thing throws all that out and makes it impossible as it runs every time a project with OB in it opens. Has there since been a way to disable this?

I hope this makes sense, when I open OB I go and disable clock&transport but the latency compensation has already run by then and confused everything.


I did it, sequencing doesn’t work on the Analgo Rytm MK1, only playing in the chromatic mode but after recording it seems MIDI is not going out. Also my BT is coming only from the left side with no panning…

it does work

Couple of things - you need to enable Midi out per Track (Fn+Trig)
Secondly, there is a way to make the Pads output to Track Channel or Auto channel
Thirdly, there seems to be a bug whereby the Pads will output a different range when played chromatically to those midi notes when sequenced, this is offset 2 octaves


I had the same problem on first startup of the A4 standalone (on Windows 10)… It was because my antivirus (Avast) had interrupted the initial startup while it scanned for suspected malware. Once avast considered the app was safe I had to reboot my system and then A4 standalone correctly displayed connected midi inputs.

1 Like

mine displays all midi connection ports and even when they are checked, the midi seems not to trigger anything in any stand alone devices. I’m on OS X 10.13.6