Project corruption.

[LEX]

I have read elsewhere out users having project corruption and issues upon returning to a saved project.

Could those who have experienced it please write your details here.

LEX

[Animus]

I haven't experienced project corruption in years. One issue ended up being related to when I updated to a later version of DirectX (I installed a game that required it, I know! stupid) which caused project corruption in Nuendo for some reason. The other was the confirmed issue of losing vstis when memory load got above 1.4 gigs of ram in Nuendo. That was a real beauty and pita. I beleive Steinberg fixed that one in Nuendo 3.

Though, I don't deny it still exists but it can very well be related to what other stuff you have installed on our DAW as I illustrated with my DirectX example.

[LEX]

I believe kdm has had project corrupt issues in N4.

That is what I am trying to find out. It is scary to even consider moving to C4/N4 if something like this still exists.

Since there has been no response to this issue from SB, it might be wise to find out what is going on and something other users could be aware of.

LEX

[kdm]

I have. I've had serious errors occur in the following situations:

1 - Two Quicktime video clips on the video track - I need to revisit to see if they were differing formats - it was a quick drop in and compare situation where I didn't have time to convert, check, etc - client in the room, need a quick look at a clip. I ended up having to export tracks and start over....

2 - Not frequent, but I've seen serious errors happen when working in the key editor, and the score editor. Mr. Anxiety reported serious errors in the score editor on the Nuendo 3 forum.

Serious errors in N3 would cause Nuendo to save to an incremental filename (-01, etc), but once you closed Nuendo, then reopened the new file, you could continue working without the corruption. In N4, this seems to have changed - once the project has a serious error and starts saving to an incremental file, it will always increment to a new file, everytime you hit save.

The only recovery is

1) to go back to a previous version of the file saved to a different name *before* the error occured. Even the non-incremented filename that was open when the error occurred will no longer overwrite itself.

or,
2) export a track archive, midi file, etc and start over. Sometimes saving mixer settings will transfer the error to the new project - even without 3rd party plugins.

It's buried somewhere deep in Nuendo's general code, and not a specific section.

I am running the /3G switch and have wondered if that is contributing, even though I've seen this with plenty of free ram, and have not seen it when running heavily loaded projects - no real rhyme or reason so far.

[The Guru]

Change patches in HaloinOne during playback and see what happens.:D

[hackenslash]

That avatar looks suspiciously familiar... :chin: :yfc:

[Sam]

This email I wrote to our old Australian support explains the only doosie I had


Hi [names witheld to protect identity :P ],

I have both N4.1 and N3.2.1 installed on this machine.

The problem is that yesterday I was working in Nuendo 3.2.1. I was opening and closing this session no problems all day. Then I get in this morning and try to open the project in N3.2.1 and it says - Invalid project file "So far away mix 2.0.npr"

I then try to open it in N4 and it opens fine (but I am using some critical DX plugs which obviously don't work in N4) and at the top of the project window it reads

"Nuendo 3.2.1 project – So Far Away.npr"

I never touched this project with N4 till this morning and I have never saved over the N3 session with an N4 session – as you can tell because N4 thinks it is an N3.2.1 session!

Any Ideas?

Really need to finish this mix pronto….

Cheers

Sam



they replied



Hi Sam,


Good to hear from you.

This isn't a known issue and thus there's no known solution. I'd recommend reporting this issue to the www.nuendo.com forums to see if others have experienced similar issues.

Has this problem happened with just this one project or with multiple projects?

Warm Regards,

Hehe....incidently another official support channel recommending the unofficial forum as a next step. I never had this happen again as I moved exclusively to N4 from there on in - I also never found out how this happened. It was some pretty bizarre shit!

[psvennevig]

I have. I've had serious errors occur in the following situations:

I am running the /3GB switch and have wondered if that is contributing, even though I've seen this with plenty of free ram, and have not seen it when running heavily loaded projects - no real rhyme or reason so far.

Hi, Could you bother trying without the /3G option. I have a couple of reports from users here in Norway also having problems with corrupt projects. Both run with the /3GB option.

Also, if a project crashes please open the perfmon.msc (if you're on a PC), then lookup the "Virtual bytes" counter for the N4 process.
If this is close to 2GB for Nuendo, you are in trouble.

If you are using Waves V6 plugins the memory limit is met at least twice as fast, since a bug (Waves or Steinberg) make sure that the footprint of the Waves plugins is twice the RAM load compared to V5. This even if you only have them sitting there.

Pål

[Daryl]

Change patches in HaloinOne during playback and see what happens.:D

Serves you right for using that POS. This is not a bug, it's a feature, designed to teach you good taste.

D

[Animus]

Hi, Could you bother trying without the /3G option. I have a couple of reports from users here in Norway also having problems with corrupt projects. Both run with the /3GB option.

Also, if a project crashes please open the perfmon.msc (if you're on a PC), then lookup the "Virtual bytes" counter for the N4 process.
If this is close to 2GB for Nuendo, you are in trouble.

If you are using Waves V6 plugins the memory limit is met at least twice as fast, since a bug (Waves or Steinberg) make sure that the footprint of the Waves plugins is twice the RAM load compared to V5. This even if you only have them sitting there.

Pål


Using the 3g switch here with no corrupt project problems.