I'm chasing my own tail here...... when trying to configure audio paths of software such as Voicemeeter, Virtual Audio Cable 4, ASIO4All, etc., should the Default Devices in Windows' sound control panel be locked down and never need to change, while wrestling with the above virtual devices?

I have a PreSonus 22 VSL USB audio interface, running mostly Cubase 10.5.
I also use and love a Sonuus i2m audio ---> MIDI USB interface that near-perfectly converts the audio signal from my Stratocaster into MIDI notes ...... despite its mono-only MIDI operation I have been ultra-happy with its incredible zero-latency throughput....... using it to play various VSTi's, it is tight and right on the fastest phrases. As a (fully polyphonic) USB audio interface, I couldn't ask for a

 

Hey, your post seems cut off.

I would say YES, you should be able to set those windows devices how you want them and other programs should see that and honor it... but see my issues later -hahah

Spoiler: here is my setup

I have my Windows devices set to 32-bit & 48k and uncheck "exclusive control".
I have "Realtek USB audio" (Realtek ALC4080).
Not to be confused with the regular old Realtek, this 'USB' version is known to have problems with bad audio, apparently from running on the USB bus or something. I assumed I'd end up buying another device for casual use. (I have a Presonus StudioLive AR-8 mixer for proper ASIO)

But as it turns out, the sound happens to be OK, and for casual use I use AsioLinkPro and select ASIO4ALL as the device, and ASIO4ALL uses the Realtek...
But I could not seem to get ASIO4ALL to take 24-bit.
It would just lock up trying to change the device in ASIO4ALL settings and I think the Realtek is demanding to be 32-bit.

So I just set Windows devices (Realtek) to 32-bit, and let ASIO4ALL choose them as it wants to.
I thought 32-bit might use more CPU or something, but it seems no problem, and I have low latency and good audio even with underclocking a bit and even with thermally throttling via ThrottleStop.

I like to keep AsioLinkPro running and allowing "multi-client" as it allows running various audio applications at once and then firing up DAWs or video editors work without glitching ASIO4ALL or anything as AsioLinkPro is already in control.

(All I have to do then is to open the Windows Sound settings - there is a handy link in AsioLinkPro - and set to "stereo" or "surround" types to record off movies. I love splitting out surround channels to discover how some movies have interesting uses, or to get pure audio tracks, etc)

Using straight Windows devices and firing up a programs that will use ASIO4ALL has given me problems ...
Not just that I can't listen to other audio playing until I arm a track,etc, but sometimes a delay in ASIO4ALL getting control, and sometimes failing to get access at all, settings getting changed, etc. On my system running AsioLinkPro is not a big deal.

I have used other virtual audio devices, and thought I would switch after not getting 24-bit setting in ASIO4All, but after trying a bunch, I just returned to AsioLinkPro + ASIO4ALL combo, as it does it so well.

Oh, and since Windows 10 & 11 like to present stupid audio settings pages, I use the old normal shortcut:
C:\Windows\System32\mmsys.cpl cpl sounds

 

Last edited: Aug 24, 2025 at 6:09 AM

Spoiler: Source: Grok KI

I totally get the frustration—configuring audio routing with virtual devices like Voicemeeter, VB-Cable, and ASIO4All can feel like a rabbit hole, especially when you're mixing in hardware interfaces like your PreSonus Studio 22 VSL and that awesome Sonuus i2M (which is indeed a gem for guitar-to-MIDI conversion). I'll break this down step-by-step to help you stabilize your setup without chasing your tail. The short answer to your core question is yes, you should aim to lock down the Windows Default Devices as much as possible and treat them as a stable "hub" while dynamically configuring the virtual devices/software around them. This minimizes conflicts and makes troubleshooting easier. Let's dive in.

Why Lock Down Windows Default Devices?
Windows' Sound Control Panel (search for "Sound settings" or right-click the speaker icon in the taskbar > Open Sound settings) manages the system's global audio I/O. Changing these defaults frequently can cause apps (like Cubase) to lose track of devices, leading to audio dropouts, latency spikes, or routing errors. Virtual audio cables (e.g., VB-Audio Virtual Cable) and software like Voicemeeter act as "bridges" between apps and hardware, so they should adapt to your fixed defaults rather than forcing you to tweak them constantly.

• Best Practice: Set your PreSonus Studio 22 VSL as the Default Device for both playback (output) and recording (input) in Windows. This makes it the system's "go-to" audio engine. Only change these if you're switching to a completely different physical setup (e.g., laptop speakers for non-music tasks).
  • Why the PreSonus? It's your main hardware interface with low-latency ASIO drivers, multi-channel support, and VSL (Virtual StudioLive) integration for Cubase. It handles your Sonuus i2M's output beautifully since the i2M appears as a USB audio device.
• Exceptions: If you need system sounds (e.g., notifications) to go to your PC's built-in speakers instead of the PreSonus, set a secondary default or use Voicemeeter's hardware out mixing to route them separately. But avoid flipping defaults mid-session.

Once locked, you configure virtual devices and software to route through these defaults. This creates a predictable flow: Hardware → Virtual Cables → Software (Cubase/Voicemeeter) → Back to Hardware.

