If you feel that the input level on the Analog Heat MKI/MKII is lower than expected, there is a technical reason for why it is like this. Then input level on the Analog Heat is set like it is by design.

The Analog Heat attenuates (lowers) the incoming signal to create headroom for the distortion circuits and the filter. If it didn't do that, the levels would be too high and cause internal clipping if you use heavy distortion and turn up the resonance on the filter.

You can always use the LEVEL parameter to gain the level back up if you feel that the volume is to low after passing through the distortion, filter, and EQ.

You can manually remove Overbridge device entries if they are corrupt, or cause other problems.

REMOVING DEVICE ENTRIES IN WINDOWS

1. Press Win+R, and then write "regedit" in the box, and then press OK to open the Registry Editor.
   

   

2. Navigate to this key (a key is like a folder):
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ELEKTRON_OVERBRIDGE_USB
   

   

3. Here you see subkeys that are in this format:
   Parameters_1935_xxxx_yyyy
   The xxxx is the product ID. See below for more information*
   The yyyy is the unique ID of your particular device.

4. Right-click the device you want to remove and select "Delete" Do this for all subkeys related to your device

REMOVING DEVICE ENTRIES IN MACOS

This will delete all known devices from the ControlPanel and the CoreAudio plugin.

1. Start a terminal session.

2. Unload coreaudio daemon (or else you will not be able to move the coreaudio plist files)
   sudo launchctl unload /System/Library/LaunchDaemons/com.apple.audio.coreaudiod.plist
   sudo killall coreaudiod
   The second line is just in case the first one doesn't work.

3. Move / delete the plist files to another location:
   mkdir ~/Desktop/PlistBackup/
   sudo mv /Library/Preferences/Audio/com.apple.audio.DeviceSettings.plist ~/Desktop/PlistBackup/
   sudo mv /Library/Preferences/Audio/com.apple.audio.SystemSettings.plist ~/Desktop/PlistBackup/
   sudo mv ~/Library/Preferences/se.elektron.OverbridgeControlPanel.plist ~/Desktop/PlistBackup/
   sudo mv ~/Library/Preferences/se.elektron.overbridge.hal.plist ~/Desktop/PlistBackup/

4. Restart macOS

5. Remove PlistBackup folder on your desktop.

*Product ID table

This information applies to Analog Four, Analog Keys, Analog Heat, Analog Rytm, Digitakt, Digitone, Digitone Keys, Syntakt, Model:Cycles, and Model:Samples

To perform a Factory Reset, hold down the Function button (ACTIVE/ON button for Analog Heat) while powering on the device, then press the appropriate button when the startup menu appears. When the reset has been completed, the unit will reboot.

When you perform a factory reset on Analog Keys or Analog Four, the following happens:

• Project slot 001 will be overwritten and re-initialized with the factory preset project.
• The currently loaded project will be cleared and the factory preset project will be loaded to memory.
• Soundbanks A and B will be overwritten with the factory preset sounds.

The remaining project slots and sound banks will not be overwritten.

If you wish to keep the active project, remember to save it to a project slot higher than 001 before you perform the factory reset. If you have saved your own sounds to soundbanks A or B, you need to move them to a different bank if you want to keep them.

When you perform a factory reset on Analog Heat, the following happens:

Preset slots 001–016 will be overwritten with the factory presets. The remaining preset slots will be cleared.

When you perform a factory reset on Analog Rytm, the following happens:

• Project slot 001 will be overwritten and re-initialized with the factory preset project.
• The currently loaded project will be cleared and the factory preset project will be loaded to memory.
• Soundbank A will be overwritten with the factory preset sounds.

The remaining project slots and sound banks will not be overwritten.

If you wish to keep the active project, remember to save it to a project slot higher than 001 before you perform the factory reset. If you have saved your own sounds to soundbank A, you need to move them to a different bank if you want to keep them.

When you perform a factory reset on a Digitakt or Digitakt II, the following happens:

• Project slot 001 will be overwritten and re-initialized with the factory preset project.
• The currently loaded project will be cleared and the factory preset project will be loaded to memory.
• Sound/preset bank A will be overwritten with the factory presets.

