I suspect that automation code is so complicated and perhaps not so well documented that it is difficult for the development team to work on it, restructure it, and finally get this sorted out.
No other explanation because this is a feature that should work flawlessly since four years for Yamaha corporate image to avoid loosing market share in the Protools area.
Another point that show a probable difficult code base to work on, is that Nuendo 10 is not object (event) oriented yet. Automation is still only track based, compared to other software that did implement object automation sometimes decades ago (Samplitude was the first well known one).
If the code base was easy to work on, i think that Nuendo would have been object oriented when the Direct Offline Processing function was introduced. A true object oriented engine is better because it does allow to have realtime automation on events, as opposite to DOP that is only static.
So i feel that DOP implementation was decided instead of a true realtime object oriented engine, because the code base was not so easy to work on. DOP was probably a lot easier to implement.
Nuendo will need to become object oriented as soon as possible. Track based automation is really a thing of the past, when tape recorders where everywhere.
Event based automation is better than DOP when working with a lot of events that cannot share a common track based processing and need realtime automation.
We cannot know we are not part of the team. This would be a reasonable explanation, but it could also be that Steinberg has a policy to always treat new features with a higher priority than bug fixing.
Too late for me, PT has almost no bells and whistles, but it gets the basics right.
And PT has it for EQ and Dynamics, also snapshot automation of plugs works flawlessly.
Audio post had been shouting for years on this forum, instead they got game audio integration.
Again, we do not know. We are not part of the team. but the fact that this feature is still broken 4 years after it was introduced is not okay. On the other hand the DOP desaster in N8 with broken RX integration is hardly what I would call an example of someting that was obviously easy to implement.
Helidream: As a Samplitude user since version 4 I’m absolutely agreed with you that Nuendo should be event oriented. DOP function is not so fast as Samplitude’s realtime object editor.
I can confirm that VCA destinations are still forgotten in a template when I enable a track from disabled state. This is enormously frustrating. Cubase doesn’t have this problem.
Thanks but the dev team has known about and confirmed these issues quite a while ago. If you could convince them to make it a priority to fix that would be great.
The Nuendo-Wwise integration is weird and I don’t know anyone who uses it. I don’t think it’s received any updates since it’s original release.
Most game audio people I know now use Reaper. Some still use Pro Tools or Nuendo (like me) and keep talking about moving to Reaper but never find the time (like me!).