One idea would be to amend the norns systemd service norns-jackd which is defined in file /etc/systemd/system/norns-jack.service, and change it's -d hw:0 to -d hw:1for alsa.
A variation of the above idea would be to have a different, separate service which connects to -d hw:1 (or by name) to replaces the norns-jack service, perhaps called something like norns-jack-opz.service, and alternate between these two. systemctl --quiet is-enabled norns-jack etc. can be used to programmatically check if a service is currently running.
This would spare running separate processes which eat a lot of CPU. At the same time, this would disable the norns input and output.
It would (partially) make sense to do this at system level rather than a norns program. This would be done by adding udev rule in /etc/udev/rules.d plus writing a program which starts alsa_in and alsa_out when the OP-Z is plugged in and adds the jack routes, and tears this setup down when the OP-Z is disconnected from USB.
One idea would be to amend the norns systemd service norns-jackd which is defined in file
/etc/systemd/system/norns-jack.service, and change it's-d hw:0to-d hw:1for alsa.A variation of the above idea would be to have a different, separate service which connects to
-d hw:1(or by name) to replaces the norns-jack service, perhaps called something likenorns-jack-opz.service, and alternate between these two.systemctl --quiet is-enabled norns-jacketc. can be used to programmatically check if a service is currently running.This would spare running separate processes which eat a lot of CPU. At the same time, this would disable the norns input and output.
It would (partially) make sense to do this at system level rather than a norns program. This would be done by adding udev rule in
/etc/udev/rules.dplus writing a program which startsalsa_inandalsa_outwhen the OP-Z is plugged in and adds the jack routes, and tears this setup down when the OP-Z is disconnected from USB.