I’m using sequencer instruments such as Harmony Bloom and Stepic. These rely on additional instrument tracks configured to receive MIDI signals from these sequencers. To get them to work, the record enabled button must be active on the instrument generating the sound. For example, the Stepic sequencer is on track 1 and is outputting on MIDI channel 1. Retrologue is on track 2 and is configured to receive MIDI input from track 1 on MIDI channel 1. The Record Enable must be set on track 2 in order to receive MIDI data from track 1.
When opening a saved project, all of the record enabled buttons are off by default. This means in order to play back the project, I need to go through and enable record on every MIDI instrument track that is receiving input signals from one of the sequencer tracks. The more tracks I have setup, the more tedious this can be. Is there another way to get one MIDI track to accept MIDI signals from another without having to enable record? or is there a way to save the state of record enable in the project?
Keyscape and Omnisphere both MIDI in from Stepic monitors as expected, and monitoring state is retained in C14P.0.20.
Interestingly enough, N14.0.20 retains both record enabled state and monitor state. If I open the .cpr in Nuendo and save the record states, they are actually enabled in C14 when I open the same updated file. Subsequent saving in C14 reverts back to no Record Enabled state. That last part probably doesn’t matter to you, but I found it interesting.
Anyway, monitoring instead of rec-enable should fix that.
Thank you! This is what I was missing. BTW, I’m running 14.0.20 and it’s not retaining the record enabled state when I save, close and reopen the project. [Edit: yeah, I just reread what you wrote… so… never mind this last bit!]
A workaround is to name all tracks that use an external MIDI input with a “tag” and use a PLE to enable Record on all those tracks. Here is an example using “#ExM#” as a track name suffix:
I thought of this solution, too, but I like the monitor button solution. Seems more elegant. But the logical editor is something I’ll need to keep in mind. Thanks!
Tagging tracks is a pretty nifty workaround that can come in handy in many scenarios.
One that I like in particular and is useful in macros, is simply tagging the currently selected tracks. Then you can use functions or PLEs that are only able to operate on selected tracks. At the end of your macro you can re-select your tracks containing the “tag” and remove it.
It’s basically a somewhat convoluted workaround to allow you to retain your track selection.
Here is an actual example that zooms horizontally to include all Parts and Events in the project:
