Add new comment

Assignable Audio ins and outs per track
I'm slightly afraid, again ;) I'm not following you on this one. Audio I/O in Qtractor just don't mess with your synths and samplers which are driven by MIDI and can be fed by Qtractor MIDI tracks. However, synths and samplers are stand-alone in this sense as having their own audio outs. These audio outputs can be bounced to Qtractor audio tracks or/and connected outbound for proper processing or listening. Having the LinuxSampler example, you connect Qtractor MIDI track/channels as output MIDI buses to LinuxSampler MIDI input(s). LinuxSampler audio device outputs are exposed on their own JACK ports, for instance, and thus are subjects for connection to whatever you wish, but the main issue is that those are not managed in Qtractor.

Multiple midi channels per track (revisited)
Perhaps, what you need is about having more MIDI buses (aka ALSA sequencer ports) then the single Master default one. Is it? I've failed to point you precise directions in my previous reply, so here it goes: audio and MIDI buses are mangaed under the View/Buses... dialog. There you can create as many MIDI buses as you need. Again, what you'll actually creating are ALSA seq ports, each one with 16 addressable MIDI channels. So let's say you have 32 instruments loaded in LinuxSampler and want to drive each one by one Qtractor MIDI track. There, you'll need 32 MIDI tracks and 2 MIDI buses. Each track must be assigned to it's own MIDI channel and MIDI bus. For example, the first 16 tracks (tracks 1-16, channels 1-16) should go to MIDI bus #1. The other 16 tracks (tracks 17-32, channels 1-16) should assign to MIDI bus #2. Now it should be clearer which Qtractor MIDI buses you want to connect to which LinuxSampler MIDI input device ports, most certainly you'll have 2 ports with a corresponding mapping to each sampler/MIDI channel. Got it?

Hope you get the mess :)
--
rncbc aka Rui Nuno Capela