(Cubase 14 Pro, last version today, w11)
To limit MIDI data copying between VST instrument tracks, I use a dedicated MIDI track that feeds instrument tracks either directly or via SEND. In total, one master MIDI track can therefore handle MIDI data for up to 5 instrument tracks.
Having discovered that the fader of this master MIDI track sends CC7 signals to the slave instrument tracks to control their volume, I made sure that the plugins on these slave tracks were responding correctly to CC7 signals. Up to that point, everything worked fine.
Then I wanted to implement an automation curve on the MIDI track, and that’s where disappointment and perplexity came in: while the automation curve does indeed control the master track’s fader, and curiously generates an identical CC7 automation curve in the MIDI track opened in the Key Editor (which can be visually examined below the notes), these CC7 signals are unfortunately, and unless I’m mistaken, not being sent to the instrument tracks. Yet, simply moving the fader sends the CC7 signals without any problem. A mystery indeed? Bug, unfinished concept, or user error on my part?
I found a workaround by duplicating the automation in each instrument track, but to do this I had to create empty MIDI events in each one, because it’s impossible to add automation to an instrument track without MIDI data in an event. This requirement to create an empty (fake) event introduces a serious flaw in the concept of sharing MIDI data but the problem is why the CC7 automation is not sent when the fader CC7 are ?
Hi,
It works on my side.
I have a MIDI Track and an Instrument Track. I route the Send of the MIDI Track to the Instrument Track. I verify the signal path by adding a MIDI Note to the MIDI Part of the MIDI Track. I can see/hear it from the Instrument.
I move the Volume slider (in the Channel section, or the Inspector) on the MIDI Track. I can see the Volume (MIDI CC7) slider on the Instrument is moving.
I show the Automation track of the MIDI Track and select Volume (it’s the default one). I draw the automation curve and play it back. I can see the Volume (MIDI CC7) slider on the Instrument is moving.
I open the Key Editor of the MIDI Part, show the MIDI CC7 Controller lane, draw the MIDI CC curve, and play it back. I can see the Volume (MIDI CC7) slider on the Instrument is moving.
Am I missing any other way?
Could you take time to better replicate my config.
- I have an HALION multi-instrument directly as output of the midi track.
- and 2 other instruments as send targets for the midi part : Kontakt 8 multi and another instrument as Retrologue or an Arturia instrument.
Thanks.
I also cannot reproduce the described problem.
On the screenshot I drew in CC7 midi events. It gets send to the two instruments and they both react to the incoming data.
Using VST automation instead of CC7 the targetted instruments still react in the same way.
Thanks for yours answers it helped me understand my pb.
In fact it was the plugin !
I am using in this tracks the AAS Player which curiously understands automation created directly in its track, but when the automation is created in the midi track containing the data, it is not propagated to the AAS player.
I tested same configuration with Kontakt 8, and the automation of the midi track is correctly sent to plugin.
May be because the shared automation is sent as CC7 and AAS player does not obey to CC7 and have no midi learn feature.
1 Like
That would indeed be a prerequisite.