Step-by-Step Configuration for Your Setup
Assuming you're on Windows 10 (as mentioned), with PreSonus drivers installed (via Universal Control software) and the Sonuus i2M plugged in. Download VB-Audio Virtual Cables (free version is fine for basics) and Voicemeeter Banana/Potato if you haven't already. ASIO4All is great for non-ASIO apps but use it sparingly—your PreSonus has native ASIO, so prioritize that in Cubase.

1. Set Windows Defaults (Lock This Down)

• Open Sound settings > Sound Control Panel.
• Playback tab: Select your PreSonus Studio 22 VSL as the default device (green checkmark). Set it to 44.1kHz or 48kHz sample rate (match Cubase's project settings for zero resampling issues).
• Recording tab: Select the PreSonus as default. Enable the Sonuus i2M as an additional input device if it's not already visible (it should show as "Sonuus i2M" or similar under USB audio devices).
• Test: Play a YouTube video or system sound—it should route through the PreSonus outputs (e.g., monitors/headphones connected to it).
• Pro Tip: In PreSonus Universal Control, set the mixer to "DAW" mode so Windows/Cubase audio bypasses the onboard mixer and goes straight to your DAW tracks.

2. Configure Virtual Audio Cables (VB-Cable)
VB-Cable creates virtual "wires" that let apps output to a virtual device, which then inputs to another app/hardware. Install VB-Cable (or VB-Audio Cable pack for multiple channels). Don't change Windows defaults here—these are additional devices that appear in the list.

• For Guitar-to-MIDI with Sonuus i2M:
  • The i2M converts your Strat's audio to MIDI data and sends it as a USB audio/MIDI stream. In Windows Recording tab, it should appear as an input device.
  • Route its output to a virtual cable: In your app (e.g., Cubase), set the i2M as the input for a MIDI track. For audio bleed (if any), route the i2M's audio output to a VB-Cable input.
  • Example Flow: Sonuus i2M (input in Windows) → VB-Cable (virtual output) → Cubase MIDI track → VSTi (e.g., synth) → PreSonus output.
  • Zero-latency tip: Since the i2M is already low-latency, keep buffer sizes low in Cubase (e.g., 128-256 samples) and avoid unnecessary virtual routing for the MIDI path.
• General VB-Cable Setup:
  • After install, you'll see "CABLE Input" (virtual mic/line-in) and "CABLE Output" (virtual speakers) in Windows Sound settings.
  • Don't set these as defaults. Instead:
    • In apps like Voicemeeter or browsers/games, set output to "CABLE Output."
    • In Cubase, set an input to "CABLE Input" to capture that audio.
  • For multi-channel needs (e.g., stereo guitar), use VB-Audio's Hi-Fi Cable or donate for more cables.
• Test: Speak into your mic or play guitar through i2M—route it to VB-Cable Output, then set Windows default recording to VB-Cable Input and record in Audacity. Audio should flow without touching defaults.

3. Integrate Voicemeeter for Flexible Routing
Voicemeeter (Banana is free and powerful) is like a virtual mixer. It sits between Windows defaults and your apps, letting you route multiple sources (e.g., system audio, i2M, mic) to outputs (PreSonus, virtual cables) without changing Windows settings.

• Install and Basic Config:
  • Run Voicemeeter. It creates virtual devices: "Voicemeeter Input" (for apps to output to) and "Voicemeeter Output" (system playback).
  • In Voicemeeter's menu bar: Set A1 output to your PreSonus (hardware out). Set B1/B2 for virtual sends if needed.
  • Inputs (Hardware/Strip Sections):
    • Strip 1: Sonuus i2M (select it as input device).
    • Strip 2: System mic or another input.
    • Strip 3+: VB-Cable inputs for app audio.
  • Routing: Send i2M to a bus → Virtual Output (e.g., VB-Cable) → Cubase for VSTi triggering.
• Tie to Windows Defaults:
  • Keep PreSonus as Windows default playback.
  • Set Windows default recording to Voicemeeter Input if you want system-wide capture.
  • In Cubase: ASIO driver = PreSonus. Inputs = Voicemeeter Aux or VB-Cable channels. Outputs = PreSonus channels (e.g., 1-2 for main mix).
• Example for Your Workflow:
  • Guitar → Sonuus i2M → Voicemeeter Input 1 → Route to VB-Cable Output → Cubase MIDI track (for VSTi) + Audio track (for monitoring raw signal).
  • This keeps everything zero-latency on the i2M path while allowing polyphonic VSTi layering (despite i2M's mono limit—use Cubase's MIDI effects for harmony if needed).
• Test: Play guitar; you should hear VSTi response through PreSonus with no Windows default changes.

4. Cubase 10.5 and ASIO4All Specifics

• In Cubase: Studio Setup > Audio System > ASIO Driver = PreSonus Studio 22 VSL (not ASIO4All unless troubleshooting). Set sample rate/buffer to match Windows/PreSonus.
• For virtual routing in Cubase:
  • Inputs: Add VB-Cable or Voicemeeter as stereo/mono channels.
  • Outputs: PreSonus mains + any aux for monitoring.
  • MIDI: Set i2M as MIDI input device in Studio Setup > MIDI.
• ASIO4All: Use only if an app doesn't support ASIO (e.g., old games). In ASIO4All control panel, enable PreSonus and VB-Cables, but disable unused devices to avoid conflicts. It wraps your hardware/virtual devices into one ASIO stream.
• Latency Tip for i2M: Since it's "tight and right," ensure no extra buffering—monitor directly from PreSonus in Cubase (low buffer) and use freeze/flatten for complex projects.

5. Troubleshooting Common Issues

• No Sound/Dropouts: Check sample rates match everywhere (Windows, PreSonus, Cubase, Voicemeeter). Use ASIO4All temporarily to test if it's a driver issue.
• i2M Not Detected: Reinstall Sonuus drivers from their site. Ensure it's set as exclusive mode in Windows (Properties > Advanced > Allow apps exclusive control).
• Virtual Cable Conflicts: If VB-Cable doesn't show, restart or reinstall. For multi-cable setups, use Voicemeeter to chain them.
• Latency Spikes: Close background apps. In Task Manager, set Cubase/PreSonus to high priority. Avoid Wi-Fi during sessions.
• Cubase Crashes: Update to latest 10.5 patches. If using VSL, ensure it's routed correctly in Universal Control.
• Tools: Use LatencyMon (free) to check for DPC latency issues from drivers.

Final Thoughts
By locking Windows defaults to your PreSonus and building virtual routing around it (VB-Cable for simple bridges, Voicemeeter for complex mixing), you'll have a stable foundation. This setup lets you experiment with paths for Cubase VSTi triggering from the i2M without constant resets. If your goal is even more advanced routing (e.g., polyphonic MIDI expansion), consider Reaper as a lightweight DAW alternative or hardware like a Fishman TriplePlay for fuller guitar MIDI. If you share more details (e.g., exact error or what you're trying to achieve), I can refine this further—happy shredding!

 

