I upgraded to Nuendo 15 immediately upon its release because of the increased video export options. Those options worked excellently.
However, errors are now occurring in areas where there were no issues before. When I start exporting or freezing an instrument track, it never finishes. I’m not sure if this only happens when there is a video track in the project, but even after the export is complete, the popup doesn’t close and the timecode continues to run. I had to force-quit the program every time this happened. I have no choice but to use Nuendo 14 for multi-track exports.
I am a Windows 11 Pro user. Has anyone else experienced the same bug?
This issue does not occur when using Real-Time Export. There is also a way to tell in advance that the export is going to fail: during export, the timecode burned into the video displays a value later than the timecode at the intended IN point of the timeline range being exported. If the export is cancelled and then attempted again, that same timecode usually does not restart from the correct IN point, but instead continues from where it had stopped previously, generally at a time value even later than the desired export OUT point.
That’s because the video engine, especially if you on Blackmagic, demands real time export. If that isn’t what’s going on with Cubase, it will freeze and screw up.
Here’s from Chat GPT:
Cubase Render in Place thread is waiting on the DeckLink video subsystem, which never returns (deadlock / blocking call).
Why this happens:
Render in Place = offline processing (faster than real-time)
DeckLink driver = expects real-time video clock / SDI sync
Result:
Cubase tries to render instantly
DeckLink waits for valid video timing
Both wait → freeze
Important detail from your dump
This line is the smoking gun:
decklink mini monitor
That means:
Your DeckLink Mini Monitor is actively initialized
Even if you’re not “using” video visually, Cubase still hooks into the card
So if you’re doing audio exports or Render In Place, Mute the video first on the video track. That’s the workaround I’ve found so far.
Important detail from your dump
That means: