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.

TROUBLESHOOTING OVERBRIDGE

Here are some basic steps that you should perform first if you are having trouble with Overbridge

1. Make sure your setup matches the system requirements.

2. Uninstall any earlier version of Overbridge from your computer.

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

4. Install the latest version of Overbridge. Available for download here.

5. You must activate Overbridge mode on your Elektron device to use it together with Overbridge. Select OVERBRIDGE MODE on your device in the USB CONFIG menu, found in SETTINGS > SYSTEM > USB CONFIG.

REPORTING AN OVERBRIDGE RELATED ISSUE!

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

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).

• 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).

First, download and install the latest version of the operating system for your Elektron device. You can download it here. For more information on how to install the operating system, please see the User Manual for your device.

INSTALLING OVERBRIDGE ON WINDOWS

Download the latest version of Overbridge for Windows. You can download it here.

1. Uninstall any earlier version of Overbridge from your computer.

2. Restart the computer.

3. Disconnect all your Elektron devices from the computer.

4. Run the Overbridge Installer you downloaded and follow the on-screen instructions. It installs ASIO drivers, Windows WDM drivers, Engine, Overbridge Control Panel, VST Plugins, and Standalone applications. If needed, enter your administrator password in order to install new software on your computer.

5. Restart the computer after the installation has finished.

6. Connect your devices and power them on.

7. Start your devices' plugins, either standalone or in a daw.

If Windows shows a plug-and-play window during the installation (or after you have connected your devices), then click No if it wants to search Windows Update for drivers.

INSTALLING OVERBRIDGE ON macOS

Download the latest version of Overbridge for macOS. You can download it here.

1. Disconnect all your Elektron devices from the computer.

2. Double click the Overbridge dmg-file you downloaded to mount it.

3. Uninstall any earlier version of Overbridge from your computer.

4. Restart the computer.

5. Double click the pkg-file to start the installation process.

6. Restart the computer after the installation has finished.

7. Connect your devices and power them on.
   This will install Core Audio drivers, HAL drivers, Engine, Overbridge Control Panel, VST/AU Plugins, and Standalone applications.

Please note:

In macOS 10.13 High Sierra, the Overbridge driver software must be explicitly allowed to load in the Security & Privacy pane in macOS System Preferences.

1. Download and install Overbridge.

2. Restart the computer, and then open System Preferences (from Apple menu at top left corner of display).

3. Click Security & Privacy in the System Preferences window.

4. Click Allow on the “Elektron Music Machines MAV” entry within 30 minutes of the Overbridge installation.

For more information please see this article.

Also, in macOS 10.14 Mojave and above, you need to allow microphone permissions for the stand-alone version of Overbridge.

When you try to start Overbridge Engine, the following popup may appear:

The reasons for this can be:

• Overbridge Engine is already running correctly, and you tried to start it again. Always check the system tray for the Overbridge Engine icon to make sure it is not already running.

• Overbridge Engine is not visible in the system tray, but there is already an Overbridge Engine process running somewhere. The easiest solution to this is to restart the computer. After the restart, the system tray icon should be visible if you configured the automatic start of the Overbridge Engine in the Overbridge Control Panel. If it is not configured to start automatically, you need to start Overbridge Engine manually .

• The computer is running another application that use port 46000. Overbridge needs to use this port for communication between Overbridge Engine and the plugins. To solve this, quit the other application that use 46000.
  
  To find out what applications that use the port, please do the following:
  
  macOS
  1. Press CMD + SPACE, and then type “terminal”, and then press ENTER.
  2. Type the following in the terminal: “sudo lsof -PiTCP -sTCP:LISTEN”
  

  
  WINDOWS
  1. Press the “WINDOWS” key on your keyboard and then type “cmd”, then choose “Run as Administrator” for “Command Prompt”.
  2. Type the following at the command prompt: “netstat -abno -p tcp”
  

