Ofcourse becasue the “cable is not connected”
No VST plugin will send the MIDI note data back to the MIDI input of the DAW track it sits on, The only direction it can send is through it’s output. Look at the arrows and explain how we get MIDI Data from [VST INSTRUMENT] and back into [TRACK]?
The flow goes from left to right in a DAW:
[MIDI IN] → [TRACK] → [VST INSTRUMENT] → [OUT]
There is no path there, the only way a path could exist is if you were using a DAW like Reaper that has the ability to place VST Instruments post track, like this:
[VST INSTRUMENT] → [MIDI IN] → [TRACK] → [VST INSTRUMENT] - [OUT]
But that would then require HALion to generating MIDI Data for the notes you click on the GUI, and if that was the case you could use Cubase to route it’s output back into a second track, i.e.:
TRACK 1 : [HALION1] → [HALION1 MIDI OUT]
TRACK 2: [HALION1 MIDI OUT] → [TRACK] → [HALION2] → [OUT]
But why would you do all that when a virtual MIDI device exsts, such as the on-screen keyboard within Cubase(?).
You need to comprehend that what you’re expecting would be to reverse direction of the MIDI Data signal flow and go from VST instrument back up the chain to the tracks MIDI input. This would could cause chaos as it would undermine any PDC latency.
Demonstrate a VST instrument that plays notes into the Cubase timeline when you press the keys of the plugins keyboard GUI, and you’d have a point - but there isn’t any.
Not necessarily. The internal sound engine of HALion could be accepting triggers from 1. Its MIDI In port or 2. the on-screen keyboard. It is not necessary to first convert the GUI keyboard events to MIDI events before being sent to the sound engine.
I don’t know how HALion works on this level so this is pure speculation but I would not assume MIDI is generated from the GUI keyboard.
So in this case only Reaper is capable of doing this and no other DAW does this?
Yes Reaper allows VST instruments as an input to that track, as well as the output. (i.e. you can have two instruments on a single track).
The VST instrument you place post track would also need to send MIDI data when you press on it’s GUI keyboard - something HALion doesn’t do on basic note clicks, though, as discussed.
And I really don’t know how many do either, sorry. I’d imagine it’s quite rare as only VST instruments that generate arps and other such data are programmed to send MIDI Data out.
But, as per Reaper you could do the same thing in Cubase by using two tracks, one for generating MIDI, the other for retrieving it. It’s just not contained on the same track as Steinberg wanted developers to utilise MIDI FX inserts for tasks such as this.
But this is far removed from what you’re wanting to do, which is solvable by using the on-screen keyboard in Cubase as per my original reply.
The onscreen keyboard is too small to do what I wanted to do besides the plugin keyboard was used at random and what came out wasn’t planned hence I wanted to use the retrospective recording to retreave it.
1 Like
Oh I can appreciate your frustrations after plotting an idea in only to lose it. I done the same when using Groove Agent to lay in some percussion hits onto a video project a year or so back, I used the on-screen pads and recorded the hits in time to the video - only to find out I recorded nothing. 
And yes, the on-screen keyboard, like a few aspects within Cubase and it’s plugins, is quite small to use. Especially on a high res screen. I only ever use it to play notes across my QWERTY keys if I haven’t got a MIDI Controller with me.
However, outside of that, what you describe isn’t ‘broken’, it’s just how MIDI data flows within most host software.
Dear gentlemen, please forgive me, but I have to say:
“it is broken” it’s the most hilarious thing I have ever read on these boards! 
Sorry for that, couldn’t resist. Legendary thread.
1 Like
Yeah, it is broken. $60 DAW can do this and such “Advanced Music Production System” for over $500 can’t read what its own plugins are doing - don’t you find this hilarious?
What is wrong with you?
I tried in Reaper what you suggested, it doesn’t work.
I used Spitfire Audio LABS and HALion Sonic SE3.
In order to declare something broken, you first have to understand how it is supposed to function when it is not.
1 Like
VST3 plugins don’t use MIDI at all. Anything that looks like MIDI is just make-belief on the surface but there is no MIDI data underneath. The only thing the plugins use are VST parameters.
The host is responsible for converting MIDI into VST parameters that the plugin will understand (mapping). Likewise the plugin needs the host to map its VST parameters to MIDI if that is required.
This is one of the strengths of VST3 over VST2 but at the same time one of the biggest points of critique from the plugin developers.
Anyway @Voxango - Retroperspective Recording only monitors the MIDI Inputs of the system. Halion does not register a MIDI Input, therefore nothing can get written into the buffer of Retroperspective Recording.
However, I think there is something wrong with Retroperspective Recording nevertheless. At least on my system RR does not work when Cubase is stopped. Only when its playing back. However, I am pretty sure it used to work some months ago when I last used it.
1 Like
my retrospective rec works like a miracle, both during playback of sequence or if stopped
[and I have MANY things to say about C12…]
probably there could be some kind of workaround using a complex midi-loop-back connection, a couple of strange apps and probably working only on mac sys
But that’s just some brainstorming, I am not sure of that and, moreover, I am distracted by that legendary “it’s broken” 
Can’t get enough…
Don’t feed the troll
2 Likes
Awesome, can you try to create the following setup?
I loaded a kit on into Groove Agent, any kit will do.
When I then play on the pads or the keyboard of GA or on my MIDI keyboard while Cubase is stopped the field “Retrospective Recording” on track MIDI 01 just flashes.
I did this:
New Project, new midi track
open lower zone key edit
pounded on my midi keyboard
did retrospective rec., Insert as Linear Recording
Worked – a Midi part with the notes I banged was inserted on the track.
Also worked the the Transport command
Steve,
can you also try to route the midi through an instrument onto a MIDI track and see if RR still works when Cubase is stopped? Kindly see my screenshot above.
More precisely, use the pads or keyboard from Groove Agent to generate Note events.
For me the RR buffer of the MIDI track will be filled up if Cubase plays back. When Cubase is stopped RR it just flashes.
Johnny, this isn’t the MIDI out madness that we had been discussing together with @Louis_R , is it?
I’ve experienced issues when routing the output from a VST instrument into a new track whereby RR flashes, but nothing goes in to the buffer. (Such as using Scaler to send scales/strums to a HALion instance, for example).
I never considered that it could be related to whether the transport was stopped though. Just thought it was just a quirk of Cubase overall. But you’re right, if you play the track the RR buffer works as expected. Handy to know, thanks!
1 Like
I did some tests, as I am in studio now
-Yes, it flashes
-while in STOP the RR doesn’t insert anything
-while in PLAY the RR works, so the recording is inserted by RR as linear sequence
That’s interesting because it confirms what I wrote: using some kind of midi loop back app it should be possible
So we all can say: “it’s broken” NOT
1 Like