It’s a know and confirmed issue for nearly 4 years.
How long did MDC (midi delay compensation) take to implement?
Is there a MIDI delay compensation? 
What does it do, compensate for 1 to 2 ms MIDI message latency? 
It means that notes are recorded in the sequencer when they are heard and no longer does anyone need to shift all notes by a specified number of milliseconds.
Guess the fact I can’t hear MIDI notes, explains why I never missed a so called “midi delay compensation” feature.
yeah, needs to be fixed.
not to overlook is the fact, that when “wrong” fixed, a live recorded automation at large buffersize may sound different (earlier) in playback, than while you were creating/recording it with your controller or mouse.
so there has to be compensation for that, too. just like the new midi compensation… so that in the end “what you hear is what you get is what you see is what gets bounced”.
best regards
Hi,
I’ve noticed some delay in Channel EQ automation. Here is how to check it:
- Create a mono audio track.
- Insert Test Generator. It will start generating a sine wave with 440Hz frequency.
- Set one of Channels EQ band’s at 440Hz and select Parametric II as the band’s type.
- Create the band’s gain automation. Simply, drop Gain from 0dB straight to -24dB, hold it for a beat and bring it straight back to 0dB (see the image attached)
- Render the track and open the rendered file.
Now you can compare VST automation with its actual effect.
In my case (120bpm), Channel EQ has approx. 1/16 note long delay, then approx 1/32 note long fall down to -24dB and approx. 1/32 note long recovery. One can hardly use such an automation for a quick tracking.
Studio EQ doesn’t have any delay before getting into the action but is still very slow.
3rd party EQ (MEqualizer) reacts much quicker.
Makes me wonder about a sample accurate VST automation… Looks like a bug to me.
Thanks,
Vitaly.
Maybe related to this: Automation playback delayed based on latency? - Cubase - Steinberg Forums?
Kris.
Has this been swept under the rug by demoting to “miscellaneous” section?
Apparently so 
this is one of the biggest bugs ever!
just imagine the many many scenarios where this issue influences your project to the bad!
As the latency in your system changes (eg add/remove plugins or change sound card buffer size) then the amount of delay in your automation also changes
This makes precise and detailed automation very difficult in Cubase.
Tried Halion Sonic SE yesterda, had it loaded as instrument track played some piano and wanted to fade in with the cutoff filter knob, but it’s movement did not get recorded in the instrument track, ofcourse the automation was on
thoughts?
off topic!
please open a new topic, this here is about latency-dependent automation
no offense 
EDIT:
oh, sorry, I just noticed that some topics were merged here, that don´t match! Please Mr. Mod, can you split the topics again?
just a little bump
I agree completely. 
I use a LOT of volume automation. When I upgraded to 7.5, I immediately started using the alt to transient feature to place automation…and immediately started noticing some weird behavior in a snare track I was manually gating.
I did some real time exports of the track (I have to use real time because i always end up incorporating hardware into the mixes) and i found that not only were the transients often getting chopped off, every export was different!
Obviously to people contributing to this thread, this is old news…
So, I realized I would have to back up the automation points so the inconsistency was happening at less crucial moments.
Question: does anyone know the least amount of time I could get away with moving those points, given that I am at 88.2 and 1024 buffer setting?
I figured 1024 samples at 88.2 KHz came out to about 12 ms…
Question: does anyone know the least amount of time I could get away with moving those points, given that I am at 88.2 and 1024 buffer setting?
Any figure you get given may be right on the users system but that doesn’t necessarily mean it will be the same on yours.
I would test it for yourself by automating mute or sudden volume change (no ramping) on a test signal (place the change exactly on a beat) and bouncing it down, then zoom in and see how far off the beat the bounced audio changes.
You can switch the ruler to samples or ms and then use that figure exactly to shift all your automation. (Or in the case of drum transients you could always add a little extra to be completely sure (as I also wouldn’t trust the transient detection to always be exact)
Drats… this could take some time to figure out. Thanks anyhow!