• Another user is logged in to the same computer, and the other user is running an instance of Engine or is running another application that is using port 46000. To solve this, log out the other user, or log in as the other user and quit Overbridge Engine or quit the application that is using port 46000.
  
  At the moment, it is not possible to configure Overbridge Engine to use another port than 46000.

If the Overbridge Engine does not recognize your device on macOS, first follow these steps:

1. Ensure you have the most recent version of Overbridge installed. 
2. Ensure your Elektron device has the latest OS version installed.
3. Ensure your Elektron device has been set to Overbridge mode in SETTINGS > SYSTEM > USB CONFIG.
4. Verify that the USB cable is securely and correctly connected to both the Elektron device and your computer. Connecting to a dedicated USB port is recommended.

In case the issue persists after following these steps, it is most likely that the Overbridge driver is still blocked in macOS Security & Privacy settings. Follow the instructions below to unblock the driver.

UNBLOCKING THE DRIVER (macOS 10.13 High Sierra to macOS 10.12 Monterey)

1. Launch the Overbridge Engine. It typically starts automatically when your Mac starts up unless this has been manually disabled in the Overbridge Control Panel. Look for the Overbridge Engine icon (Elektron logo) in the macOS menu bar and click on it. If your Elektron device isn't visible in the Overbridge Engine interface, proceed with the following troubleshooting steps:

2. Reboot your computer. This is important because the option to unblock a driver is only available for 30 minutes after the Elektron device has been connected. (Note: If you're using macOS 11 Big Sur or 12 Monterey, you don't need to do this step.)

3. After rebooting, open 'System Preferences' and navigate to 'Security & Privacy'.

4. Scroll to the bottom of the 'Security & Privacy' section. Here, you'll likely find a notification stating that the Elektron driver is blocked and requires permission to run:
   

5. Click the 'Allow' button to unblock the driver.

6. Now, open your DAW and check if the Elektron device establishes a connection to the VST/AU/AAX Overbridge plugin. Alternatively, you can open the standalone version/s of the Overbridge plugin/s to verify the connection.

UNBLOCKING THE DRIVER (macOS 13 Ventura or later)

1. When the Overbridge installation has finished, you should see a popup telling you that the Overbridge driver (system extension) was blocked. Click on Open System Settings in this popup, or choose Apple menu > System settings > Privacy & Security to get to where the driver can be allowed:
   
   
2. Here, the Overbridge Engine should show up as blocked (see screenshot below). Click the Allow button to unblock the driver.
   
   
   
3. After allowing the Overbridge driver, you should see a confirmation popup indicating that the Overbridge installation has been successful:
   
   

If the dialog box is still not showing or the allow button is not clickable it can be because of macOS security features that don't allow some software that can manipulate the mouse, keyboard clicks or screen sharing to be active. Examples of software that causes this behavior includes:

macOS Screen Sharing, Apple Remote Desktop, VNC, TeamViewer, MagicPrefs, BetterTouchTool, Synergy, Screens, Share Mouse

If you cant see the dialog box, try to uninstall this software.

Sometimes, some keyboards, mice, Wacom tablets or MIDI keyboards/devices might also need to be unplugged to solve this issue.

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/.

WINDOWS

If you experience issues while installing Overbridge on Windows, we would like you to attach a log file of the installation process to the support ticket you create so that we can get some more information about what is not working properly. The Overbridge installer produces a log file in your appdata directory. The name of the install logfile is “overbridge_install_log.txt”.

To navigate to your appdata directory, Press the WINDOWS key and type “%appdata%”, and then press enter. You should find a file named “overbridge_install_log.txt” in this folder. Attach this file to the support ticket.

In case you cannot find the installation log in that folder, please perform the installation process to produce a log file by taking the following steps:

1. Open a command prompt. Press the “WINDOWS” key on your keyboard and then type “cmd”, then choose “Run as Administrator” for “Command Prompt”.

2. In the Command Prompt window, navigate to the place where you have unpacked the Overbridge zip.

