When i open a Atmos Project or open a template from steinberg - then the Renderer plays only 1 Channel per Bed!!! - had to go back to 14.032
This is documented and being fixed as we speak. Steinberg recommends staying on .32.
Then, honestly, if ādocumentedā, there should be a warning on the download page.
Mark.
2 Likes
Completelely Agreed, itās a broken update, itās happened, no excuses, and very good practice would be to clearly state the issue next to the downloads (on site and download assistant) Otherwise itās like Steinberg are saying that the source of reliable support information is basically the āforumāā¦ā¦and this is not a āsupportā forum.
1 Like
They should mention it on their release note but thats what forums are for. As mentioned, there are other fixes available, and not everyone uses Atmos. Those who do should avoid it.
As a warning- Do not Open and Save Your Atmos Project
What Steinberg should do is create a separate forum section for technical alerts and post issues there. Each issue being marked as verified or potentially under investigation. Verified issues should have the bug tracker number on it for easier communication.
This way users know where to search for verified issues as they pop up which is going to be much better than having a million posts with people asking about essentially the same thing in a million different ways, each time forcing other users to decipher the description and go through reproduction steps.
It would also allow users to set up alerts for new posts in that section. By doing this it would mean that if a new post pops up Iād get a notification about it right away and could react to it right away.
For āprofessionalā software I really think this is the bare minimum.
(guess who does this)
Iāll put this in my upcoming feature requests.
6 Likes
I am about to pick up a big Atmos project started a few weeks ago. Luckily I seem to have dodged a bullet here. Also, luckily, my current 5.1 project seems OK.
Wow! Just wow!
Since updating my computer to a Mac Studio, Iāve been working on adjusting my workflow towards migrating to the Nuendo internal Dolby Atmos Renderer. However, the more I hear about bugs with the internal renderer (here, and as revealed in the release notes), the more Iām thinking how I really donāt want to have to spend time baby-sitting it to make sure a new renderer bug hasnāt surfaced. 
Removing the renderer and re-inserting it temporarily fixed the problem (weird). But after closing & restarting the project it goes back to this behaviour
Best option is to immediately go back to 14.0.32ā¦ā¦messing with this new update is probably not worth your time/energy
I installed patch 40 for bot NUENDO and CUBASE, unfortunately. And I manage alla my projects with DOLBY ATMOS from the start. I never reverted to previous patch, is it a SAFE process? Will it be easy to install/reinstall further patches from Download Assistant? Thank you
Hi! it is safe to go back , i did it (had to do it) even all midi remote works fine again. (on mac) - all the best!
Iāve not dared open an Atmos project in .40. But while Steinberg seem to indicate that this is a Windows-only issue, I have seen reports of problems on Mac (Iām on an M1 Studio). Any clues as to what is the actual situation? 
Hi! i am also on a MAc Studio M1 Ultra .. and the .04 problems are quite the same - i had to go back to .032ā¦
1 Like
Thankyou. I think that Steinbergās messaging on this has been poor, and that the .40 update should be withdrawn. IMHO.
2 Likes