Main menu
You are here
Bus automation using track automation
Is it possible to automate buses with the Qtractor automation tool?
Of course, Qtractor offers you enough modules so that you can do almost anything possible.
You just have to create the way (the workflow) to achieve it.
You just have to combine the automation tool with the CC control tool.
(As a transmitter event we have the 7 volume and the 10 panning. I will continue investigating how to use more. On the other hand, the receiver can be any element on the bus)
*See P.S. 2
The only problem is the data backflow. But it is solved by a midi filter plugin. With this filter at the beginning of the plugin box we get that automation track to receive CC on channel 15, and emit on 16. There is no conflicting loop anymore.
Another added advantage is that we can now have an exclusive layer for each automation.
Attached files.
P.S.
If you need more controllers you can add a midi clip and send the CC events from there, it is not as comfortable as the automation tool, but it expands the possibilities.
Another option is to use more midi channels, but of course we are very limited with only 16.
P.S. 2
We can use the fader (CC7) and turn it into any CC message with the "MIDI CC map" plugin.
This means:
We only use midi channels 15 (input) and 16 (output). We have 127 CC messages to automate 127 track and bus elements from each main fader of each midi automation track. If we fall short (I don't think I will) we can always have 127 extra controllable elements using 2 more midi channels (13, 14 for example).
This means being able to create automation layers, and have them all visible at the same time.
Now, it can no longer be said that Qtractor has any limitations when it comes to automation.
| Attachment | Size |
|---|---|
 BusAutomati.1.qtz | 2.41 KB |
 BusAutomati.gif | 228.12 KB |
re. Bus automation using track automation...
Can I hear a new How To coming in?
cheers && happy NYE
In NYE
It seems like a powerful and affordable workflow. So yes, my intention is to do a how-to at the beginning of this New Year that we hope will be prosperous for everyone.
Improved flow
I don't know why, but with the "Midi CC Map" plugin the backflow doesn't occur. So one midi channel is enough.
The key is to always transform the CC7 message type into another one using the "Midi CC Map" plugin.
Important: Generic CC messages must be used to avoid conflicts (for example from 20 to 31, from 46 to 63, etc.).
The image shows how we can also automate plugins.
I have now used a midi bus for the sends, which simplifies the connections.
I also attached the .qtz for those curious.
Harmful backflow continues to occur
If new filters are added, the harmful backflow reappears.
On the other hand, I have the feeling that the midi signal does not work in series like the audio signal, but in parallel. If so, it is impossible to cut the backflow.
I will continue investigating, but it seems that this is not a recommended working method.
I think I've found the problem
Midi faders (Volume/Pan) always receive CC 7/10 of their channel, even if they have another CC assigned, or none at all.
I ask, is that a desirable behavior? I guess it was a feature at the beginning of Qtractor to make it easier to control mixers with external devices.
Considering that we can have several midi tracks with the same channel and different plugin synths, it's confusing and counterproductive.
When you assign a CC to a fader, Qtractor takes the precaution that it is not a previously used CC message. However, it allows all midi tracks with the same channel to share the same CC and channel.
If an element does not have a CC controller assigned, it should not receive a CC message. I think that would be the desired behavior always.
The problem was auto-monitoring
It seems that disabling it eliminates the reflux.
The default CCs of midis tracks are also reset if that same CC is assigned to any other element.
Everything worked fine, it seems that it was just auto-monitoring.
I'm still curious.
I'm sorry to be going around in the dark
I think I've finally found the problem.
It's the auto-assignment of CC controls on faders 7/10 of midi tracks.
For example:
I want to control the Fader and Pan of an audio bus.
I configure it to receive from channel 16 CC 7/10 respectively.
Everything works fine, because when I assign it in the Audio Bus, the midi tracks stop receiving that CC control by default. They lose the default CC reception.
Now, if I remove or change the CC reception on the audio bus, the midi tracks recover it, and the loop arises again.
Conclusion:
The midi track faders should work like any other fader element in Qtractor. They should not receive CC controls if they are not expressly assigned to them.
Add new comment