This sounds like it may be a job for zita-resampler but I don’t know if it works with PipeWire’s JACK implementation. Unfortunately I can’t speak to the 2 devices question but in the past I had a USB Bluetooth interface that worked with JACK and only supported the BT standard 48000 and all my Ardour sessions were 44100 so in order to use the BT device on the fly and hear Ardour through my BT speakers I had to use zita-resampler, hopefully bigger brains show up to assist and say whether this is an option at all…
If you skip all the Audio backends there may be some way to tie the devices together at the ALSA level but I think the different sample rates are going to throw a wrench in the works.
Lastly the obvious point… A USB Audio device locked at 44100 seems kind of unimaginable in this day and age, is a hardware upgrade, or rental, or borrowing from that good buddy who has all the gear but doesn’t know how to use it not an option?
If you don’t need audio from that interface, then use it for midi only and don’t connect to the audio graph.
If you didn’t need to route audio between applications, then use the alsa backend. If you do need to route audio and that is why you want to use pipewire, then use the audio configuration application to configure pipewire to ignore the 44.1-only interface.
Thanks for the quick answers. Switching to ALSA as the backend does the trick for this type of projects. MIDI works and I connected the audio outputs from sc44100 with the inputs from sc48000 to be able to record audio.
A quick test with Tracktion showed that my Pipewire setup works with both sound cards so I hope my configuration is not the culprit. I can not find an option to turn off the audio part from an interface. Is this an Pipewire or Wireplumber feature?
There are, for example, synthesizers, which can also act as an USB audio interface (with inputs and outputs), that only support a 44100 Hz sampling rate.
I have such a synthesizer, the Yamaha MODX, which provides a 44100 Hz, 10 ch input, 4 ch output interface. Using this audio interface, in addition to my main interface, is very handy to record the MODX digitally, without any unnecessary DA->AD conversion and without taking up inputs on my main interface. I have been using zita-a2j/-j2a to integrate the MODX interface into my JACK2 setup. And in spite of the strong recommendations against this, e.g. in the FAQ article by Paul, this has been working very well for me. I can add the interface to my running JACK graph on-the-fly as needed.
Unfortunately, still the case and, particularly with Linux where a lot of older hardware is still supported, functional and, in many ways, better than currently available gear, very common.
I reckon around 50% of the kit I regularly use is still locked to 44.1kHz. And I, personally, wish to see 44.1kHz die a fiery death as there is, increasingly, no longer a reason for it to exist (although the nostalgia-for-obsolete-technology trend is, apparently, now on the CD bandwagon - at least there’s more logic to it than compact cassettes).
Haha, on that note I fished out my Tascam US-122 from behind the door it had been holding open since 2013 or so… It’s officially dead even on Linux, I summoned all the udev hackery, alsa-firmware, lsusb mojo I had and I did get the little green light to go on and the capture ports to show up but no output ports (several Reddit threads confirmed this is the current best-case state of affairs). Linux don’t let 'em die very easily but this one’s time has come…
