This information applies Analog Rytm, Analog Four, Analog Keys, Digitakt, Digitone, Digitone Keys. The screens look a little different depending on which unit you are using, but the steps are the same.

Access the global settings menu by pressing the cogwheel button (Digitakt, Digitone/Keys, Analog Four MKII, Analog Rytm MKII), Function + Track (Analog Rytm MKI), Function + Song (Analog Keys), Function + Keyboard C2 (Analog Four MKI).

In the global settings menu, select SYSTEM

In the SYSTEM submenu, select FORMAT +DRIVE

In the FORMAT +DRIVE submenu, select which items you want to format and then choose to ERASE SELECTED DATA

PROJECTS+SOUNDS is available on all machines and will remove sounds and projects created by the user, factory sounds, and the factory preset project.

SAMPLES is only available on Analog Rytm and Digitakt and will remove all user items, but the factory samples will remain (the factory samples do not occupy space on the +Drive and cannot be deleted). 

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

The Elektron C6 utility is a 32-bit application and is not supported under macOS 10.15 (Catalina) or later. C6 will not be updated further, instead, we recommend using Elektron Transfer for transferring samples, sounds, presets, and OS updates to your Elektron device.

Elektron Transfer does not support SID Station, Octatrack MKI/MKII, and Analog Drive. For Monomachine and Machinedrum (all versions), only OS transfers are supported.

You can download the Transfer utility here: https://www.elektron.se/support/

Another possible (non-Elektron) replacement for C6 is SysEx Librarian.

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.

Kits and patterns are part of projects, while sounds in the +Drive sound library are not, so backing up the project(s) will include patterns, kits and the sound pool of the project. Sounds located on the +Drive needs to be backed up separately.

In the global menu, go to the SYSTEM / USB CONFIG menu and make sure the machine is in USB-midi mode and not in Overbridge mode, the Overbridge mode setting is machine global, the change is persistent and is not saved as part of projects. You can change it back to Overbridge mode once the backup / restore is complete.

In the global menu, go to MIDI CONFIG / PORT CONFIG and make sure that OUTPUT TO is set to MIDI + USB or just USB. The midi port config is project specific and will be saved with the current project. Saving it and loading another project will activate the midi port settings of that project, the default setting of a new project is MIDI only, so if you haven't changed this before it needs be changed in order to use the USB port for midi output.

How to back up an entire +Drive sound bank from AK / AF

1. Start C6 and select the appropriate in/out midi ports and click the receive button.
2. Open the sound manager on your Analog Keys
3. Click trig 16 to open bank P
4. Click the right arrow button to open the sidebar menu
5. Scroll down and and choose SELECT ALL, all sounds should now be selected
6. Scroll further down and choose SEND SYSEX
7. The sounds in bank P transfers to your computer.
8. Once complete, click Stop! (where it previously said receive) in C6
9. Click the received data syx file and click the save button to save the backup file to the hard drive (make sure you have clicked the file(s) to save before clicking save, otherwise it will simply save a list of the currently open files and not the files themselves).
10. Repeat the above process for every bank where you have stored your sounds.

How to back up a project from AK / AF

1. Go to the MIDI CONFIG / PORT CONFIG and make sure that OUTPUT TO is set to MIDI + USB or just USB in your project
2. Start C6 and select the appropriate in/out midi ports and click the receive button.
3. Go to SYSEX DUMP in the global menu
4. Open SYSEX SEND
5. Send WHOLE PROJECT
6. Once complete, click Stop! (where it previously said receive) in C6
7. Click the received data syx file and click the save button to save the backup file to the hard drive (make sure you have clicked the file(s) to save before clicking save, otherwise it will simply save a list of the currently open files and not the files themselves).
8. Repeat the above process for every project you want to back up.

How to restore a project to AK / AF

1. Open C6
2. Click to mark the project syx file that you want to send to your machine
3. On your machine, create a brand new project, then open the global menu, go to SYSEX DUMP / SYSEX RECEIVE / ANYTHING / RECEIVE ANY
4. Click Send button in C6
5. Once the project has been received, save it to a +Drive slot using the SAVE PROJECT menu option in the global menu

How to restore an entire sound bank to AK / AF

1. Open C6 on your computer, load the previously backed up sound bank file
2. On the machine, go to SYSEX DUMP in the global menu
3. Open SYSEX RECEIVE
4. Using the [ARROW] keys, highlight +DRIVE SOUNDS on the left hand menu and press [YES/SAVE]. The highlight bar will now appear on the right hand menu. This is where you select the Sound Bank that will receive the new sounds. Select Sound Bank position using the [ARROW] keys. Sound Bank A and B normally contains preset sounds, so in this example we will select Sound Bank C.
5. Highlight Bank C and press [YES/SAVE]. The words “WAITING DATA...” will be shown flashing on the chosen Sound Bank position, indicating that it is ready to receive the .syx file from the computer.
   Note that if the Sound Bank already contains sounds that aren’t locked (consult the User Manual on how to do this), they will be overwritten with the new sounds. Make sure you select an unpopulated Sound Bank, or a Sound Bank that contains sounds that you do not wish to keep.