The remaining project slots and sound/preset banks will not be overwritten. Any samples that you have transferred to the unit or recorded directly into the unit will remain on the +Drive after a factory reset.

If you wish to keep the active project, remember to save it to a project slot higher than 001 before you perform the factory reset. If you have saved your own sounds/presets to soundbank A, you need to move them to a different bank if you want to keep them.

When you perform a factory reset on Digitone or Digitone Keys, the following happens:

• Project slot 001 will be overwritten and re-initialized with the factory preset project.
• The currently loaded project will be cleared and the factory preset project will be loaded to memory.
• Soundbanks A and B will be overwritten with the factory preset sounds.

The remaining project slots and sound banks will not be overwritten.

If you wish to keep the active project, remember to save it to a project slot higher than 001 before you perform the factory reset. If you have saved your own sounds to soundbanks A or B, you need to move them to a different bank if you want to keep them.

When you perform a factory reset on Syntakt, the following happens:

• Project slot 001 will be overwritten and re-initialized with the factory preset project.
• The currently loaded project will be cleared and the factory preset project will be loaded to memory.
• Soundbanks A through E will be overwritten with the factory preset sounds.

The remaining project slots and sound banks will not be overwritten.

If you wish to keep the active project, remember to save it to a project slot higher than 001 before you perform the factory reset. If you have saved your own sounds to soundbanks A through E, you need to move them to a different bank if you want to keep them.

When you perform a factory reset on Model:Cycles or Model:Samples, the following happens:

• Project slot 01 will be overwritten and re-initialized with the factory preset project.
• The currently loaded project will be cleared and the factory preset project will be loaded to memory.

The remaining project slots and sound banks will not be overwritten.

If you wish to keep the active project, remember to save it to a project slot higher than 01 before you perform the factory reset.

In order to update your device using the method described in this article, your device needs to run at least the OS version listed below. The OS version is visible in the bottom right corner of the device screen when it is being powered on.

If the device is running an older version than the one listed below, you need to update your device using sysex transfer. Refer to the following article for information on how to update using sysex transfer. Once your device is running at least the OS version listed above, you can use the method described in this article for future OS updates.

Connect your device to one of the USB ports of your computer and start Elektron Transfer, make sure the unit is selected as the MIDI in and MIDI out ports, and then click the Connect button.

Unzip the archive and drag and drop the .syx file containing the OS update onto the big area with the text "Drop files here".

When you drop the OS file, it will automatically be transferred to the device.

When OS has been transferred, Elektron Transfer will let you know that you need to press the YES button on your device to perfrom the upgrade. Press the YES button and follow the instructions on the device screen. DO NOT TURN THE DEVICE OFF UNTIL THE UPGRADE IS COMPLETED.

If you have problems getting your Elektron device connected to Overbridge Engine, there are several ways to solve this depending on what kind of connection problem you have.

MY ELEKTRON DEVICE IS NOT VISIBLE IN OVERBRIDGE ENGINE

Your Elektron device is not visible/not detected in the Overbridge Engine application.

1. Download and install the latest version of Overbridge and device OS. For more information, please see this article about how to install Overbridge.

2. Set your Elektron device to Overbridge mode. For more information, please see the User Manual for your Elektron device.

3. Make sure the USB cable is connected correctly.

If you are using a Mac, please read this article before continuing any further troubleshooting.

MY ELEKTRON DEVICE IS VISIBLE IN OVERBRIDGE ENGINE BUT IS NOT CONNECTING

Overbridge uses local ports to communicate between different applications within the Overbridge suite, and between Overbridge and the computer. But other applications installed on your system may already use the same ports that Overbridge needs for communication. For Overbridge to work, you must close the other applications that use these ports.

Port 46000 needs to be free for Overbridge Engine to be able to communicate with your computer. Also, each Elektron device that you use in Overbridge must be able to use port 460n0, 460n1, and 460n2, where n is the device that you have added.

Example:
If you have two Elektron devices connected, you need to make sure that the following ports are free:

46000 (for Overbridge Engine - Computer communication)
46010, 46011, 46012 (for Elektron device 1 - Overbridge Engine communication)
46020, 46021, 46022 (for Elektron device 2 - Overbridge Engine communication)

Please see this article for information about how to find what ports are in use by the computer's processes and applications, and how to free them up.

MY ELEKTRON DEVICE IS VISIBLE IN OVERBRIDGE ENGINE BUT SHOWS AN ERROR

Your Elektron device is shown as “Measuring” or “Fault” in Overbridge Engine when you try to connect them to Overbridge and it never gets out of this state.

1. Make sure you update to the latest OS for your Elektron device. Available for download here.

2. Configure the devices’ audio channels to send to and from the device in the Overbridge Control Panel. (Only applicable for Analog Rytm MK I, Analog Four MK I, Analog Heat MK I, and Analog Keys.)

3. Another cause of this problem might be because of USB2/USB3 and chipset issues. Please see this article concerning USB2/USB3 and chipset issues and how to solve them.

Here you can find detailed specifications of the power supplies (PSU’s) for the different Elektron devices.

MODEL:SAMPLES, MODEL:CYCLES

Current Elektron power supply: PSU-4b. These devices were originally shipped with PSU-4 and still work with PSU-4. The PSU-4b power supply includes adapters for the following regions: North America, Continental Europe, the United Kingdom, Brazil, Japan, Korea, Australia, and China. The PSU-4b power supply handles voltages of 100-240 VAC, 50/60Hz.

The power supply you want to use must meet the following specifications:

• Voltage: 5 VDC

• Minimum Current Rating: 1.2 A

• Barrel Connector Size: 3.5 mm outer diameter, 1.35 mm inner diameter

• Polarity: Positive center

ANALOG RYTM MKI/MKII, ANALOG FOUR MKI/MKII, OCTATRACK MKII, ANALOG DRIVE, ANALOG HEAT MKI/MKII, DIGITAKT, DIGITONE, DIGITONE KEYS, SYNTAKT

Current Elektron power supply: PSU-3c. These devices were originally shipped with PSU-3, PSU-3b, or PSU-3c. All these devices work with PSU-3 and PSU-3b (With the exception of Analog Drive which doesn’t work with PSU-3). The PSU-3c power supply handles voltages of 100-240 VAC, 50/60Hz.

The power supply you want to use must meet the following specifications:

• Voltage: 12 VDC

• Minimum Current Rating: 2 A

• Barrel Connector Size: 5.5 mm outer diameter, 2.5 mm inner diameter

• Polarity: Positive center

MONOMACHINE MKII, MACHINEDRUM MKII, OCTATRACK MKI

Current Elektron power supply: PSU-2b. These devices were originally shipped with PSU-2. The PSU-2b power supply handles voltages of 100-240 VAC, 50/60Hz.

The power supply you want to use must meet the following specifications:

• Voltage: 6 VDC

• Minimum Current Rating: 3 A

• Barrel Connector Size: 5.5 mm outer diameter, 2.5 mm inner diameter, 6 mm length

• Polarity: Positive center

MONOMACHINE MKI, MACHINEDRUM MKI

Original (and now obsolete) Elektron power supply: PSU-1 (two versions depending on voltage standard)

Please note that the power supply output must be AC!

The power supply you want to use must meet the following specifications:

• Voltage: 6 VAC, 50/60Hz

• Minimum Current Rating: 2.5 A

• Barrel Connector Size: 5.5 mm outer diameter, 2.5 mm inner diameter, 6 mm length

SIDSTATION

The power supply you use must meet the following specifications:

• Voltage: 6 VDC

• Minimum Current Rating: 400 mA

• Barrel Connector Size: 5.5 mm outer diameter, 2.1 mm inner diameter

• Polarity: Positive center

OVERHUB

In most cases, you don't need to use a power supply together with the Overhub. However, if you want to use it together with a non-self powered device (for example, an external hard drive), you must connect a power supply to the Overhub.

Please note that the Overhub is not shipped with a power supply.

The power supply you use must meet the following specifications:

• Voltage: 5 V DC

• Minimum Current: 4 A (3 A on earlier devices.) This number is written on the Overhub itself so you can see there which version you have.)

• Barrel Connector Size: 3.5 mm outer diameter, 1.35 mm inner diameter, 6 mm length

• Polarity: Positive center

TROUBLESHOOTING YOUR ELEKTRON DEVICE

If you are experiencing problems with your Elektron device, there are several different things you should do before you contact Elektron support. There are a couple of ways to self diagnose your device. Please use this guide to determine whether the problem is hardware related or in the software/firmware.

A. Basic troubleshooting

To make sure that the issue isn’t software related, and/or caused by external interference (such as incoming MIDI data causing MIDI feedback), please do the following, and then check if the problem is still there after each step of it is solved: 

1. Install the latest OS for your Elektron device. Available for download here.

2. Unplug all MIDI cables and the USB cable from the device.

3. Perform a factory reset. Read more about factory reset here.

4. Create a new project.

B. TEST mode (not available on Model:Samples, Model:Cycles, and Analog Drive)

In TEST mode, you can perform a variety of tasks to determine the health status of your device. If you have any trouble with your device and suspect it may be due to a hardware problem, perform this self-test.

1. Hold down the [FUNC] button on ([ACTIVE]/[ON] for Analog Heat) your device while powering it up to enter the STARTUP menu.

2. In the STARTUP menu, press the appropriate button to enter the TEST mode.
   WARNING: For testing purposes on some Elektron devices, a short, loud beep is heard through all outputs of the unit when you enter the TEST mode. If you encounter any errors here, it might be a sign that there is a problem with the device.

3. In this mode, it is also possible to check the buttons and encoders/potentiometers functionality. Depending on which device you are using, most buttons either light up a led-light and the display shows which button is pressed, or turn the display on/off. This method is an excellent way to confirm if a button is broken or not. If the device doesn’t register a button press, then it’s likely that the button needs to be replaced. (MASTER VOLUME does not give any indication on the screen when it is turned). Various sequencer button combinations change the color on the button mechanisms on the devices where this is available.

If the information above did not solve the problems, please proceed to this article.

This article explains some of the reasons for crackles, dropouts (gaps in playback) or glitches during playback. Hereafter these will be referred to as simply ‘dropouts’. It also tries to explain why a modern computer can have performance problems although it is powerful enough for the task. It explains the problem domain and tries to give some tips on how you can solve the problems.

USB BANDWIDTH

In some cases, your USB bandwidth might be limited, and this could introduce various problems. There are a couple of reasons why those problems may arise.

Sharing USB Host controller (USB 2.0 Full Speed)

Overbridge for Analog Four MKI, Analog Keys, and Analog Rytm MKI uses USB 2.0 Full Speed. This USB specification limits the data transfer rate to max 12 Mbps. Later Elektron products use USB 2.0 High Speed and have a max rate of 480 Mbps. Many laptops use a single USB host controller that controls all ports. It means that if you have multiple devices connected that run with USB 2.0 Full Speed they might be sharing the 12 Mbps maximum bandwidth. It is, however, possible that your computer has multiple USB host controllers. You can try to connect a device to a different port that might also use a different host controller internally. This might increase the possible bandwidth for each device.

USB 2.0 Full Speed also limits the number of audio channels that can stream simultaneously. If you open the Overbridge Control Panel and configure your USB Full Speed device to use fewer channels and/or a lower bit depth, this might improve the Overbridge performance on your system.

USB Hubs

When connecting a USB 2.0 Full Speed device (12 Mbps) to an STT hub (typical for an internal laptop hub), all devices on that hub are limited by 12 Mbps, even devices that are otherwise High Speed or Super Speed. We recommend that you use an MTT hub (such as the Elektron Overhub) whenever you connect a Full Speed device to your system so as not to constraint your other USB devices.

It is especially important to use an MTT hub if you want to use more than one Full Speed device at the time. Connecting two Analog Four MK1 to an STT hub, for example, causes them both to share only 12 Mbps bandwidth. If they instead connect via an MTT hub, they get 12 Mbps each.

SAMPLE BUFFER SIZE & AUDIO LATENCY

The audible latency in your DAW can be described as the delay time from when the source of an audio stream is played until you hear it. The sample buffer size is the number of audio samples that are processed in each audio packet. A larger buffer size introduces a higher audible latency but might solve problems related to real-time performance as the computer gets a longer time slot to process data. A system with less processing power or more other software/hardware needs a larger buffer size. If you experience dropouts you might have to adjust this to your needs.

• Make sure your DAW is configured with an appropriate sample buffer size for your hardware.

• Please also make sure that Overbridge is configured with an appropriate Plugin Buffer Size in the Overbridge Control Panel.

• If you are on a Mac, adjusting the Buffer Safety Margin in the Overbridge Control Panel can also improve the performance of streaming audio.

• If you are using Windows, adjust the performance mode in the Control Panel to match your hardware.

OTHER CPU INTENSIVE APPLICATIONS RUNNING

Do not run other CPU intensive applications at the same time as Overbridge. These might put a high strain on your computer and limit its real-time capabilities.

Examples of these kinds of applications are:

• Web browsers with multiple open tabs.

• Image or video/3D editor programs.

• Games

AUDIO LATENCY AND REAL-TIME REQUIREMENTS 

Real-time applications, such as a DAW, have very different requirements than other software on your computer. The big difference between a DAW and for example, a video editing program is that in a video editing program the editing is mainly done while the video isn’t playing. After the editing is done the result is played. The processing is allowed to take some time and can be interrupted without you knowing that it was. This is not a real-time process.

Another example is a web browser that is allowed to have a response time from click to result of a few hundred or even thousands of milliseconds before it is deemed unusable. The typical case in a DAW, however, is to run a set of plugins and/or recording sessions while also listening to the output of these. The processing of these sources is always time-limited because if something takes a too long time, it is audible, and the harmonic content becomes distorted and unacceptable. This is a real-time process. 

The sound card converts digital samples to analog from the sample buffer at a fixed frequency, decided by the sample rate in your DAW. It always expects there to be a sample in the buffer to convert. If there is no sample available, it tries to convert empty data, resulting in a dropout. 

It is the CPU of your computer that carries out the actual audio sample processing. The CPU is, at the same time, constantly interrupted by other processes or devices in your system. Therefore, it can’t guarantee to deliver at a specific frequency but is instead given a time slot to deliver. This time is decided by the buffer size and sample rate in your DAW. Audio latency is when the CPU fails to deliver a sample to the buffer in time before the sound card needs to read it. 

The CPU itself is capable of delivering in time on all modern high performing computers. However, as mentioned before, the CPU is always interrupted by other processes or devices on the system. This is not a problem per se, but some devices are more prone to lock up the CPU and not giving it enough time to perform the real-time task of audio processing. Other performance heavy software might also cause the same problem. Therefore, make sure you are not running any heavy processing outside of your DAW.

Listed below are some devices that can easily lock up the CPU.

High probability of lock-up

• Video Cards

• Audio Interfaces

Medium probability of lock-up

• Network Interfaces

• USB Controllers 

• Disk Controllers 

Before troubleshooting the devices, make sure you have all of these devices’ latest drivers.

On a Windows PC you can debug your system by disabling devices in the device manager to figure out which device is causing the CPU to lock up. You can use tools such as DPC Latency Checker or LatencyMon to measure the devices’ latency independently from your DAW setup. If you do find problems when you run these tools, we recommend replacing the device or devices that are causing the problems. If you find no problems with either of these tools, there is a possibility that the problem is with your DAW or a plugin used in your project.

COMPUTER HARDWARE RELATED ISSUES

There are som known incompatibility problems with certain hardware:

• Intel Core2Duo processors, or Xeon CPUs from that same generation, are not supported.

• There could be USB 2.0/3.0 compatibility issues. For more information, please see this article.

• Some USB host controller chipsets have worse performance than others. If you use a USB hub, it adds another chipset in the signal chain and could potentially worsen the performance.