3. Type msiexec /i "C:\MyPackage\Example.msi" /L*V "C:\log\example.log" to start the intaller
   The path to the msi should point to the Overbridge installer .msi file and the last argument to the above command needs to point to a folder that exists. After the installer is finished you should have a file in the same location as the installer.

4. Attach the file to the support ticket. in the example above it should be in "C:\log\example.log".

macOS

macOS logs for all installations are collected in a single file for all applications. This file is located in /var/log/install.log. Attach this file to the support ticket.

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

PREREQUISITES

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

• Install the latest version of Overbridge. Available for download here.

COMPUTER OS

• macOS 10.12, 10.13, 10.14, 10.15, 11, 12, or 13 (latest update) - Overbridge includes native support for Apple Silicon M1/M2 hardware

• Windows 10 or Windows 11 (latest Service Pack)

COMPUTER HARDWARE

• At least Intel Core i5 CPU. Ultra-Low Power CPUs like the Intel U-Series or Y-Series are generally not recommended.

• 8GB of RAM

• OpenGL 3.2 capable GPU

• A 1280 x 768 pixels resolution monitor

• At least 250 MB free hard drive space

• A dedicated USB host port for each connected Overbridge-supported Elektron device is preferable to minimize problems with both connectivity and performance. If you want to connect multiple Elektron instruments to a computer host with only one USB controller, a high-quality hub, such as the Elektron Overhub, should be used.

RECOMMENDED DAWS

• Ableton Live 10 or 11

• Logic Pro

• Bitwig

• Studio One

• Reason

• Pro Tools (10 and later)

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 are experiencing that Overbridge or Transfer crashes on Windows it will be easier to see what caused the problem if you can provide a memory dump when you open a support ticket at Elektron. When memory dumps are enabled, they will be created in a specific location on your computer if Overbridge or Transfer crashes. This guide describes how to enable memory dumps on Windows and where you can find them.

ENABLING AND LOCATING MEMORY DUMPS

1. Download the file “enable_full_memory_dump.bat” that is attached to this article.

2. Press the “Windows” key on your keyboard and type “cmd”, then choose “Run as Administrator” for “Command Prompt”.

3. Press “Yes” on the User Account Control popup.

4. In the Command Prompt window, navigate to the directory to where you saved the “enable_full_memory_dump.bat” file. For example, C:\Users\*UserName*\Downloads
   If you don't know how to change directory, make an internet search with the search phrase “Change directory in cmd”.

5. Type “enable_full_memory_dump.bat” to run the script, and then press the “Enter” key. The output from running the script will look something like this:
   c:\Users\*UserName*\Downloads>echo off
A subdirectory or file C:\Users\*UserName*\AppData\Local\CrashDumps already exists.
Your memory dumps will be created in "C:\Users\*UserName*\AppData\Local\CrashDumps"
The operation completed successfully.
The operation completed successfully.
The operation completed successfully.

After completing the above steps, you should try to reproduce the crash. After the crash, there should be a memory dump file in the location pointed out in step 5 above. Make sure to attach this to your support ticket.

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.

The USB 3.0 specification requires that it must be fully backward compatible with USB 2.0 devices. However, not all USB 3.0 ports or the computers they are connected to achieves this USB 2.0 backward compatibility properly. This could be a problem that causes your device to not be visible in Overbridge Engine.

To solve this problem, you can try the following:

• It is not uncommon to have both USB 3.0 and USB 2.0 ports on the same computer. These might also use different USB host controller chipsets. Try moving your Elektron device to a different USB port on your computer.

• Connecting your Elektron device to a USB 3.0 port using a USB 2.0 hub can be a possible workaround for any issues you encounter when using a USB 3.0 port. Elektron Overhub comes with both a USB 2.0 and a USB 3.0 cable. If you use the USB 2.0 cable, the Overhub effectively acts as a USB 2.0 hub. 

• Try another USB cable. Good quality USB cables are less prone to introduce problems.