06-25-2020, 09:42 PM
(This post was last modified: 06-25-2020, 09:44 PM by madmaxmiller.)
(06-25-2020, 02:08 PM)zimbodel Wrote: The problem can be solved by:
1) a2j developers assing a devce ignore config file so that it not just grabs everything exclusively when it starts. I contacted them.
2) Mixbus needs explicit jack routable midi ports for interface control to circumvent the use of a2j.
3) Bitwig give up their proprietary behaviour and accept devices from providers like a2jmidid
Bitwig even "sees" the devices when a2jmidid is on, it just choses to not access them.
MMM
Linux throughout!
Main PC: XEON, 64GB DDR4, 1x SATA SSD, 1x NVME, MOTU UltraLite AVB
OS: Debian11 with KX atm
Mixbus 32C, Hydrogen, Jack... and Behringer synths
Main PC: XEON, 64GB DDR4, 1x SATA SSD, 1x NVME, MOTU UltraLite AVB
OS: Debian11 with KX atm
Mixbus 32C, Hydrogen, Jack... and Behringer synths