Tips for Optimizing Your PC for a DAW

Using a computer to produce music means that some basic optimizations to your system are necessary to avoid hiccups and stutters. We have listed some basic steps that could improve your computer’s performance.

1. Some seemingly basic programs, such as web browsers, can eat up A LOT of CPU. Make sure to shut down your web browser and all other unnecessary background programs while working with audio.

2. You can use advanced computer monitoring applications such as Open Hardware Monitor to monitor your computer in detail. This will allow you to figure out if certain applications are hogging your CPU and resources.

3. Disable any unnecessary apps from starting up with your system using the Task Manager (shortcut: CTRL+ALT+DELETE). Open the “Startup” tab and disable all programs that you do not need to run in the background. Using a software like AVG’s TuneUp will help ensure your system is running at optimal performance.

4. When playing back projects with audio located on a slow hard drive, dropouts are possible. Consider investing in an SSD drive or a fast M.2 NVMe drive.

5. Always use a commercial ASIO soundcard made by a reputable brand like Focusrite. Never use MME or WASAPI drivers. If you need to use your laptop’s built-in sound card,  ASIO4ALL is a much better driver than Window’s MME or WASAPI. However, you will probably still have latency issues even with ASIO4ALL and the audio will be low-quality because this is determined by your hardware. 

6. If you experience dropouts during audio playback, consider increasing the audio buffer size in the software control panel of your audio interface. This is usually accessible outside of SoundBridge, however you can open it within SoundBridge if you click “Control Panel” in Preferences -> Audio. Increasing the buffer size will increase the latency of playback, but it will put less strain on your CPU.

7. If your operating system has not been re-installed in a long time, re-install it to remove potential clutter and unnecessary programs eating up your resources. This solution is the most effective one. Starting with a freshly installed operating system and keeping it clutter-free moving forward will ensure that you experience the least amount of issues. When starting fresh consider using websites like Ninite to install all of the necessary programs and avoid forceware.

How do I make RitMix function in Ableton on macOS Catalina?

Follow these steps:

1. Close Ableton Live

2. Delete the RitMix.vst located in the folder /Library/Audio/Plug-Ins/VST if it already exists in that location

3. Delete the RitMix.vst3 located in the folder /Library/Audio/Plug-Ins/VST3 if it already exists in that location

4. Delete the RitMix folder located in /Documents (make sure you back up any of your custom Kits contained in there)

5. Delete (or just move to have a backup) the file Preferences.cfg located in:

Users/[username]/Library/Preferences/Ableton/Live x.x.x/

Note: The user “Library” folder is a hidden folder… To view it, do the following…
– Open Finder
– Click on the Go in the menu bar
– Press and hold the “Alt/Option” key
– Click on the “Library” after it appears in the drop-down menu

(Deleting this file will reset your Ableton Live to its defaults)

6. Install RitMix 1.08

7. Launch Ableton Live

8. In Ableton’s Preferences > Plug-ins section enable these two options:

“Use VST2 Plug-In System Folders”
“Use VST3 Plug-In System Folders”

After you do this, Ableton Live should re-scan plugins automatically and show RitMix and other plug-ins in its browser.


The Sample "Loop" button does not work in RitMix. How do I fix this?

If you are having problems with the Sample “Loop” functionality in RitMix, increase your audio driver’s buffer size to 512 samples or more.

How can I reduce latency in my project?
SoundBridge has audio preferences for selecting the size of the buffer it will use for input and playback. Type “p” to open the preferences window or go to options —> preferences.

Here you will find the sliders for buffer size.
A smaller buffer size yields less latency but higher CPU.
A larger buffer size yields more latency but less CPU.
The “Use Recommended Buffer Size” button will set these sliders at calculated optimal buffer sizes based on your current driver setup.

If you cannot resolve your latency issue by changing these settings, consider switching to a higher quality sound card and/or driver.

