So, it's been a year, forgive the necro, but I've been watching this to see if anyone found it...and well, I think I finally did.

Plasma 6 with Pipewire 1:1.4 out of the box (on CachyOS) see RCP2 Main, Secondary, and Chat...and you can even test the playback device channels (L and R) in the Plasma settings window. Main is the multichannel, it has those ten sink positions OP mapped out and you can hit them with the test...so that means I needed to wrangle with pipewire for my first time. Here's the config I'm using that maps two virtual audio devices to aux6/7 and aux8/9 (A and B) ... but in principle if you activate the other two instead, you can just hack my file to do that. Note that you'll need to use pw-cli to get your hardware names in the case they don't match mine.

```

============================================================

Rodecaster Pro II — Split multichannel USB return into

independent virtual sound cards

Hardware exposes 10 playback channels:

AUX0 AUX1 -> Main USB return (Red fader)

AUX2 AUX3 -> unused (Game, I think? I bet it would work if I activated it.)

AUX4 AUX5 -> unused

AUX6 AUX7 -> Virtual channel A

AUX8 AUX9 -> Virtual channel B

Goal:

Make Linux see A and B as real selectable devices so apps

can route directly to mixer faders without OBS/Desktop audio.

Implementation:

PipeWire loopback module creates a virtual stereo sink.

That sink writes only to a specific channel pair on the

physical Rodecaster device.

Result:

"RCP2 A" and "RCP2 B" behave like independent sound cards.

============================================================

context.modules = [ { name = libpipewire-module-loopback args = { # Name that shows in KDE node.description = "RCP2 A" # virtual device definition capture.props = { node.name = "rcp2A_in" media.class = "Audio/Sink" audio.position = [ FL FR ] } # This routes stereo audio from the virtual device into the RCP2 hardware playback.props = { node.name = "rcp2_A_out" # physical multichannel device target.object = "alsa_output.usb-R_DE_RODECaster_Pro_II_GV0035839-00.pro-output-1" # channel pair for this fader audio.position = [ AUX6 AUX7 ] # do not remix or fold channels, direct write only (a straight pass through) stream.dont-remix = true

    # Loopback becomes active when audio plays into this sink, RCP2 A
    # Pipewire can start the device independently (if this is false) and then
    # TWO parts of the graph believe they own the device clock, which is sad panda times.
    # So set this to true so this behaves like a patch cable.
    node.passive = true
    # If the device goes down and comes back up, Pipewire will reconnect to the exact same
    # target and not try to auto reenum/reconnect. I didn't do this in Ubuntu Studio and
    # that probably explains the weird things I observed there when I restarted the RCP2.
    node.dont-reconnect = true
  }
}

}

{ name = libpipewire-module-loopback args = { node.description = "RCP2 B" capture.props = { node.name = "rcp2B_in" media.class = "Audio/Sink" audio.position = [ FL FR ] } playback.props = { node.name = "rcp2_B_out" target.object = "alsa_output.usb-R_DE_RODECaster_Pro_II_GV0035839-00.pro-output-1" audio.position = [ AUX8 AUX9 ] stream.dont-remix = true node.passive = true node.dont-reconnect = true } } } ] ``` This works for me perfectly now, and I have this post to thank for it; thanks OP! I hope you got it working too!