Add new comment

Hi Rui:
I know we are on a holiday. So it is not necessary to read this now.
Whether it should be solved or not is up to you.

When developing this flow I think I have stumbled upon a bug. Maybe not.
To avoid the reflow loop we have to perform midi filtering.
If I do it with an external application, there are no problems, everything works correctly. For that I have used Qmidiroute.

However, if it is done with internal filters it does not work.

I have confirmed that the error is not in the filtering plugins (I attach and develop the tests later).
I think the error is in the inserts and auxiliary sends.
--- Update ---
The error may not be in the MIDI insert/auxend.
I can't diagnose the problem and I don't want to confuse either.
--- End Update ---
They do not only send the filtered information, but also the original.

This is the test that shows the bug:

A midi channel has been created as a CC signal transmitter.
It has been filtered in the following way:

Plugin 1: Ensures that all channels are now channel 16, the one chosen for CC transmission. As long as no tracks are used with channel 16, there is no risk of backflow.

Plugin 2 and 3: Convert the original CC signals from Gain7/Pan10 into the desired ones.

Through an insert, the signal is sent to the input of the Master midi bus. Just before the insert, I place a midi monitor to view the send. It is checked that the pre-send filtering is correct.

I place another midi monitor at the input of the Master midi bus.
It is checked that in addition to the filtered midi signal, the original is received. Hence the errors and blind shots that are being suffered.

If this is solved, I think that the How to could be created, because it would be a relatively simple workflow to carry out (somewhat complicated to understand, but in general the whole subject of connections is always complicated, whether in audio or midi), and it would really allow for much more powerful automation than the current one.
For example, it allows nesting automations, creating automation groups, staggering, inverting, limiting automations through plugins, etc.

Related topics:
I've noticed that the increase in plugin shortcuts is only in odd numbers. It would be nice if you could set any value from there, not just odd numbers. This would allow you to target channels, specific CC messages etc without having to go into the plugin properties.

I also stand by my previous comment.
MIDI track faders should not receive CC or have a CC assigned by default, unless it is expressly applied to them (as is the case with the rest of the MIDI tracks and buses).

Happy New Year :)

P.S.
Discard Unmached Events

Without this option, the evil loop also occurs with QMidiRoute.