Category: Presonus

  • Pro-Sound Guitar Lessons on Zoom: Routing Hardware and Backing Tracks

    Pro-Sound Guitar Lessons on Zoom: Routing Hardware and Backing Tracks

    Remote collaboration presents unique technical challenges, especially for musicians who rely on high-quality audio. A client, a dedicated guitar student, was frustrated because while his teacher sounded great on Zoom, his own guitar signal was thin and muffled, relying only on his webcam microphone.

    The goal was clear: get his existing guitar rig—pedals and all—running through his MOTU M4 audio interface and into Zoom, perfectly mixed with his voice and a backing track. Achieving this on a Windows PC requires expert setup of a virtual mixer. This is a complex but entirely solvable audio routing problem, exactly what Audio Support specialises in.

    The client wanted to send a professional-quality, live guitar signal—complete with his preferred multi-effects pedal sound—to his teacher over Zoom. His setup was a Windows PC tower and a MOTU M4 audio interface.

    The hurdles were twofold:

    1. Initial connection issues where the M4 was not being recognised by the PC.
    2. The complex task of routing three separate audio sources (Guitar/Mic, Backing Track, and Zoom Return) into one neat stream for the teacher, while maintaining a clear headphone mix for himself.

    The first step was to establish a rock-solid connection for the MOTU M4.

    1. Hardware Connection: The physical signal path was correct: Guitar into the multi-effects pedal, and the pedal’s output into Input 1 (or 1/2) of the MOTU M4.
    2. USB Power Issue: The PC was not detecting the M4 correctly. The interface’s own hardware display was showing that no sample rate or buffer size was selectable. After quickly checking and updating drivers and firmware, the issue was traced to the physical USB port. The front USB sockets on the PC tower were not delivering sufficient, stable power to the M4.
    3. The Fix: We switched the M4 connection to a rear USB port on the motherboard. This instantly provided the required power, and the MOTU M4 was correctly recognised by Windows, allowing the drivers to install and function. This is a common but easily missed issue on Windows desktop PCs.

    Once the M4 was stable, we moved on to routing using the virtual mixing software.

    To mix the guitar, microphone, and backing track for the teacher while controlling the monitoring levels, we needed a virtual mixer: VoiceMeeter Banana.

    We installed the software and restarted the PC. The routing plan was set up as follows:

    Audio SourceVoiceMeeter InputUser Monitoring (A1)Teacher/Zoom Send (B1)
    Guitar & Mic (via MOTU M4)Hardware Input 1 (MOTU Input 1/2)A1 SelectedB1 Selected
    Backing Track (Spotify/YouTube)Virtual Input (Aux)A1 SelectedB1 Selected
    Zoom Return (Teacher’s Voice)Virtual Input (Main VAIO)A1 SelectedB1 NOT Selected

    Crucially, the following adjustments were made:

    • Hardware Out (A1): We set the main hardware output (A1) to the MOTU M4’s output device (WDM: MOTU M4 1/2) so the client heard everything through his headphones.
    • Mono for Guitar/Mic: On Hardware Input 1, we pressed the Mono button. This ensured the guitar (likely on one channel) and the mic (if on the other) were merged and heard equally in both headphone ears.
    • Windows Default Playback: We set the Windows default sound output to Voicemeeter Aux Input so that backing tracks (e.g., Spotify, YouTube) fed into the specific virtual channel strip.
    • Zoom Settings: The client’s Zoom microphone input was set to VoiceMeeter Output (B1) to send the perfectly mixed blend of Guitar, Mic, and Backing Track to the teacher.
    • Feedback Prevention: The Zoom return (teacher’s voice) was routed only to A1 (client’s headphones) and critically NOT to B1, which would have created an immediate and destructive feedback loop.

    We ran a full test recording using a separate DAW (PreSonus Studio One) and then connected over Zoom to confirm the teacher could hear all three elements cleanly, and the client had perfect monitoring, including his own audio (via the M4’s direct monitoring feature) and the Zoom return.

    ComponentSetting/ActionPurpose
    MOTU M4 ConnectionConnect to a Rear USB Port on your PC tower.Solved the power/recognition issue for the interface.
    MOTU Signal PathGuitar FX Pedal Output $\rightarrow$ MOTU M4 Input 1 (or 1/2).Sends your guitar signal into the computer.
    Install VoiceMeeterDownload and install VoiceMeeter Banana (must reboot PC).This is your master virtual mixer.
    VM Hardware Out (A1)Top right of VoiceMeeter, set A1 to WDM: MOTU M4 1/2.Your headphones will now hear the mix from VoiceMeeter.
    VM Hardware Input 1Top left, set the input to MOTU M4 Input 1-2.Brings your live Guitar/Mic signal into the mixer.
    VM Hardware Input 1Press the MONO button on this strip.Prevents your guitar (or mic) from being split to one ear.
    VM Aux Input SetupSet the Windows default sound output (bottom right speaker icon) to VoiceMeeter Aux Input.All PC audio (Spotify, YouTube) is now routed to the Aux strip.
    VM Aux Input (Backing Track)Select A1 and B1 on this strip.A1 = You hear the backing track. B1 = Teacher hears the backing track.
    VM Guitar/Mic StripEnsure A1 and B1 are selected.A1 = You hear your guitar/mic. B1 = Teacher hears your guitar/mic.
    VM Virtual Input (Main VAIO)This strip controls the level of the Zoom Return (your teacher’s voice). Select A1 only.A1 = You hear your teacher. DO NOT select B1 to prevent feedback.
    Zoom Microphone SettingIn Zoom Audio Settings, set Microphone to VoiceMeeter Out (B1).Sends the mixed Guitar/Mic/Backing Track signal to your teacher.
    Zoom Speaker SettingIn Zoom Audio Settings, set Speaker to VoiceMeeter Input (VAIO).Routes the teacher’s voice into the Virtual Input strip for monitoring.

    The most important takeaway here is the importance of a holistic diagnosis. We couldn’t have successfully set up the complex software routing until we had solved the simple, underlying hardware problem of USB power. A faulty or underpowered port can make a high-quality interface look broken. Once the hardware was stable, the virtual mixer VoiceMeeter Banana became the perfect tool to combine multiple audio sources and send a high-quality, professional mix over a simple conferencing app.


    I help musicians and producers worldwide solve problems like this every day. If you’re struggling with audio routing between your hardware, software, and platforms like Zoom or OBS, I’ll help you find the real cause and get you back to creating.

    No automated tickets, no waiting queues — just one-to-one help from an experienced music technology specialist. I’ll connect to your system remotely, identify the issue, and guide you through the fix.

    Recent problems solved for real clients.

    Optimising Logic Pro CPU Usage for Large Orchestral Mixes

    Client’s Question

    Why does Logic Pro keep crashing when I add plugins to my tracks?

    Session Result

    CPU load drastically reduced; mix workflow stabilised via bus routing.

    Read Full Case Study Report: Pro-Sound Guitar Lessons on Zoom: Routing Hardware and Backing Tracks
    Preparing for a Studio Hardware Installation

    Client’s Question

    What cables do I need to connect my hardware synths to my mixer?

    Session Result

    Equipment audited, cable inventory confirmed, site visit planned.

    Read Full Case Study Report: Pro-Sound Guitar Lessons on Zoom: Routing Hardware and Backing Tracks
    Mono Microphone Only in Left Speaker Fix in Logic Pro

    Client’s Question

    Why is my mono mic input only coming out of the left speaker in Logic Pro?

    Session Result

    Mono input successfully centred by changing Logic Pro track format from Stereo to Mono.

    Read Full Case Study Report: Pro-Sound Guitar Lessons on Zoom: Routing Hardware and Backing Tracks
    Managing Native Instruments Komplete Libraries in Kontakt

    Client’s Question

    How do I hide unwanted libraries in the Kontakt side pane?

    Session Result

    Unused libraries hidden, visual clutter removed.

    Read Full Case Study Report: Pro-Sound Guitar Lessons on Zoom: Routing Hardware and Backing Tracks
  • PreSonus Audio Interface Not Connecting to Logic Pro: How to Fix Blocked Drivers in macOS Security

    PreSonus Audio Interface Not Connecting to Logic Pro: How to Fix Blocked Drivers in macOS Security

    Hi Paul. I tried to update the PreSonus Universal Control software to the latest version from my account on the PreSonus website, but now it’s not working, my Quantum audio interface isn’t connecting with Logic at all. Can you help please? – Chris

    I received the above message via the enquiry form on my website and arranged a time with Chris to connect for a remote support session.

    This issue turned out to be a simple one to resolve. After my client had installed the updates for his PreSonus Universal Control software, he had missed the 30-minute window to ‘Allow’ the OSX driver extensions to run in OSX’s Security Preferences. 

    PreSonus have published a guide on how to do this on their own website:

    I followed the instructions from PreSonus’ site and removed and reinstalled the driver. After installation, I went straight to the security preferences and allowed the system extension.

    Universal Control – audio driver system extension

    For the remainder of the session, I spent time with Chris making sure the rest of his Logic system was working properly. We checked over his plug-ins to make sure everything was loading correctly and I gave him some advice about which version of Kontakt was the right one to use with his version of Logic Pro.

    Categories: , , ,

    No automated tickets, no waiting queues — just one-to-one help from an experienced music technology specialist. I’ll connect to your system remotely, identify the issue, and guide you through the fix.

    Recent problems solved for real clients.

    Optimising Logic Pro CPU Usage for Large Orchestral Mixes

    Client’s Question

    Why does Logic Pro keep crashing when I add plugins to my tracks?

    Session Result

    CPU load drastically reduced; mix workflow stabilised via bus routing.

    Read Full Case Study Report: PreSonus Audio Interface Not Connecting to Logic Pro: How to Fix Blocked Drivers in macOS Security
    Preparing for a Studio Hardware Installation

    Client’s Question

    What cables do I need to connect my hardware synths to my mixer?

    Session Result

    Equipment audited, cable inventory confirmed, site visit planned.

    Read Full Case Study Report: PreSonus Audio Interface Not Connecting to Logic Pro: How to Fix Blocked Drivers in macOS Security
    Mono Microphone Only in Left Speaker Fix in Logic Pro

    Client’s Question

    Why is my mono mic input only coming out of the left speaker in Logic Pro?

    Session Result

    Mono input successfully centred by changing Logic Pro track format from Stereo to Mono.

    Read Full Case Study Report: PreSonus Audio Interface Not Connecting to Logic Pro: How to Fix Blocked Drivers in macOS Security
    Managing Native Instruments Komplete Libraries in Kontakt

    Client’s Question

    How do I hide unwanted libraries in the Kontakt side pane?

    Session Result

    Unused libraries hidden, visual clutter removed.

    Read Full Case Study Report: PreSonus Audio Interface Not Connecting to Logic Pro: How to Fix Blocked Drivers in macOS Security
  • I/O Effect Feedback Fix: Setting Up SPL Transient Designer in Logic Pro with PreSonus Universal Control

    I/O Effect Feedback Fix: Setting Up SPL Transient Designer in Logic Pro with PreSonus Universal Control

    Hi Audio Support. I’m trying to set up my SPL Transient Designer hardware unit to use as an effect in Logic. My audio interface is a Presonus 1810c. I want to be able to control the balance between processed and unprocessed sound and I need quick and easy access to this unit to use it like a plugin. I’ve tried so many times to get this right and I just can’t. All I’ve achieved so far is nasty feedback noises and frustration.

    Joe

    I received the above message from Joe via my enquiry form and we arranged a one-hour remote support session for the next day.

    Once the remote connection was established, Joe talked me through the current arrangement of his hardware and cabling and how he had set up his transient designer as a I/O effect in Logic. He showed me an example of how he wanted to use the transient designer and pointed out where it was behaving strangely.

    Joe and I spent a bit of time talking through all the connections and I initially couldn’t find anything wrong. The cabling seemed fine and his setup in Logic should be producing the desired result. However, I could see where the problem lay once we opened the Presonus Universal Control app that gave us access to the internal routing of the audio interface.

    The 1810c has routing options within the mixer software, which allows the user to set up custom mixes for each pair of physical stereo outputs on the interface. These custom mixes can be created by highlighting the Main, Mix 3/4 or Mix 5/6 buttons and adjusting the faders and mixer settings. I could see that in Joe’s setup, we were currently sending both the Stereo 1-2 and Stereo 3-4 outputs of Logic to the 1810c Main out. In order to get the setup working properly, we would need to set different mixes for Main and Mix 3/4 on the software mixer.

    I downloaded the 1810c manual from the Presonus website and skimmed through the relevant info on routing. I then set up the software mixer as shown in the pic below:

    For the Mix 3/4 setup, I reversed the mutes on the first two DAW (Logic) channels. DAW1 was muted and DAW 3 was unmuted. (The setup of Mix 5/6 wasn’t relevant at this point.)

    This meant that the Presonus physical outputs were now matching the outputs selected in Logic.

    I could see that the Presonus mixer settings were also responsible for the feedback Joe was experiencing. All the input channels were turned on with raised faders on each of the mixes. This meant that the output of the SPL would be feeding back into itself. Muting all the mixer inputs stopped this problem and Logic could be used to control input monitoring.

    We tested everything with a few loops running through the SPL. The transient designer sounded great and Joe was happy with his new setup. After the session, Joe was kind enough to leave me a nice review:

    Categories: , , , ,

    About the Author

    PAUL ANDREWS

    I’m the owner and lead technician for Audio Support, a small company based in London, UK that connects remotely with clients worldwide to help them with their music technology issues. I’ve run Audio Support since 2005 and in that time I’ve seen and solved thousands of recording studio problems. 

    Outside of Audio Support, I run music workshops at a local school, play bass in a 90s tribute function band and perform modular synth jams with friends on Twitch.


    Get support for similar problems: