So happy I am with Nuendo, so annoying it is…
Maybe the problem is in reality on Windows side (Win-11-Pro, 64-bit, 22H2) but nevertheless, since today, Nuendo started crashing when loading the start screen. I was working on WaveLab 11 at that time when opening Nuendo. Everything was fine up to then…
Strange thing might be the Project folder name, where I don’t know where it comes from…
The only chance is to kill Nuendo:
And re-start with de-activated settings:
I’ve tried out several older and different Projects, without success.
Just that now a different error (eLicenser) appeared, while writing this topic…
I’m wondering why this error pops up, especially when I’m not using VST Connect at all…
Does anyone have any idea where to look for?
I’m really getting tired with every 3 months re-installing the PC from scratch…
Just to make it sure for the right understanding:
The SW was working fine all day long without any SW change on the machine…
Just closing and starting Nuendo / WaveLab again…
Once again, below setting does work as long as Nuendo is not closed and started up again in normal mode:
I’m not sure if it does help but Nuendo seems to freeze while/after initializing Display2.
(It is the next message after below picture, but very difficult to catch due to the short visibility)
Meanwhile I think that it’s not a Nuendo issue but rather a windows display driver issue.
I’m using an nvidia T1000 with 8GB VideoRAM
It doesn’t matter if you read my threat. With different setting Nuendo will start…
But just to answer your question: Yes of course!
This I do know very well and I know the difference between eLicensner and ActivationManager…
If there is a problem with the license, you will get a proper message. Therefore, I do think, that there is no issue with license. And it popped up just once.
If you tell me how, then I’ll give it a try…
(Sorry, I don’t know about WinDBG Preview)
It’s just a way to check what the crash was, and really is only good to get a hint for troubleshooting, especially if it’s a plugin causing the problem. Many times there’s no human-readable info in there. It’s worth sending it to Steinberg though, they have statistics on types of crashes.
I don’t know what the issue is exactly, but if it doesn’t happen after a restart, doing a force quit of the Synsopos process can get things going that’s effectively why restarting can fix the symptom.
Is that actually a # sign? Have you edited the field?
No
But this doesn’t seem to be an issue because Nuendo starts without user preferences. And the # comes from Nuendo due to long file/directory names that won’t fit inside. During a normal start-up you can click inside this field and see the full name…
I’ve just installed the latest Display driver from nVIDIA (and yes, of course, I’ve re-started the Machine…) but no change…
This process is not running (at least, I couldn’t find it in the running processes…)
As nothing helped, whatever I’ve tried, if deleted the program references:
At least, I’m able again to work on my current projects without re-installing the SW again.
But now, the trouble starts to find the broken *.xml file within the 1.001 and configuration and preset files…
As a useless request to Steinberg/Yamaha, but if they do care about their customers, then they might provide a tool (someday) to copy/restore all the preferences and settings within their different SW’s. If I find the ???.xml which made the trouble, I’ll post it again…
The freeze causing file is the “Defaults.XML”. (I’ve copied all presets, etc. from my back-up to the newly initialized settings. There were no problems at all. After restoring all 49 files from the Main folder “Nuendo 12_64” the problem was back. After using again, the initial. data and exchanging file by file the problem was back with the “Defaults.xml.”. I’ll send it to Steinberg, so that they can check where the problem is related, to…
(But maybe they don’t have time for it)
Missed to comment my experience. Busy in the rat race…
Indeed, I’ve changed back to Win-10 and changed the settings as described by Steinberg. Since then, the system is much more stable again…