Spoiler: Source: Grok KI

The issue of not getting 24-bit audio with a Realtek audio chip and ASIO4All typically stems from configuration limitations or incompatibilities rather than the hardware itself. Here’s a concise explanation and solution:

Why 24-bit isn’t available:

1. Realtek Hardware and Windows Settings:
   • Most Realtek chips (e.g., ALC887, ALC1220) support 24-bit audio, but the Windows audio driver often defaults to 16-bit (e.g., 44.1 kHz, CD quality) in the Sound settings.
   • ASIO4All is a wrapper that relies on the Windows driver’s settings. If Windows is set to 16-bit, ASIO4All won’t offer 24-bit.
2. ASIO4All Limitations:
   • ASIO4All is not a native ASIO driver but a universal wrapper. It only exposes bit depths supported by the underlying Windows configuration and Realtek driver.
   • Sample rate mismatches (e.g., 44.1 kHz vs. 48 kHz) or buffer settings can prevent 24-bit from appearing.
3. Driver or Software Issues:
   • Outdated Realtek drivers or generic Microsoft drivers may not expose 24-bit options.
   • Some older Realtek chips are hardware-limited to 16-bit, though this is rare in modern systems.

How to Enable 24-bit:

1. Update Realtek Driver:
   • Download the latest Realtek driver from your motherboard manufacturer’s website (e.g., ASUS, MSI) or realtek.com. Install and reboot.
2. Configure Windows Sound Settings:
   • Right-click the speaker icon in the taskbar > "Sound" > "Playback" tab > select your Realtek device > "Properties" > "Advanced".
   • Set the format to "24-bit, 48000 Hz (Studio Quality)" or higher. Disable "Allow applications to take exclusive control" if issues persist.
   • Repeat for the "Recording" tab (e.g., for microphones).
3. Tweak ASIO4All:
   • Download the latest ASIO4All version (v2.15 or higher) from asio4all.org.
   • Open the ASIO4All control panel (via your DAW or standalone).
   • Ensure the Realtek device is selected and set the sample rate to match Windows (e.g., 48 kHz).
   • Adjust buffer size to avoid crackling (e.g., 256–512 samples). Enable "Always Resample" if needed.
4. Test in Your Software:
   • In your DAW (e.g., Ableton, Reaper), select ASIO4All as the audio driver and check for 24-bit in the audio settings.
   • Use a tool like Audacity to verify bit depth.

Additional Notes:

• If 24-bit still isn’t available:
  • Confirm your Realtek chip supports 24-bit (check motherboard specs or use HWInfo).
  • Reinstall ASIO4All or try the official Realtek ASIO driver (if available, rare).
  • Consider a dedicated audio interface (e.g., Focusrite) for reliable 24-bit ASIO performance, as Realtek + ASIO4All is a budget workaround with limitations.
• Why 24-bit matters: It offers better dynamic range (144 dB vs. 96 dB for 16-bit), crucial for recording/mixing, though less critical for playback.

If you provide details like your motherboard model, Windows version, or DAW, I can refine the advice further!

 

you should look into Windows sound settings and disable all enhancements and NOT enable exclusive mode (else apps lock out audio ins outs devices)