The parameters of SoundBridge look tiny, how do I fix this?
Please go to preferences -:> GUI and scale the interface by 25% until the software fits comfortably on your screen. Scaling requires you to restart the software.
How can I reduce my CPU usage in SoundBridge?
There are several actions you could take to improve CPU usage. The first recommended action is to check the status of our “Multi-Core Support” option in preferences. Type “p” to open preferences or go to options —> preferences.

If “Multi-Core Support” is enabled and your CPU issue is not resolved, consider using our freeze tool. The freeze tool will allow you to render channels to new audio tracks or “In Place” so there is not as much processing going on during playback.

If your CPU issue persists, consider using a higher quality soundcard and/or driver and closing any other programs that may be open while you are using SoundBridge.

How do I send MIDI out of SoundBridge?

Make sure your MIDI output device (USB, software MIDI bridge, or ASIO sound-card with MIDI output) is connected or installed before opening SoundBridge.

  • Launch SoundBridge.
  • Create a MIDI track and import, record, or draw-in your MIDI sequence.
  • Open the main mixer by pressing Tab on the keyboard.

Select the MIDI output device from the MIDI Out combo box located on the mixer channel of the corresponding MIDI track and press Play.

The recorded MIDI information from the MIDI track will be sent to the MIDI Output device.

How do I use USB MIDI controllers with SoundBridge?
Before opening SoundBridge, make sure the USB MIDI controllers are plugged into your computer.

The controller’s ID will display in the combo-box located on the MIDI tracks.

If the MIDI controller is a piano keyboard, select it from this combo box, load a VST instrument on to the track, and start playing.

Please reference the MIDI MAPPING chapter in the built-in tutorials to learn how to map MIDI CC articulations to control SoundBridge and plug-in parameters.

How do I add VSTs to SoundBridge?
First, find the location of the plugin file on your hard drive. Plugin companies usually ask where you want to save the plugin (.dll, .vst, component) in the beginning of their installer. If you’re not sure where it saved to, try searching these locations below… plugins often default to saving in these locations.


C:\Program Files\VSTPlugins
C:\Program Files\Steinberg\VSTPlugins
C:\Program Files\Common Files\VST2
C:\Program Files\Common Files\Steinberg\VST2
32-bit plug-ins on 64-bit Windows: C:\Program Files (x86)\Steinberg\VstPlugins


Hard disk // Library // Audio // Plug-Ins // VST

Hard disk // Users // Username // Library // Audio // Plug-Ins // VST

After you’ve found the plugin location…

  • Open SoundBridge.
  • Click “p” to open the preferences window or go to options –> preferences.
  • Go to the “VST” tab.
  • Click “Add Directory”.

A browser will appear in which you can tell SoundBridge where the plugin file is located. Select the folder containing it, and click “Select Folder”. Then click “Ok”.

Click the “Refresh Plugins” button at the top of the file browser to tell SoundBridge a new directory has been added. It may take a moment to refresh. When it does, you will have the newly added VST available in the VST partition of the file browser for use.

If you are having an issue involving a VST that you cannot resolve with our troubleshooting tools, please email us at support@soundbridge.io.

I don't have my VSTs installed on all of my computers. How can I ensure my progress on them won't be lost when transfering the project?
When you open your work on a computer system that does not have the VSTs you were using installed, you will be prompted with a “missing VSTs” dialogue. Here you will have the option to skip missing plugins (load the project without them) or to go into preferences and find them.

If you have to load the project without them, we suggest you back up their settings and automation data in the project that contains them (ie: saving the patch, exporting MIDI, freezing the output to an audio track). Or, save the current project “as” instead.

Is SoundBridge available for Mac?
Yes indeed!
Does SoundBridge require Internet access?
SoundBridge requires internet access for online activation once a month if you select “Remember Me”.
Where is the RitMix VST installed?
Check your browser’s download directory to find the installer executable.

In the installer, please pay attention to this screen:
Make sure you choose a directory you can remember, otherwise this is the default location for Windows.
On Windows, VST2 & VST3 are combined into one .dll file. You are looking for the RitMix.dll
For Mac, VST2 is stored in: Hard disk // Library // Audio // Plug-Ins // VST
VST3 is stored in: Hard disk // Library // Audio // Plug-Ins // VST3
Clock Setback Detected

Clock Setback Detected

SoundBridge and RitMix uses a licensing manager called Reprise Licensing Manager (RLM) by Reprise Software.

RLM detects windback by looking for future-dated files in system directories, and examining the accessed and modified timestamps on all the files there. In many cases just running the system for a little while with the correct date will access the future-dated files and the problem will clear itself. Often a reboot helps too.

  1. Remove the license.lic file from your SoundBridge folder within My Documents.
  2. Please check the system date and time on your computer and ensure that it is correct for your current location.
  3. Start up SoundBridge

If it doesn’t clear itself, you will have to go into those directories and look for the offending files, and set them to the current time by accessing them. Below are the directions for how to do this on Mac and PC.

Resolve Date/Time Function Issues

  • Mac: 
    • Find Files. Within a terminal window, from anywhere, please type the following:
      ls -ltrcH /etc
      ls -ltrcH /var/log
      ls -ltruH /etc
      ls -ltruH /var/log

      This will identify the time and date stamp on these files.

    • Corrective Action. If there are any files with with a date later than today, please run this command on those files displaying a future date from a terminal window. You will need to be in the /etc/ and /var/log/ folders
      sudo touch filename
    • Verify. After executing the above, re-run these commands to ensure the timestamps are updated correctly:
      ls -ltrcH /var/log

      This will show that the future-dated files now have the current date’s timestamp and SoundBridge should be able to run.

      Start up SoundBridge.

  • Windows: 
    On Windows, this error message is related to file timestamps on your system that are not current. RLM may be detecting clock-windback and not honoring expiring licenses.

    • Find Files. You can find the offending file(s) in a Command Window with these commands:
      dir /od /ta C:\Windows (displays and sorts on last access time)


      dir /od /tw C:\Windows (displays and sorts on last write time)

      Copy and paste the output from those commands into a text file to help see if any files have a future timestamp that can be corrected.

    • Corrective Action. If your output shows a future date, perform the following commands to modify the timestamps appropriately for the license manager to work. You can run these commands in a Command Prompt (or place the contents in a .bat file and run it from the command prompt).You will need to update these sample commands with the actual file name of each future-dated file. Ensure that you use the correct command for the future-dated files as some files are future-dated based on ‘last write time’ and some are ‘last access time’. 
      powershell $(Get-Item C:\Windows\SampleDirectoryName).lastwritetime=$(Get-Date) OR
      powershell $(Get-Item C:\Windows\SampleFileName.dll).lastaccesstime=$(Get-Date) OR
      powershell $(Get-Item C:\Windows\SampleFileName.exe).lastaccesstime=$(Get-Date)
    • Example. Below are examples of the commands run for future-dated files from one customer:
      powershell $(Get-Item C:\Windows\CSC).lastaccesstime=$(Get-Date)
      powershell $(Get-Item C:\Windows\CSC).lastwritetime=$(Get-Date)
      powershell $(Get-Item C:\Windows\RtlExUpd.dll).lastaccesstime=$(Get-Date)
      powershell $(Get-Item C:\Windows\SwUSB.exe).lastaccesstime=$(Get-Date)
      powershell $(Get-Item C:\Windows\runSW.exe).lastaccesstime=$(Get-Date)
      powershell $(Get-Item C:\Windows\PidVid_List.txt).lastaccesstime=$(Get-Date)
    • Verify. After executing the above, re-run these commands to ensure the timestamps are updated correctly:
      dir /od /ta C:\Windows
      dir /od /tw C:\Windows

      If the output does not show any files with a timestamp greater than today’s date, please try to start SoundBridge or RitMix.

Experiencing a crash on Startup?

Supporting the vast supply of third-party VSTs and Windows Audio Drivers is quite a task, but without your feedback we don’t know what to fix.

If you come across a specific VST or Windows Audio Driver that is in compatible with SoundBridge, please write us with a URL to the corporate specs with a brief explanation of the problem at: support@soundbridge.io

If you’re having a crash a startup, it’s probably due to a bad VST or Windows Audio Driver. We can clear the cache memory to narrow down the issue and decide what’s causing the crash.

Please follow these directions in order for Windows and Mac.

On Windows, you should do Step 1 first, then process to Step 2.

On Mac, there is just one step because there are no third-party audio drivers involved.


Step 1:

Search for regedit in the Windows Search Bar.

Go to: HKEY_CURRENT_USER\Software\SoundBridge\SoundBridge\Preferences

Deleting this folder will clear the audio device preferences and the default device will be used on the next run.

First, delete this folder and run SoundBridge.

If you are able to enter the software, the cash was probably due to an incompatible audio driver. In this case, please report the audio driver to: support@soundbridge.io with a brief description of the situation.

If you are still experiencing a crash, please proceed to Step 2.

Step 2: 

Go to: HKEY_CURRENT_USER\Software\SoundBridge\SoundBridge\

Deleting this folder will delete the entire VST cache memory and remove any history of audio drivers. Deleting this will also reset SoundBridge’s preferences to default.

Delete this folder and run SoundBridge.

If you are able to enter the software, the cash was probably due to an incompatible VST. In this case, please reach out to support@soundbridge.io for the next steps.


Click the Desktop to bring up Finder toolbar.

Click on Go.

Hold down alt/option while the go drop-down menu is open.

Click on Library, which should be visible while holding down alt/option key on keyboard.

The Library folder will open. Find the folder named Preferences and open it.

In Preferences, folder find the file named com.soundbridge.SoundBridge.plist and delete it

Restart OSX

Run SoundBridge

If you are able to enter the software, the cash was probably due to an incompatible VST. In this case, please reach out to support@soundbridge.io for the next steps.

RitMix's loop functionality is not working in FL Studio. How do I fix it?

To fix this, please perform the following steps:

  1. Click on the VST wrapper Settings button that is located in the upper left of RitMix.
  2. In the Processing section, make sure to enable the Use fixed size buffers option.
  3. Open the More drop-down menu and tick the Process maximum buffer size option.
Forcing the Intel binary to run on Apple silicon
SoundBridge does not scan any plugins after the update for Apple Silicon-powered computers.

Since we introduced native Apple Silicon support, SoundBRidge version 2.2.1 BETA now contains both the old Intel and the new Apple Silicon binaries.

The new 2.2.1 BETA version does not recognize any of the plugins that worked on the previous Intel-only version of SoundBridge.

To use those plugins with SoundBridge 2.2.1 BETA on an Apple Silicon-powered computer, run SoundBrige using Rosetta.

This will force your macOS to run the Intel-based version using Rosetta on your Apple Silicon-powered computer:

    1. Right-click the SoundBridge icon.
    2. Click on “Get Info”.
    3. Check the “Open using Rosetta” checkbox.
    4. Close the Get Info dialog and run SoundBridge.

Mac arm64 and x86_64 architecture support explained.

SoundBridge now fully supports Apple Silicon with the release of version 2.2.1 BETA.

Heads-up: Only VSTs compiled for arm64 will work in the arm64 version, and 64-bit VSTs compiled for x86_64 will only work in the x86_64 version. 32-bit VSTs are not supported on Mac at all.

That said, M1/M2 users can go between the two architectures from a single installation of SoundBridge.

M1/M2 users can easily switch back to x86_64 by right-clicking the SoundBridge.app located in the Applications folder, selecting “Get Info,” and checking “Open using Rosetta” under the “General” tab. This will open SB in the old x86_64 architecture, so you can easily access the plugins you need.

The splash screen will inform you of the architecture you’re running.