Midi+Audio mixdown & pan/vol in Qtractor: a hack & a half

[bluebell]

@rncbc, anything wrong with this approach? If not, could you perhaps enable/allow direct creation of "aux send" in the "out" section of busses?

nothing is really wrong if it works right for you

welcome to qtractor's power-user guild
cheers

Respect, @yellius!
I am still abusing insert sends.

But @rncbc, is there a technical reason why it's not possible to create an aux send in an output bus?

[rncbc]

is there a technical reason why it's not possible to create an aux send in an output bus?

reason explained above: only would work only if the target bus is listed after the source one;
to avoid the pitfall the insert option is permanently disabled.

[bluebell]

is there a technical reason why it's not possible to create an aux send in an output bus?

reason explained above: only would work only if the target bus is listed after the source one;
to avoid the pitfall the insert option is permanently disabled.

OK, so I'll stay with insert sends. This works with targets after and before the source. The price to be payed is one jack buffer of latency, easily audible with jack buffer sizes of 1024 and more.

See my sample session

Bus_to_Bus-Test.qtz.zip

(12.2 KiB) Downloaded 37 times

Bus Latency should be correctable by using an additional bus between source bus and master bus. And it is:

Bus_to_Bus-Test_2.qtz.zip

(12.23 KiB) Downloaded 34 times

Important: A bus' output (not insert send) to another bus works only if the receiving bus is left (in mixer) from or above (in View->Buses) the outputting bus.

[rncbc]

as said,

the permanent disablement of having an Aux-Send in an output bus chain is at the UI level, only!

nothing will stop you from running an old session that was saved before that UI restriction took place...

you may even hack the xml file for that, but please, a lot of caveat emptor, yada yada will apply... it's just you ought to know what you're doing
like house cats do know dang well, if it fits, it sits
cheers

ps. if it's there enough demand the restriction might go away. sure, your call (PR first:))

UPDATE: qtractor >= 0.9.35.10git.af34cb might have nailed it! enjoy

[bluebell]

as said,

the permanent disablement of having an Aux-Send in an output bus chain is at the UI level, only!

nothing will stop you from running an old session that was saved before that UI restriction took place...

you may even hack the xml file for that, but please, a lot of caveat emptor, yada yada will apply... it's just you ought to know what you're doing
like house cats do know dang well, if it fits, it sits
cheers

ps. if it's there enough demand the restriction might go away. sure, your call (PR first:))

UPDATE: qtractor >= 0.9.35.10git.af34cb might have nailed it! enjoy

That's great. Now Qtractor offers 2 options for Audio from bus to bus:

• AUX send to output or duplex destination bus "right" to the sending bus, no additional latency
• INSERT send to any duplex destination bus, adds one jackd bufsize of latency