Preview is a tricky one.
The thing is that preview is not bufferred, which means that all is done real time on the CPU and RAM.
Which means that if your computer hasn’t enough juice left to process the preview, either nothing will happen or in the worse case, you will crash. If you have enough computing power left, then there must be a bottleneck somewhere else.
Fredo, with all due respect, there is NO condition that should cause Preview to crash or exit unexpectedly. Period. If the app can’t do it, it should decline gracefully and not take your work with it.
In my case, there is/was plenty of CPU/RAM available.
And I would definitely not call this a bottleneck. The stack trace says it’s a crash in a piece of Nuendo code. That is entirely preventable. It’s a bug.
Unfortunately, I can’t spend time trying to reproduce this, especially since the result is a crash.
I just tried to explain what was probably happening, you read it as excusing what was happening.
You are right about the fact that anything that makes the application crash is considered a bug.
Proper behaviour is that preview is grayed out and/or plays back “crackely”.
Now, as far as the problem is concerned, I have never run into this and I haven’t seen any reports about it too.
I would, Max, but in the middle of a project. Can’t disturb the environment. When I get some downtime I’ll try some things. In fact I’m still on 5.1.0. Haven’t wanted to risk 5.1.1 on a deadline.
I’m pretty sure if I just remove Nuendo from my machine I won’t see the bug at all!
