Zero Copy

man, how many times do I have to say it again?

it stands the (dang old) advice for not connecting directly any own outputs (output buses and insert sends) to own inputs (input buses and insert returns).

what you may be experiencing here is the so called "new AuxSend development" will reorder the internal route processing of the output buses, entirely independent of their visual listing order, remember?

so, bear with me, while some direct loop insert sends/returns might have once worked before, on some tracks and/or buses, they also might stop or even start working again, once you mess with that said internal processing order ad-hoc.

so please, again, don't overlook the advice :)

Mostly, this is a communications problem. Remember, we're dealing with somewhat abstract concepts which are made harder to understand as folks use different words and terms to convey ideas and related components. It's a shortcoming of the communication method (forum) mostly; someone writes something that is true but a few months later it just ends up fading into the abyss....

Seems like a single source of truth would be a better way to document and showcase these ideas. It can't be that wiki thing...... it's too hard to interact with and is just too "read-only". It should be a git repo that showcases known-working setups which produce repeatable outcomes. That approach would make a ton of sense since all the "guts" of Qtractor's data are non-binary (.qtr and .mid files). A hosted git repo (a.k.a. github) has all the collaborative tools baked in already so people could easily do all the things (issues, PRs, etc).

The only thing I see that might block that vision is the "absolute path" behavior of the <directory> element in the .qtr spec. If that would be changed to be relative, I could see people being able to profit like so...

git clone https://github..com/whatever/qtractor-workflows.git
cd qtractor-workflows
qtractor zero-copy/project.qtr

You get the idea. Maybe I'll throw together an example repo showing how I handle signal routing of a multi-output drum plugin (using AVL drumkits)