6. In C6, click the file you want to restore so it gets highlighted. Press the SEND button. A progress bar will appear at the bottom of the c6 window. On the Analog Keys/Four LCD screen you will see “WRITING DATA...” for the duration of the transfer. Transferring the sounds will take a few seconds.

We recommend using the software Elektron Transfer to load sound packs to your device. For devices that are not supported by Transfer, we recommend using either Elektron C6 or other SysEx software capable of sending and receiving SysEx data. Please note that C6 is not compatible with macOS Catalina and later.

For more detailed information on how to install sounds to your device, please see the Sound Pack Install Instructions.

RESOURCES

Transfer

C6

Sound Pack Install Instructions

If you have problems connecting to Transfer, please refer to this article.

INSTALLING SOUNDS TO A SPECIFIC SOUND BANK ON YOUR ELEKTRON DEVICE

1. Press [GLOBAL SETTINGS] or [SETTINGS] (depending on your device).

2. Scroll down and select SYSEX DUMP, and then press [YES].

3. Select SYSEX RECEIVE and press [YES]. 

4. Select +DRIVE SOUND or SOUNDS (depending on your device) and press [YES]. 

5. Select the BANK you want the sounds to be transferred to, for example, BANK D, and then press [YES]. The screen now reads “WAITING DATA”. 

6. In Transfer. On the DROP page, drag and drop the .syx file containing the sounds you want to transfer to where it reads “Drop files here”. 

When the transfer is finished you will find the Sounds in BANK D (in this example) when you go to the Sound Browser.

LOCATING YOUR SOUNDS IN YOUR ELEKTRON DEVICE AND LOADING THEM TO A TRACK

1. Press and hold [FUNC] and then turn the LEVEL/DATA or TRACK LEVEL knob (depending on your device) to open the SOUND BROWSER.

2. Press [BANK] + [TRIG 1-16] to select sound bank.

3. Navigate to the Sound you want to load, and then press [YES] to load the selected Sound to the active track.

INSTALLING A SAMPLE PACK
Here’s how to install a sample pack using Transfer. The steps below apply to Digitakt, Analog Rytm MKI, Analog Rytm MKII, and Model:Samples.

Method 1:

1. Select the device for both MIDI IN and MIDI OUT in Transfer, then press CONNECT.

2. Drag and drop the samples or folders on the DROP page.

Method 2:

1. Select the device for both MIDI IN and MIDI OUT in Transfer, then press CONNECT.

2. When the device has connected to Transfer, select the EXPLORE page.

3. Navigate to MY COMPUTER (e.g., your computer) in the left column and select the samples or folders you want to transfer.

4. Drag and drop the samples or folders to your preferred folder under DEVICE NAME (e.g., Digitakt or Analog Rytm, etc.) in the right column.

The default name of the folder the samples or folders end up in is /transfers-YYMMDD, which means you will get a folder with today's date by default. If you want to rename the folder, right-click and select RENAME. Change the name to e.g., the name of the Sound Pack.

If you have any further questions or issues, please contact Elektron Support.

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.

If you want to report an Overbridge related problem or issue, it is very useful if you can supply the User Care department and the developers with the problem-related logs from your system. This makes it easier for us to pinpoint what it is that is causing your problem.

All Overbridge related support tickets should include:

• Overbridge version.

• Computer OS.

• Firmware version (shown briefly on the display when the device is powered on) and the name of your Elektron device (e.g. Analog Four MKI/MKII).

• Logs (see instructions below).

• Steps to reproduce, if possible (if it is not possible to reproduce, please let us know this).

• If you have access to another device and/or another computer OS, please try to reproduce the issue with different combinations of devices and OS:es (and report what you find).

Extracting Logs from your Computer
Please extract the relevant diagnostics information, log files, or crash dumps from your operating system. Make sure you attach the files to your ticket.

macOS
If the Overbridge Control Panel freezes or crashes, you can find the log files in: /Users/“USER”/Library/Logs/Elektron Overbridge/. Make sure you attach the most recent file to the ticket.

If you experience problems in computer and device communication (USB connectivity issues, driver issues, etc.), please extract the relevant logs from the Console.app application. Assuming you can reproduce the problem, extract the log lines from just before you started your attempt to reproduce the problem, through to when the problem occurred. Here is how to achieve this:

1. Please choose the log that has the same name as your computer in the left sidebar (e.g., Davids iMac) and hit “Clear” on the top bar.

2. Reproduce the issue, and the log fils up with data.

3. Copy-paste the output into a text file and attach this to the ticket.

macOS saves information about app crashes in /Library/Logs/DiagnosticReports/. If you experience issues with plugin crashes or Overbridge Engine not showing your device as “idle” or “active”, then please include all files related to Overbridge from this folder.

Windows
If the Overbridge Control Panel freezes or crashes, you can find the log files in C:\Users\“USER”\AppData\Roaming\Elektron Overbridge. Make sure you attach the most recent file to the ticket.

If Windows has crashed with a blue screen, report this, and we might ask you to collect system crash logs for us.

REPORTING AN OVERBRIDGE RELATED ISSUE

Please contact Elektron support: https://www.elektron.se/customer/tickets/.