Thanks for the suggestion. I’m really not sure whether it’s feasible for us to be able to show the real waveform for a given note in the Key Editor. But we do know how important being able to set default offsets for different samples is, and this is something we will definitely add in future.
That is good news Daniel. Surely if Cubase/Dorico can find the wave form to play it, it can represent it?
Surely, Dorico passes MIDI data to the VSTs, which generate the audio wave forms. You’d need some ‘feedback’ mechanism for the VSTs to pass the audio back to the host app; and I suspect the amount of CPU work to display the wave forms of each note would be non-trivial.
Yes on reflection - your probably right. I should have known that Daniel knows more than I. Maybe with MIDI 2 if this ever comes out of the crypt.? This is much more 2 way. Editing offset on a note by note basis might still be possible though
I got Tokyo Scoring Strings during the weekend, it has a look-ahead feature that works like a charm with notation but it needs an offset of -1000ms. Dorico can handle that but I’m encountering an aspect that makes it a bit cumbersome (totally useable though)
Unless I’m missing something, you have to do it on a per-note basis. Ideally, it should be configured on a per-articulation basis which is triggered without having to enable the offset manually for each note. If that’s hard to implement, it could be implemented the way it works in most DAWS: you set the offset per midi track, in Dorico’s case I guess it’d be the instrument.
Having some more thoughts.
To make a representation of a wave form in the key editor, for a single note, whilst editing it, is not such an onorous task CPU wise, as one only would need to deal with one note, not the whole instrument.
There must be a point IMO where the audio file is delivered to the track and outputs in Cubase/Dorico. COuld it not be copied from there? Of course I am an amatueru here and do not know the code or difficulties. One only needs to deal with one note at a time.
A further complication though, that I did not cosider is the layering, perhaps crossfading, which typically happens on a per note basis in a VST instrument.
For example, if one were to play/display a C 3 in the key editor and somehow set an offset for it, but then decide to change its dynamic from FF to pp, then this would typically be a different sample - potentially with a different offset. This would have to be factored in.
If it were not possible to reflect the actual wave form in the Key Editor (or below in the lower pane), then a second best would be some kind interactable of art drawing in the key editor - a visual representation of the functions required.
Editing offset’s on a note by note basis AND articulation by articulation basis is the ideal and would give most accuracy
you can set the Steinberg MonoDelay plug in Dorico as well at track level. I used it for a time when a script with Cinematic Studio libraries required it.
Oh, that’s awesome. thank you! I’m testing it. How do you create a negative offset with it? Like -1000 ms?
this gives you the basic instructions MonoDelay
It’s important to remember to click on the little the tempo synch button to disable so you can set it manually to 1000ms. Also you must set the feedback dial to zero.
Thanks! I did that, but that generates a delay of 1000 ms, not an offset of -1000 ms.
Unfortunately it is not a time machine, but if you offset everything else by 1000 ms, you get the same effect 
Yes, delaying everything else seems like the way to go.
Thank you guys!
yes – I think that’s what I did with one arrangement.
Back on Topic: If the sound of a given MIDI note/articulation can be played in teh key editor, gthen surely it is not a huge task to represent that wave form in Cubase.
Z