How to Assign Separate ASIO Output Pairs to HW1 and HW2?

Replies

• PatchdNov 8, 2026#2

  Not today. In Patchd 1.0.0 you can't pick an ASIO output pair for a hardware output, so on the UR24C you can't reach Out 3+4.

  Here's why. A hardware output in Patchd picks a Windows playback device, and Patchd then uses the ASIO output pair whose channel names match that device's name. The Steinberg driver's playback devices are called Voice, DAW and Music, which match none of the channel names, so every hardware output lands on Out 1+2.

  Choosing the output pair on each hardware output, the way you can already pick Input 1 and Input 2 separately, is the fix. It's noted as a request.

  👍1👎0

  • COKAAuthorNov 9, 2026#3

    Thanks for the detailed explanation! This confirms exactly what I was experiencing with my Steinberg UR24C.

    I believe there are three features that would make Patchd significantly more powerful and flexible, especially for users working with professional audio interfaces and external controllers:

    1. Direct ASIO Output Pair Selection The ability to manually select a specific ASIO output channel pair for each Hardware Output. For example: - HW1 → ASIO Out 1+2 → Studio Monitor Speakers - HW2 → ASIO Out 3+4 → Headphones This would provide the independent hardware routing that many users need when working with multichannel audio interfaces.

    2. Manual ASIO Driver Selection The ability to manually select which ASIO driver Patchd should use, rather than relying exclusively on automatic detection. Some users have multiple audio interfaces or several ASIO drivers installed on their systems. Being able to choose the preferred driver manually would provide much greater flexibility and prevent potential conflicts or unwanted automatic selections.

    3. MIDI Controller Mapping Support for MIDI mapping, allowing users to assign physical controls from external MIDI controllers to Patchd functions. For example, mapping physical faders, knobs and buttons to individual input levels, hardware output levels, mute controls and other available functions. This would make Patchd much more practical for hands-on audio routing and studio workflows, especially for users who already own MIDI control surfaces such as the Korg nanoKONTROL2.

    I believe these three additions would greatly expand Patchd's capabilities and make it an even more attractive solution for advanced audio routing and studio setups. I really hope these features can be considered for future releases.

    Thanks again for listening to user feedback and for being so responsive. Keep up the great work!

    👍0👎0
  • PatchdNov 9, 2026#4

    Here's where each one stands.

    Choosing the output pair on each hardware output is now on our plan, so HW1 could use Out 1+2 and HW2 Out 3+4. We can't say yet when it will be built.

    Choosing the ASIO driver yourself comes in the next update. Click MASTER CLOCK at the top of the window and pick Automatic, any ASIO driver you have installed, or your computer's timer. There's also a button that opens the driver's own settings.

    MIDI controller mapping is noted as a request.

    👍1👎0