Set the output on the midi channel to the instrument channel
play your midi and it should make some sound.
Add midi-insert on the instrument track. Monitor will do.
Watch the monitor during playback. The midi channel send data to instrument channel without passing the midi-insert chain.
It is expected that midi-inserts are applied on all midi input for a instrument.
A other observation is that you can connect to a instrument channel as midi output. But you can not select a midi channel as input for a instrument track. This implies a midi mixer and that might be good, but would also be good to see all input-output on that mixer.
If you look in to the monitor you will see nothing. Is it not obvious that if you do not have any input then you can not do anything with nothing. If it was doing anything that was not right then there would have been a monitor before and after.
Now it is only monitor on the input, and there is no events there. However the VSTi get input.
I don’t think this is a bug, just the intended behavior, that the Midi-data from the Midi Track gets routed directly into the VSTi, ignoring Midi Inserts, Modifiers and Sends.
You can put all the Midi Inserts, Modifiers and Sends you want to use directly on to the Midi Track, if you want to use them.
If it is intended it is in the documentation. And it very confusing to have a input monitor function that does not cover all inputs. Eg notes that you can not easy trace where it is origin from.
Yeah but it’s not an input monitor. It doesn’t specify “Input” anywhere. It just says Midi Monitor. So it’s monitoring the Midi on the Track.
I agree this isn’t exactly intuitive, but changing this would create way more problems than solving it.
If the Midi Data gets inserted before the Midi Sends, it would severely limit how you can route Midi between different tracks, as this will create feedback loops very easily.
Expression maps also send midi data. If you have an expression map on the Midi Track, but you want to use some Midi Effects like randomizing position or length on the Instrument Track, it will mess up all the keyswitch data, cause this gets randomized too.
If all incoming Midi also goes through the Instrument Track’s Expression map it messes up even more things.
Cubase desperately needs a better option to monitor midi. I always load Kontakt and check with the Midi Monitor Multiscript what Midi actually comes in at the instrument level. This should be possible without having to rely on 3rd party plugins. But it should be added directly inside the VSTi instrument window.
There are many ways to solve this. One way just to make a midi flow-chart and document the lack functionality. This would be good even if they do a change to solve this. And yes, it need to be backward compatible and I think that can be done with something similar as they do for audio-send effects where you have post-or-pre fader selections.
The only time I use Midi tracks is for recording my hardware synths…you can fix flubs and such and then send it back to the synths to record the audio outputs. For software instruments it’s always Instrument tracks, you get the Midi track to play with but it’s already hooked up to your plugin for bouncing to audio
