I just got a session corrupted out of the blue in N14.0.40 ( I wasn’t even really doing anything. Session was idle and one of the autosaves didn’t happen due to session corruption).
Since the only fix I care about in the release notes isn’t really fixed, I’m rolling back to 14.0.32
Okay, Timo.
I hope the report I have made, and the dump files could help to investigate the crash!
I don’t know what’s the cause behind it, but I’m not the only one to experience it. If there are a specific hardware requirements that are not covered by my HP Z820 2x Xeon 8-core E5-2670?! It’s an old workstation, but still serves me perfectly well for music.
@TimoWildenhain, any words about the first fix of the list, regarding automation values returning to original upon deletion of first automation point, not really being fixed?
Thanks
Besides the internal DAR bug I noticed yesterday, I’ve already tested that the Z-axis issue seems to be resolved, and ADM file objects created in Nuendo finally appear in the correct positions in the standalone Dolby Atmos Renderer. Thanks to Steinberg and thanks to Dolby for the good communication with Steinberg after my posts about this issue .
But I’d like to ask once more — is it really that difficult to make Nuendo capable of using the external Dolby Atmos Renderer in Mac Silicon mode? That would be a huge advantage, as it would allow us to use analog and digital outboard gear for Dolby Atmos mixing. Right now, Nuendo’s internal renderer can’t export a Dolby Atmos file in real time — only offline! But this can be achieved with an external DAR.
Likewise, the problems around ARA2 remain:
whenever you have ARA on a clip you get a loud POP at the beginning and the end of the event and gain automation is baked into the file.
Still no fix for this!
Thinking maybe this update should be pulled until this stuff is resolved with another update/hotfix. Combining the Cubase and Nuendo update schedule has obviously not gone as smoothly as desired. Nuendo needs to be completely solid.
Thank you for your feedback on version 0.40. Since this is a rather big maintenance update, it is important to learn about unwanted side effects quickly.
That said, I officially confirm that there are at least 2 issues in relation to Dolby Atmos projects, which is why at the moment
I strongly recommend not to install the 0.40 update in case you work with Dolby Atmos.
Please use the 0.32 version instead until this issue is resolved (we’re working on it). The previous update can be downloaded from the Steinberg support section: www.steinberg.net/support then DOWNLOADS dropdown.
Thanks Timo, It’s just a shame that it was released with a broken major component and having to receive forum user feedback for Dev’s to realise this! Regards