CC from one track to another

[Largos]

In this topic I tried to send CC from one track to another. Just setting the MIDI output to another track’s MIDI input doesn’t work*. I tried to connect a track’s output to the MIDI control in channel via the midi connections manager but this doesn’t work with MIDI Learn* and it pops up the No Align light. I don’t know whether that is supposed to work or maybe the ability to make that selection shouldn’t be there?

*Edit: I should clarify that this is for Ardour’s controls and for the purposes of recording automation. Plugins with their own midi learn can receive the CC

[befloibent (Manuel)]

See if this helps

[SOLVED (sort of)]Hardware/MIDI Through no longer visible in MIDI Connection Manager

Thanks for checking. That did help. Using Pipewire/JACK, despite the MIDI Through not being visible in the MIDI Connection Manager, it IS visible in the Control Surface->Protocol Settings. This is not so when using ALSA. So I think I figured this thing out. First a big screenshot of what all is going on, later the wiring, and finally some caveats/question marks. [CCAutomationFromAnotherTrack] In this picture, Track 1 has Cardinal (upper right) with 1- and 2-D Random Walk Modules attached t…

Does not work with ALSA, only Pipewire/JACK.

[Largos]

Thanks for the reply. I couldn’t get it to work with midi learn with this method though.

[befloibent (Manuel)]

Sorry for the delay. I’ve put together an Ardour template called CCAutomation. Try unpacking the gzip in your local templates folder. It will hopefully set up all the routing, otherwise they are shown in the screenshot below. Pre-requisites are Cardinal Synth and ACE Reverb, but if you can get it to work, you can use whatever you want.

Right now, it is set up to use the 2D Walk module in Cardinal. One variable is mapped to CC 1 which controls the track fader, the other is mapped to CC 11 and controls the Reverb Blend parameter.

The variables in Cardinal are muted. Engage MIDI Learn on one automation parameter and un-mute the associated CC.

If you still can’t get it to work, I’ll try putting a demo on YT or something.

Good luck

[x42 (Robin Gareus)]

@Largos

I tried to send CC from one track to another.

That should work just fine.

@Largos

I tried to connect a track’s output to the MIDI control in

That is unlikely to work correctly, and as you mentioned “the ability to make that selection shouldn’t be there”.

Control surface data is processed at the start of each process cycle, and may perform operations on tracks or plugins. This happens before the MIDI track runs and produces output.

Besides, In theory you could MIDI learn a Fader to itself, which produces a feedback loop, and an ambiguity regarding port latencies (1 cycle offset).

In any case, we cannot prevent JACK users who use a 3rd party patchbay application from making nonsensical connections, and hence Ardour also needs to show them in the connection matrix.

[Largos]

Thank you, it seems the problem for me was the plugins I was using to generate the CC as well.

[Largos]

@x42

That should work just fine.

Yes, I’d like to say I didn’t open the wrong CC lane instead of pressing show existing automation but I can’t

@x42

That is unlikely to work correctly, and as you mentioned “the ability to make that selection shouldn’t be there”.

Control surface data is processed at the start of each process cycle, and may perform operations on tracks or plugins. This happens before the MIDI track runs and produces output.

Besides, In theory you could MIDI learn a Fader to itself, which produces a feedback loop, and an ambiguity regarding port latencies (1 cycle offset).

In any case, we cannot prevent JACK users who use a 3rd party patchbay application from making nonsensical connections, and hence Ardour also needs to show them in the connection matrix.

It would be nice to be able to automate parameters with plugins and not have to resort to nonsensical connections though. Also, if you have a midi file with CC in and want to link it to a plugin parameter via Ardour, this seems to be the way to do it as well. Unless I am missing something (likely).

[befloibent (Manuel)]

@Largos

Unless I am missing something (likely).

I generally don’t know what the hell I’m doing. I tend to just make things up as I go along. Sometimes it even works, and occasionally it’s repeatable.

[Largos]

Not a way to link but there is a lua script called Midi CC to plugin automation which converts the CC of a midi file to processor automation. However if the plugin has plugin automation parameters in sub menus then they don’t appear as a choice in the script. This is an issue in another script (add LFO to plugin parameter) so it might be a bug.