Spent the whole day on a mix - saved many times as per usual - shut N5.5 down - took a break - came back to check the mix - and… the project now takes about 5 minutes to read (after repeated attempts) and finally opens…
But here it is… when the project does finally open - it’s WRONG!!! Missing inserts on vocal channels, etc, etc. It does not even resemble the mix.
Ok, if this was a one-off I’d understand, but it’s happened sporadically the last few days. There was a problem with this at one stage with version N2 I think. But, this is just crazy!
I opened a feature documentary surround mix that was near completed in 5.1.1. Opened in 5.5, did a days work with the clients. Opened again the next day and all of my inserts on ever track were automated to bypass.
Finish your old projects in 5.1 or earlier… start new projects in 5.5. That’s just superstition talking.
What OS, machine & Slate plugins are we talking about here please?
I use VCC all the time on N5.1.1 & 5.5 on XP/32 and have never seen this problem…but am now worried.
Can you please give some more details & an attempted repro so I can check here too?
I’m running W7 64bit and Nuendo 5.5 in 32bit mode.
What seemed to happen is that 5.1 projects with VCC, opened in 5.5, then saved, became corrupted… Scary!!
The worst of it all is that most of the projects were ok. I have a feeling that the ones that were ok were projects where VCC was only inserted after the projects were opened in 5.5 (saved in 5.5 without VCC first…)
I will be doing extensive testing over the next few days. Saving new versions before certain plugs are inserted, etc. Also saving the individual channels of the mixer…
This is a really terrifying one for me. I will keep you posted…
Loaded 5.1 project. Saved as 5.5 project. Closed project. Re-opened project. Started setting up the mix in 5.5. Saved. Closed the project. Re-opened. Noticed that one of the FX busses was missing plugins that were there from the original 5.1 rough mix. Went to re-insert the plugins and Nuendo crashed…above message. (no Altiverb here)
The problem seems to be the loading of some VST 3 versions of plugins that were saved in the 5.1 project.
Ok, from the last post. The FX track that didn’t load correctly was the VST 3 version of Softube’s Tzar. On the corrupted FX track I can load the VST 2 version. As soon as I load the VST 3 version Nuendo crashes. Now, I tried the same thing with Steinberg VST 3 versions and VST 2 versions on that corrupted track. Same thing.
However, if I add a new FX channel and select a VST 3 version plug there is no problem… So, for some reason some individual tracks are being corrupted.
Nuendo 5.5 is sporadically corrupting mixes done in 5.1…
After importing the track archive of my 5.1.1 job into 5.5, things went well for a day or two. A few minutes ago, I opened up to find that again there are a few track that have been reset and rerouted to to the main outputs instead of where they are supposed to be.
I’m very fortunate that this particular job has an open ended deadline because I will need to start over.
Why this was not documented or mentioned during the roll out of 5.5 is very irresponsible. I find it hard to believe that this was not found in the beta testing. This is NOT some new version of a video game here… this is how I make a living. I’ve stood by SB and waived their flag for years. I could have lost many thousands of dollars on this and I’m extremely lucky.
Techincally, I’m not sure if I can go back to 5.1.1. I’ve done significant amounts of work in 5.5 at this point and there are other reasons… Like Eucon, I don’t have my mackies set up anymore…
So right now I’m attempting to AAF out of the to “corrupted” mix to a brand new 5.5 session. Hoping that most my dialog level auto will stay put and I can just do my EQ’s and sends over. (majority of this feature takes place in an RV) shouldn’t be too bad
Moderators are there to moderate. All they can tell you is that they’ve passed on any information you’ve given them. It has been stated many times that they do this anyway, so I’m not sure that it is necessary to repeat this information ad nauseum, although it would certainly make things clearer for some users. Then the threads would all be about when!
However, if you’re expecting an answer from the people who actually code Nuendo then I think you’ll have a long wait.