Add new comment

THE WORST:
It really is a nodal workflow.
All node workflows share a pro and a con:
* Pro: Powerful and flexible
* Con: Difficult to understand and visualize from the outside.

It doesn't matter the context, image, video, 3d, audio...

In this case it is even more difficult:
1 MIDI flows tend to propagate in parallel configurations, filtering becomes unintuitive, which causes flows that are difficult to detect (hence ShowMidi).

2 There are 2 nodal systems coexisting and interacting Carla, and Qtractor connections, which in turn are divided into inserts, buses and sendAux that can vary in behavior to the same MIDI events, and to top it off Control CC messages, which propagate throughout qtractor because they do so at the interface control level.

3 The MIDI filters that are available lack a GUI and the concepts they handle are very abstract.

So while these flows I propose are functional and allow to expand the possibilities of Qtractor, it is true that they are not intuitive.
Hence the need to document and give custom names to each element. (Plugin Aliases are very useful here).
That is why I need a plugin that allows to include text (comments) at any point in the chain.
I am going to take a look at the LV2 plugin examples, to see if I can build myself a "Notebook".

However, I do not think that these nodal flows can help to improve and expand the automation tools of Qtractor at the level of functionality and GUI. Because the moment the flows are defined at the programming and GUI level, they will stop being nodal.

That said, it can be useful to improve the GUI and functionalities of Qtractor when implementing nodal flows.

---

THE BEST:
If we limit ourselves to using midi tracks as an internal Automatable Midi Controller capable of sending "learn midi" to control things through Qtractor's CC Control, everything is greatly simplified. We create a duplex Midi Bus and call it CCA (Automatable CC Midi Controller). Done. All the tracks dedicated to sending CCA are assigned to this bus.

The filtering work is done from Carla.
You can create presets for tracks with everything already preconfigured according to the flow you want to achieve.

The user does not have to understand how the track works if he does not want to. He will only have to read the "note" to know what values ​​are available to assign to the CC receiving faders.

But of course, for that you need a notepad plugin.