For me, the “Render in Place” function in Nuendo 15 freezes when used on a project coming from Nuendo 14. When I open the same project in Nuendo 14, the same instrument track on which I apply “Render in Place” works perfectly.
Please, I kindly urge you to fix this extremely important function!!!
Yes, I’m on Windows 25H2. When I use the “Render in Place” function a new project in Nuendo 15, it works fine. However, when I reopen a project (with video) that I originally created in Nuendo 14, the “Render in Place” function freezes and the timecode keeps running endlessly… Do you have a solution for me?
This may be plugin specific as its possible that aspects of N15 and some third party plugins have affected the way N15 interacts with windows explorer (25H2). It may not be related but I was getting alot of freezes and think the culprit for me was sonible plugs
his bug has occurred again, but this time during an audio export:
During the offline rendering process, the timecode keeps running indefinitely even though the selected range has already finished. Nuendo becomes completely frozen, and it’s impossible to click “STOP.” I’m forced to quit Nuendo using “End Task” in the Task Manager.
On Nuendo 14, there is no issue at all—the render completes correctly, using the exact same computer and therefore the same plugins.
Yes I can confirm for me as well I keep getting freezes when it reaches 100% and the files are finished etc but Nuendo won’t return and stucked waiting. Dmp files indicate some kind of deadlock with windows and it could be an incompatibility between latest win update and N15.
I’m experiencing the same problem.
It only happens when the video player is displayed on the screen, so I close the video player before rendering.
That way, I can export successfully.
In any case, I hope for a quick fix.
Thank you all for your feedback and for sharing your experience regarding this Nuendo bug. I am currently in a very busy work period, so I’m unable to provide more information for now. Normally, I’ll be finishing this week, and I will then provide you with a .dpm and a project where, in my case, this bug occurs with every render. Indeed, I believe this bug is related to the type of video added to the project (MOV, MPG, and possibly the different resolutions…).