Source-Nexus Troubleshooting
The following page contains a list of error messages and common issues related to Source-Nexus I/O, Source-Nexus Review and Source-Nexus Control Panel.
If you run into any issues not listed on this website, including error messages, please contact the support team.
Sound Troubleshooting
Listed below are some of the most common problems faced by users using the application. Before trying any of the solutions below, make sure you download and install the latest version of Source-Nexus I/O.
If the issues arise when using Source-Nexus I/O together with Source-Connect, check out the Source-Connect troubleshooting page and go through the Sound Troubleshooting section.
Issue | Reference Article |
Audio is not sent or received in Source-Nexus I/O |
If you are experiencing issues with the Nexus I/O plugin not sending or receiving audio, read through the following article for instructions. If you are on Logic Pro and you are not getting any audio from Source-Connect via Source-Nexus, please read through this article. |
Cannot send stereo in Zoom using Source-Nexus I/O | Read through this article to learn how to send stereo audio into Zoom using Source-Nexus I/O. |
Clicks in the audio | If you are hearing clicking when using Source-Nexus I/O, the problem might be related to clocking issues (see below "Clocking issues" section). Clocking issues are caused by sample rate conflicts. Make sure that your hardware devices have the same sample rate (this applies to any devices, including webcams, that you have connected while you are using Source-Connect). If you are a Mac user, check the Audio MIDI Setup to make sure all devices are set to the same sample rate your session has. Also, make sure the audio device input and output are not muted on the Audio MIDI Setup. If you are on Windows, go to Sounds > Recording/Playback > Device > Advanced instead. If the above does not solve the issue, try creating new drivers and using them instead of the default ones (Source-Nexus A and Source-Nexus B). Check out this article for Mac and this article for Windows. If you are on macOS Monterey or higher, make sure your issue is not related to Apple's CoreAudio problems. |
Clocking issues | This is a link to a tips and tricks for Mac for all Source Elements products. This is the same article, but for Windows instead. Specifically, tip 2 expands on understanding digital clocking problems. |
DAW not loading Source-Nexus plugins / blacklisted Source-Nexus plugins | If you are having issues with Source-Nexus not showing up on your DAW, you can follow the instructions in any of these articles: Ableton Live, Adobe Audition, Cubase and Nuendo, Cubase and Nuendo (Rosetta), Logic Pro X, Pro Tools, Reaper, Studio One, Cakewalk Sonar for Windows. If your DAW is not in the list, let us know, and we will add troubleshooting instructions. |
Devices missing after a reboot | If you have rebooted your device, and some or all of the Source-Nexus I/O devices created using Source-Nexus Control Panel are not available, go through this article. |
Deleted Source-Nexus I/O device not removed from your DAW after uninstalling |
If you are still seeing the plugin in your DAW after using the uninstaller, make sure to check the plugins folder and manually removing any Source-Nexus folder. For Pro Tools specifically, check both the Avid plugins folder to make sure it is not still there. Also check the Slate folder if the problem persists. |
Increasing audio latency or drift in Logic Pro X | This can be caused by the plugin latency compensation. Make sure plugin latency compensation is set to "Off" in Logic Pro X -> Preferences -> Audio -> General. |
Source-Nexus I/O 1.3 gets stuck and causes Pro Tools to crash | In order to resolve this issue, try trashing your Pro Tools preferences. For Mac, go to ~/Library/Preferences/Avid and delete the “Pro Tools” folder. For Windows, go to %appdata% > Avid and delete the Pro Tools folder. |
Dropouts related to Apple's CoreAudio issues | Since the release of Apple’s Monterey OS, they have had issues with their CoreAudio process, when the system is under moderately high memory (RAM) usage. From numerous reports and our own testing, it seems this issue is especially apparent on the M-series Apple Silicon chips (M1, M2, M3). |
List of Source-Nexus Alerts, Error Messages, Notices and Warnings
Product | Message | Reference Article |
Source-Nexus Control Panel | Cannot get number of channels for device. Failed to get device stream. | Cannot get the number of channels error message. |
Source-Nexus Control Panel | Cannot add a device. Failed to get box ID. | Failed to get box ID error message. |
Source-Nexus I/O | DSP Mode has been automatically enabled for one or more tracks to preserve Low Latency Monitoring for the entire signal path. | DSP Mode warning in Pro Tools. |
Source-Nexus I/O | Fatal Error - Source-Nexus 1.3. Source-Nexus could not be loaded. Please contact the software publisher using this software. | Fatal Source-Nexus I/O 1.3 error message. |
Source-Neuxs Suite | Source-Neuxs Suite Setup Wizard ended prematurely. Source-Nexus Suite Setup Wizard ended prematurely because of an error. Your system has not been modified. To install this program at a later time, run Setup Wizard again. Click the Finish button to exit the Setup Wizard. |
Source-Nexus Suite ended prematurely error message |
Source-Nexus I/O | Source-Nexus.vst3 Can't run because Pace License Support hasn't been installed, OS error 0xc0000135. The code execution cannot proceed because libxml2.dll was not found. Reinstalling the program may fix this problem. |
Reaper error message for Source-Nexus.vst3 when iLok License Manager is not installed. |
DAWs | The following plug-ins failed to load because they are not valid 64 bit AAX plug-ins: Source-Nexus.axxplugin. | The following plug-ins failed to load error message. |
All Products | The installation failed. The installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance. | The installation failed error message. |
Source-Nexus Gateway | Connection Error: Unable to connect to media server , this is likely due to an issue with your firewall. Please see the following support article for details and configuration information. | Connection Error: Unable to connect to media server on Source-Nexus Gateway |