When I automate parameters in N14 and have activated “Fill Loop”, Nuendo does not write the parameters exactly into the loop, but creates small ramps at the beginning and end of the loop. Why is the automation data not written exactly into the loop? This leads to unwanted automation ramps, although I actually want to have jumps to the other automation data outside of the loop range.
Is there any setting that prevents this behavior?
Here you can see that I wanted the automation to jump from one setting to another where the two markers meet but instead there is a little ramp (which is audible in this case because it is an EQ and I obviously don’t want that).
anyone any ideas? 
does anyone experience the same problem or is it only on my system? A strange thing is that the position of the ramps varies with different buffersize settings on my soundcart. And it is possible to correct the automation points manually (that means jumps from one automation point to the next point are technically possible) but that can’t be the soultion 
It’s really just a guess cause I’m not sure if this should apply in your case. But for the sake of it, have you tried messing with the return time to see if it has any effect on it?
thank you yes I tried that, but it didn’t change anything. I also tried different Asio Guard settings (and disabling Asio Guard) and changed the “precision of volume automation” in the studio settings → no difference.
Also, for comparison I checked how it works in Pro Tools and there it works as it should, it writes the automation data exactly into the loop selections and doesn’t create any ramps. That’s what I expected in Nuendo as well…
This is an odd one that I haven’t noticed, but will keep an eye on if so. Just one thought that cames to mind is did you happen to have Cross-over selected in automation window? could be trying to smooth back to existing automation point. Not sure.
nope, makes no difference if touch, latch or cross-over is selected…
I tested it a little further and the “reaction speed” (don’t know if it is called like that in the english version) changes the speed of the outgoing ramp for whatever reason. The ramp at the beginning stays the same, at every setting. I tested it with 1ms (the lowest possible setting) and 100ms:
That has to be a bug, doesn’t it? Or at least there should be an option to set it to zero. I also tested it on different computers and also with N13 (same problem).
Just to chime in I’ve experienced this behaviour too - been working around it at times to avoid audible sweeps when punching in EQ changes
1 Like
yes, thats exactly why it is an annoying bug… I was hoping to use the same preview and punch to loop/selection workflow as in Pro Tools but these little ramps are audible in many cases (like EQ changes, as you said) and therefore I always need to extend the selection/loop manually as a workaround, which is timeconsuming and annoying. Hope there will be a fix soon dear Steinberg Team
