Hi,
In my project I use a Chord track, created from an audio track and used as input for some HAlion instruments.
I also have a GA5 track loaded with a preset from Simon Phillips, this track has no input because I don’t want to receive any midi, using the GA5 templates to fill its midi events…
But when I select it and play the project, On each start of chord from the chord track, Groove Agent plays one of its instruments (cymbals).
If I select the chord track, there is no more any instrument played in the GA5 track on new chords.
I closed and reopenned the project but no change.
It seems to be a bug ?
It sounds like you have the Chord Track set to playback on Monitored Tracks and your GA5 Track has its Monitor button Enabled. I think there may be a Preference that Enables Monitoring on the Selected Track - but I’m not totally sure.
There are 3 ways to resolve this
- Disable Monitoring on the Track
- Set the Chord Track to playback on one specific Track, which could even be a dummy Track
- Mute the Chord Track
Thank you @raino I will have a look on this as soon as I am back on Cubase.
Chord track seems more subtile than I was thinking 
So I checked and :
- Chord track is effectively set to playback on monitored tracks
- But GA5 track has not its monitor enabled
I also set a midi monitor in GA5 and no midi input is coming from anywhere.
Here is a small video showing that GA5 track is playing on each new chord ???
And I can’t mute the chord track because I need it for some HALion tracks ??
EDIT: I just discovered that turning off the Record icon on the GA5 track suppresses the sound played on each new chord.
For me it is a bug because I can’t see any usage of all this.
As no midi goes between Chord track and GA5 track, it seems that GA5 is receiving some internal signal and plays the instrument corresponding to the chord note.
It does not seem to be related.
I pratice midi since years and midi thru simply states that incoming midi will go through tracks with recording enabled.
In my case midi monitor sees nothing as incoming, the problem is Chord track 's code related.
Some signal is triggered from Chord track to vst3 with monitor and/or record enabled.
Another side effect of this is that Olympus Choir (from Soundiron), set as HALion instrument in a track and monitoring, reacts with a peak in cpu/disk access (64 Gb RAM, large SSDs) on each new chord, where Voices of Passion (East West inside Opus engine, not HALion) sees nothing special as if its Opus engine was not reacting as Steinberg VSTI to this internal signal triggered on each note by Chord track.
I hope Steinberg will read this and fix it.
Well, I did test it before posting here and it sure seemed related to me.
Did you actually try it, or just decide because of…?
This is a side effect and I need midi through when recording.
And on your side have you tested what I related here :
1- One non muted chord track with several chords (prferably created from an audio file playing chords or solo notes, and sending its chords to any monitored tracks
2- several monitored instrument tracks (HALion), muted
3-One GA5 track, non muted, non monitored track with an instrument preset loaded and some bars filled with midi from one of its presets, no midi input source, stereo output.
Do you encounter the same pb as me : when selected and playing the project the GA5 track triggers a sound on each chord (no midi traced in midi monitor attached)
Have you experimented this please ?
I installed midi monitor in the GA5 and nothing goes through so the midi passthrough you invoked as a solution is, as I said ealier, a side effect, just as the removal of recording ready mode for the track which removes the parasite sounding in GA5 or the CPU peak on HALion on each chord from chord track.
You must agree it is a chord track bug, or some Steinberg’s bug between chord track and its vst3 instruments (because other editors seems not affected).
Well if you require that Track to have Monitor Enabled. Then use one of the other 2 methods above.
If you want to have more control over which Tracks listen to the Chord Track, here’s a workaround so it looks like just another MIDI In.
Very nice trick, thank you,
I agree with you why, why, why Steinberg do not allow Chord track to be a midi input as the others ???
… and fix the bug I reported here.
Hi,
If you select the GA5 track, the Record become enabled by default (you can change this in the Preferences), therefore the track is monitored.
Yes I know but I have the prefrences set to not enabling record when selecting.
The problem here is what is triggered by chord track able to peak cpu in monitored halion tracks or generate a sound in not monitored GA5 track ?
Hi,
On the video, you posted, I can see the GA5 track is record enabled. Therefore it receives MIDI data from the Chord Track.
May be but I tested the 2 positions.
Moreover I traced some midi emited by chord track and I am puzzled by two lines in the saved midi log.
One is Chord Symbol and is certainly related to an internal NRPN to signal that next notes are part of a same a chord.
Next is VST3 Event, and this could correspond to this unexpected signal sent to GA5 or HALion, and triggering a GA5 instrument or an HALion CPU peak.
I would appreciate to know if there is somewhere a midi translation for these NRPN messages ?
See
Hi,
Could you attach a screenshot, please?
Cubase doesn’t translate NRPNs. Instruments do so.
In this case these NRPN are supposely generated by Cubase if you have followed.
Hi,
Could you attach a screenshot from the MIDI Monitor to see the exact messages, please?