Reviewing @rounakagag's excellent help videos, I realized once again how unintuitive it is not to be able to manage the signal from bus faders.
I've thought of a new approach... This isn't a feature request.
In short, once again, I couldn't help but think of a possible solution, and once I've thought of it, why not share it?
As always, I don't know if it's viable or completely absurd from an engineering and usability perspective...
1_
Add a new access point to the current "triangle" of plugins + faders, just after the faders and before the output.
This would be for audio tracks and buses.
2_
This access point would be exclusively for AuxSends audio. It would be available in the pseudo-plugin's properties.
3_
If the box is checked, the pseudo-plugin automatically moves to the last position in the rack. It also adds a small 2px top margin compared to the previous plugin, and its top border is dotted with the color assigned to the audio in the options.
There can be multiple aux sends downstream to multiple buses. The behavior remains the same.
All of this symbolizes that it is separate from the current rack's audio chain.
4_ For ease of understanding, the bottom border of the track will also appear dotted.
re. Post Fader pre Out...
yes, you're almost right (hundreds of times at least and prolly one+ decade old... ain't that right @bluebell ? ;))
sorry to tell, it's been uber-procrastinated to v2.0 or later, dang!
cheers
Me? Never heard of :D
That would be a cool idea.
Seriously, there are many ways to implement it and I think it should be considered well, especially because there are not only audio tracks but MIDI tracks, and having CCs on fader and pan is a basic concept of Qtractor.
My dream is a switch for fader and pan, both in audio and in MIDI tracks, to switch between
1.) old way (default when creating a track)
2.) freeing them from their old function but making them a source that can be bound to plugin parameters (like automation).
I would configure the fader to the volume of a simple amp plugin. By placing other plugins or AUX sends before or after the amp plugin I can make them pre- or post fader.
re. Never heard of...
maybe it was way back before, but this one was what's about:
https://sourceforge.net/p/qtractor/tickets/105/
or am I dreaming and loosing my mind to ageing? :)
't was just a joke
Of course I tried multiple times :)
Assignable Faders
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
fader scaling
Since the fader cannot know how the plugin's parm scales I think a first try would be a range from 0 to 1 and an option to switch between linear and logarithmic.
True
I don't know why, I thought the measurement data (dB, %, etc.) was searchable, but no... it doesn't appear anywhere.
So the behavior should be identical to the current shortcut. The advantage here is that we can read the value directly in the box without having to hover over it (tooltip).
Add new comment