From everything I've read (which isn't all because the topic is old and branched across several platforms) and thought, there are ultimately two approaches:
1) Touch the audio flow
2) Allow interface customization (assignable faders, equivalent to the current assignable automation). Which, if I understand correctly, is what @bluebell proposes.
The first approach always stumbles upon the complexity of finding equivalences between the audio workflow and MIDI + audio.
I came up with the one at the beginning of the post, in case focusing only on audio Auxiliary Sends could simplify things a bit...
However, in the end, I think @bluebell came up with the real solution a while ago.
Assignable faders allow everything without having to modify any of the engineering or internal logic, because it's a GUI-level feature only.
It really solves the problem and greatly expands the potential (especially now that we have Controllers).
It's a little less user-friendly than the default Fader in the plugin rack (Adour style), but only a little.
When we were talking about it a while ago, I wasn't convinced because each plugin has its own scales, but if the fader numeric boxes adapt to the units of dB, %, or fractions offered by the plugin, there's no big confusion either.
Ultimately, this is the solution so that Qtractor remains Qtractor and doesn't modify its internal logic, simply expanding its functionality.
Related:
I finally found a fader compatible with Qtractor's gain scale, to use as a fader pre AuxSends.
From everything I've read (which isn't all because the topic is old and branched across several platforms) and thought, there are ultimately two approaches:
1) Touch the audio flow
2) Allow interface customization (assignable faders, equivalent to the current assignable automation). Which, if I understand correctly, is what @bluebell proposes.
The first approach always stumbles upon the complexity of finding equivalences between the audio workflow and MIDI + audio.
I came up with the one at the beginning of the post, in case focusing only on audio Auxiliary Sends could simplify things a bit...
However, in the end, I think @bluebell came up with the real solution a while ago.
Assignable faders allow everything without having to modify any of the engineering or internal logic, because it's a GUI-level feature only.
It really solves the problem and greatly expands the potential (especially now that we have Controllers).
It's a little less user-friendly than the default Fader in the plugin rack (Adour style), but only a little.
When we were talking about it a while ago, I wasn't convinced because each plugin has its own scales, but if the fader numeric boxes adapt to the units of dB, %, or fractions offered by the plugin, there's no big confusion either.
Ultimately, this is the solution so that Qtractor remains Qtractor and doesn't modify its internal logic, simply expanding its functionality.
Related:
I finally found a fader compatible with Qtractor's gain scale, to use as a fader pre AuxSends.
It doesn't have exactly the same scale, but if you customize it in the bolliefader.ttl, it does the job well.
https://github.com/MrBollie/bolliefader.lv2