Back then we looked at a different malfunction and the flashing RR just came up en passant.
Now we discussed specifically RR and I noticed the different behaviour depending on whether Cubase is playing or is stopped.
Different issue, even though once again we’re looking at MIDI being passed by Cubase from a plugin (resp. the output mapper) to a track.
skijumptoes suggested this not me.
Yes diffrent issues, the whole point of the retrospective recording and the issue here is to capture something you have been doing while setting up your sounds. In the plugin you even have the build-in kyboard to test things out. In some DAWs you can have retrospective audio recording with a time buffer you set that can capture anything you are doing in the DAW regardless if it is MIDI, plugin or audio.
nope it’s definitely you 
And I will tell you a story, which happened to me thousand years ago, but still valid and maybe useful for some “broken not” lol
Once upon a time there was a musician tweaking one of his synthesizers, playing and modifying a patch for a bunch of minutes: tweak filter 1, tweak filter 2,tweak envelopes, tweak a knob, play a slider and so on…
Suddenly he reached an amazing setting, but he thought: go on perfecting it!
So he went on, but unfortunately he lost that amazing setting and was unable to get back to where “he once belonged”. Gosh! “it’s broken”!
Fortunately, he had Cubase 12 open, and was tweaking his synth while being in the ‘right midi track’, then hit the magical button: insert as linear recording and… What happened?
Cubase gave back the entire tweaking session, including notes and all the parameters! So he was able to get back to the initial patch, put Cubase in PLAY waiting for the synth to receive all the parameters until the point he liked
What’s telling this story? “it’s broken” NOT 
That you have no idea what you are talking about and clearly do not understand the issue here, and the creative circumstances in which retrospective recording is useful as a tool.
I mentioned how it works in Cubase. It is up to you whether you like the current feature set or not and what consequences you take.
I mentioned how it works in Cubase. It is up to you whether you like the current feature set or not and what consequences you take.
Unfortunately, I have bad news for you - you are wrong, and it is broken! The documentation says the 88 virtual keyboard can be used to triger MIDI notes! @av_music @mlib
here is link to the maual - Performance Controls
The documentation tries to “dumb the language down” for the regular musician as otherwise they would have to explain that there is indeed no MIDI happening inside a VST3 plugin. Unfortunately in this process the documentation became technically incorrect. It doesn’t create MIDI events, only VST events.
The correct sentence ought to be:
“The virtual 88-note keyboard can be used to trigger what would be perceived as MIDI notes but are in effect VST events.”
That would, however, raise more questions than it answers.
Regardless of the above: Even if the keyboard triggered MIDI notes, it states nowhere that those MIDI notes are passed from inside the plugin to outside the plugin. That is something that you implied. Unfortunate writing maybe, but not broken.
The documentation tries to “dumb the language down” for the regular musician as otherwise they would have to explain that there is indeed no MIDI happening inside a VST3 plugin. Unfortunately in this process the documentation became technically incorrect. It doesn’t create MIDI events, only VST events.
The correct sentence ought to be:
“The virtual 88-note keyboard can be used to trigger what would be perceived as MIDI notes but are in effect VST events.”
That would, however, raise more questions than it answers.Regardless of the above: Even if the keyboard triggered MIDI notes, it states nowhere that those MIDI notes are passed from inside the plugin to outside the plugin. That is something that you implied. Unfortunate writing maybe, but not broken.
Sorry, I stick to what the documentation says. Which means the midi recording from within the plugin is broken and needs to be fixed!
All meters are showing it does except form the recording receiver lightbuld which indicates it is broken. Simple.
I wish you all the best and a happy life in your simple world.
I wish you all the best and a happy life in your simple world.
You are doing yourself a big disservice by being ignorant to issues that clearly should have been fixed. So many things are broken in Cubase becasue even users like you can’t acknowladge that and instead they argue about issues with other users and Steinberg never fix them…
In order to record MIDI data onto a track you need to select a MIDI input first, right?
(or use the piano roll inside the MIDI editor or draw the notes with your mouse)
Do you see HALion in the track’s MIDI inputs list? No.
HALion cannot send MIDI data to the track. Some plugins like arpeggiators (and even Groove Agent for instance) have a MIDI output of their own that will show in the input list and which you will use as the track’s input. This is the only way!
Your VST instrument is placed AFTER the MIDI track, so I don’t see how it could send data to it without requiring to set an input first.
Data can only go this way : MIDI Track → VST Instrument
It CANNOT go the other way around.
You’re just mixing up everything there, the audio VU meter, the MIDI activity indicator inside the plugin, MIDI routing… everything. Sorry but ignorance is more like posting 70+ times and you still can’t process what is being said as simple as it can be. (this looks like a manic episode to me but I can be wrong, I don’t remember you going that far on simple topics before)
You guessed it, MIDI Retrospective Recording only uses the MIDI Input of the track…
(or all MIDI inputs for the global button)
How’s this to settle the issue. The discussion being whether or not Halion keyboard produces midi messages vs triggering the internal sound generator of the VSTi.
Put the MidiMonitor midi plugin on the track and start analyzing live events.
Open Halion. Using your mouse, click the keyboard to produce sounds inside Halion.
If MidiMonitor shows that midi data is being sent out from Halion as a result of the mouse clicks in the track, then @Voxango is correct and it is broken.
If MidiMonitor does not show any midi data being sent out of from Halion, then @Johnny_Moneto is correct and the manual is broken and needs to be reworded.
There is really no need for some additional tests with a midi monitor.
The architecture of Cubase is such that if a plugin is supposed to send MIDI events, the plugin needs to create a midi port.
Halion does not create such a midi port, therefore it cannot send midi events.
It seems the above is undisputed.
Voxango seems to take an issue with the wording in the manual suggesting that Halion should indeed be able to send MIDI events.
Personally I think that this is one possible interpretation of the text in the manual but not the only one.
Voxango states that the program should work exactly as described in the manual or, more precisely, as per their interpretation of the manual.
I am not saying that they are right or wrong with their expectation. I am just not interested in this part of the discussion, that’s why I opted out.
