Topic: Linux custom suitcase controller - alsa subdevices ignored
First, let me thank the Pianoteq team for building such and amazing piece of rock solid audio software. I've been running Pianoteq on linux x86_64 for a few months now and it has been rock solid! I've even left the same instance running for over 2 weeks with no performance problems, memory leaks etc. Absolutely awesome. Thank you.
I'm building a suitcase controller / live rig using an Atom 550, Ubuntu 10.10 x86_64, Native Instruments Audio2DJ, Fatar TP80 waterfall keyboard. The rig is designed to be used headless (no monitor) and will use midi automation to control Pianoteq. With this setup I'm getting a performance index of 13-14.
The only issue I've run into is in utilizing all 4 channels of the Audio2Dj, a 2 subdevice, low latency usb audio interface. Pianoteq will only list the first available subdevice in the Alsa config, whereas on my MacBook, Pianoteq lists all 4 channels for the Audio2Dj (not a fair audio subsystem comparison, I know).
Here is what 'aplay -l' tells me
card 2: Audio2DJ [Audio 2 DJ], device 0: Audio 2 DJ [Audio 2 DJ]
Subdevices: 2/2
Subdevice #0: subdevice #0
Subdevice #1: subdevice #1
I've tried creating virtual alsa devices that included all 4 channels, but Pianoteq will still only list the first available subdevice.
I have been able to route to all 4 channels using Jack, but Jack can be unstable and my attempts at automating channel routing post launch of Pianoteq were not rock solid - there are too many things that can go wrong in a headless environment. I've also had Jack crash on me many a time - it is not as stable as Pianoteq IMHO.
Does anyone know of any tricks to get Pianoteq to list all Alsa subdevices? That way I could select all 4 channels, save my configuration and leave it.
Thanks,
Patrick