Hi, All. Have been meaning to post this for at least a couple of versions.
If I’ve been working for an extended period of time–I’m talking several hours-- or left my project up while I go and do something else, there’s a good chance that sometime, after I start working again, Nuendo will freeze, with audio still playing-- meters stuck in place, entire computer non-responsive. If I’m lucky and don’t touch anything, after a few minutes (anywhere from 1 to 5+), things will start running again. If I’m not lucky, Nuendo will crash with my work up to that point unsaved. When Nuendo either crashes or returns, the computer itself once again works as it should. It’s not necessary to reboot the computer for Nuendo to run as it should; restarting the application brings things back to normal–until the next time.
This has been happening from at least the first release of N10, and I’m pretty sure it was happening on 8, as well. This has happened on every computer I work on (laptop, remote location iMacs, my desktop). You can see my RAM numbers in my sig.
For the sake of simplicity, what I’m describing happens in my most basic production (and source of longest marathon sessions), audiobooks. For these I am entirely “in the box,” and using only Nuendo’s included plugins-- compressor, expander, de-esser, brick wall limiter. RX is used as DOP, and for batch pre-processing.
This has happened using at least a couple of different interfaces, and audio buffer does not seem to make a difference.
I’m scoring a TV series right now, which is much more plugin and VSTi-intensive (a lot of UAD and others, plus Halion, Addictive “everything” and some other stuff), and I’m NOT experiencing this issue when working on music. I’m assuming that’s because I’m just not spending as many consecutive hours in those sessions.
Just wondering if others have experienced this issue, and if so, if they’ve (you’ve) found a way around it. My workaround has been to do a lot of manual saving and to restart Nuendo at the first sign of misbehavior (it sometimes hiccups a warning before a full freeze). I’m fine with that–nothing wrong with improving my working hygiene, but if there is in fact a way past this it’d be great to be able to just rely on autosave again and not worry about crashing after forgetting to hit ctrl-S for too long at 3am…