:!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post general topics related to Nuendo 8 here.
Post Reply
Proabe
New Member
Posts: 32
Joined: Tue Sep 01, 2015 6:27 pm
Contact:

:!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post by Proabe » Thu Jan 18, 2018 8:10 am

i have big regular problem with save file project (manual or autobackup) in N 8.1 Never on N4-7 not have this problem

there is no clear chronology of the problem, but I think that this is due to the DOP, since I often use it

The OS is clean, I think that this can not be related to this, since I tried to open the project on another system
Win 10 Pro, i9 9700x, Asus x299 prime deluxe, corsair h115x, elite ballistix 16gb, sdd samsung, Nuendo 6,7,8, fireface 800

User avatar
fenderchris
Senior Member
Posts: 1399
Joined: Mon Dec 20, 2010 7:30 pm
Location: Planet Palmer
Contact:

Re: :!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post by fenderchris » Thu Jan 18, 2018 8:28 am

Proabe, some info about your system would be useful here. Select your name top right (after logging in) then Profile tab and Edit Signature.

🙂
Chris

The Archers - give it a rest already!

OS: Windows-10 Pro 64-bit v.1903.
PC: i7 Quad core 2.66GHz, 24GB ram, SSD drives.
Screens: LG 4K 3440x1440, AG-Neovo 1280x1024 (x2).
Hardware: RME FireFace UFX, MR816CSX (x2), SmartAV Tango-1 + 12-fader expansion, MOTU Midi Express 128, UAD-2 Quad, Lexicon PCM-91, Lexicon MPX-550, TC-Fireworx, Roland V-Drums TD-20X, Nektar Panorama P1.
Software: Nuendo-8.1.10, Nuendo-10.2.10, Wavelab-Elements-9.5, Halion-6, Halion Sonic 3, Kontakt-5, Cubase iCPro for iPhone and Android (killed by its parents at birth), Omnisphere, Trillian.

Proabe
New Member
Posts: 32
Joined: Tue Sep 01, 2015 6:27 pm
Contact:

Re: :!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post by Proabe » Thu Jan 18, 2018 8:34 am

found out the reason. The problem occurs after processing the region of the DOP and copying it with a time code offset (see screen)
Image

although some regions after the DOP do not lead to an error. Need a patch
Win 10 Pro, i9 9700x, Asus x299 prime deluxe, corsair h115x, elite ballistix 16gb, sdd samsung, Nuendo 6,7,8, fireface 800

Proabe
New Member
Posts: 32
Joined: Tue Sep 01, 2015 6:27 pm
Contact:

Re: :!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post by Proabe » Thu Jan 18, 2018 8:38 am

fenderchris wrote:
Thu Jan 18, 2018 8:28 am
Proabe, some info about your system would be useful here. Select your name top right (after logging in) then Profile tab and Edit Signature.

🙂
thx, no prob :)
Win 10 Pro, i9 9700x, Asus x299 prime deluxe, corsair h115x, elite ballistix 16gb, sdd samsung, Nuendo 6,7,8, fireface 800

Oliver.Lucas
Senior Member
Posts: 1402
Joined: Wed Dec 15, 2010 11:26 pm
Contact:

Re: :!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post by Oliver.Lucas » Thu Jan 18, 2018 10:02 am

Problems with corrupt sessions have been reported by various N8.x users now.
While this could well be a faulty RAM or HDD thing if it happened to you exclusively, I think it is more likely to be a showstopper bug.
Main machine: Fireface UFX+ 64GB, 2TB Hecacore macmini 10.14.x, egpu
Avid ProTools Ulitimate and S3. A gazillion plugings
https://aufnahme.myds.me

Proabe
New Member
Posts: 32
Joined: Tue Sep 01, 2015 6:27 pm
Contact:

Re: :!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post by Proabe » Thu Jan 18, 2018 10:34 am

if the project try to open on another PC, then the problem is same
I am convinced that it is related to the DOP and the error in information when changing the region's TC or addressing the plug-ins (see screenshot) The region implies the presence of a plug-in inside (since it was processed earlier, but the plug-in is not seen in the DOP)

sorry for my eng
Win 10 Pro, i9 9700x, Asus x299 prime deluxe, corsair h115x, elite ballistix 16gb, sdd samsung, Nuendo 6,7,8, fireface 800

Proabe
New Member
Posts: 32
Joined: Tue Sep 01, 2015 6:27 pm
Contact:

Re: :!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post by Proabe » Thu Jan 18, 2018 10:37 am

Also, if these "sick" regions make a bounce and insert into the previous saving of the project, the problem disappears
Win 10 Pro, i9 9700x, Asus x299 prime deluxe, corsair h115x, elite ballistix 16gb, sdd samsung, Nuendo 6,7,8, fireface 800

User avatar
ChrisPolus
Member
Posts: 576
Joined: Sat Jun 13, 2015 9:32 am
Location: Schweiz
Contact:

Re: :!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post by ChrisPolus » Thu Jan 18, 2018 12:04 pm

It is really a bit scary how many such bugs appear. I really do hope they get addressed in the late January update. Stuff like that kills people's time and money.

I also shiver every time I see the DOP window. This UI design is making me angry. Seriously? 4 Banks? With 9 presets per bank? What are we? In ancient ROM times of the first digital synths? Can we address those presets via MIDI messages too? I really hope this UI redesign project Timo was talking about will get its feet to the ground very very soon. Nuendo's interface makes me angry.
Handmade Win10 x64 Machine, Intel 6 Core CPU, ASUS Prime Board, 16GB RAM, 1080 GTX
MacBook Pro 15" Late 2016 with Touchbar, latest macOS, 16GB RAM
Latest Nuendo version, Logic Pro X, Reaper, UAD Apollo Duo + Twin MK2 via Thunderbolt

Proabe
New Member
Posts: 32
Joined: Tue Sep 01, 2015 6:27 pm
Contact:

Re: :!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post by Proabe » Thu Jan 18, 2018 12:28 pm

ChrisPolus wrote:
Thu Jan 18, 2018 12:04 pm
It is really a bit scary how many such bugs appear. I really do hope they get addressed in the late January update. Stuff like that kills people's time and money.

I also shiver every time I see the DOP window. This UI design is making me angry. Seriously? 4 Banks? With 9 presets per bank? What are we? In ancient ROM times of the first digital synths? Can we address those presets via MIDI messages too? I really hope this UI redesign project Timo was talking about will get its feet to the ground very very soon. Nuendo's interface makes me angry.
The DOP is a great tool that saves time, I know it very well, because I work on rerec film studio in PT also. You need a little patience. Over the last 7 years, this is the first big bug I met on Nuendo. I think in the patch will fix it.
These 9 banks are only presets, often used and not having hotkeys.
Win 10 Pro, i9 9700x, Asus x299 prime deluxe, corsair h115x, elite ballistix 16gb, sdd samsung, Nuendo 6,7,8, fireface 800

Timeline
Junior Member
Posts: 121
Joined: Wed Apr 10, 2013 8:22 pm
Contact:

Re: :!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post by Timeline » Tue Jan 30, 2018 6:36 am

Hi Proabe, I can definitely attest too that corrupt projects in N8.1 are do to the DOP as i've encountered a few myself. For me the connection seem to be with importing track archives that had DOP data on them from other systems in our studio either running N7 or N8. However what you describe may be the culprit and actual reason. Are you able to elaborate a little more. I'm not really following 100% what you mean about copying the region with a timecode offset? What does that mean. moving the region to a different location after processing? Thanks for your help
Proabe wrote:
Thu Jan 18, 2018 8:34 am
found out the reason. The problem occurs after processing the region of the DOP and copying it with a time code offset (see screen)
Image

although some regions after the DOP do not lead to an error. Need a patch
Windows 10 64 bit/ Windows 7 64 bit- i7-770k CPU 4.2GHZ, 32 GB

Proabe
New Member
Posts: 32
Joined: Tue Sep 01, 2015 6:27 pm
Contact:

Re: :!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post by Proabe » Fri Feb 02, 2018 1:04 pm

Hi, this problem is definitely due to the processing of the DOP on the events. Now I came out of the situation (temporarily) through the bounce (via hotkey) of each event after applying to it the DOP
I'm talking about applying the DOP to the events of the project, and then the time code offset of this event inside the project (close and open N8 again). Or the reconforming functions, when the events after the new video editing are rearranged.

PS Once again I will clarify, the problem appears ONLY after the N8 is closed completely and the project is loaded again.
If the N8 is not closed, but saved under different names, but after the N8 is closed, ALL are loaded, but the project can not be saved already
Win 10 Pro, i9 9700x, Asus x299 prime deluxe, corsair h115x, elite ballistix 16gb, sdd samsung, Nuendo 6,7,8, fireface 800

stingray
Senior Member
Posts: 1109
Joined: Thu Dec 16, 2010 12:55 am
Contact:

Re: :!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post by stingray » Fri Feb 02, 2018 2:10 pm

Proabe wrote:
Fri Feb 02, 2018 1:04 pm
I'm talking about applying the DOP to the events of the project, and then the time code offset of this event inside the project (close and open N8 again).
I've tried this here. No project corruption occurs. Can you provide a VERY precise step-by-step sequence that reproduces this problem every time. Without this we cannot test this issue.

Proabe
New Member
Posts: 32
Joined: Tue Sep 01, 2015 6:27 pm
Contact:

Re: :!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post by Proabe » Sat Feb 03, 2018 7:35 am

unfortunately, I can not recreate the problem from scratch, since it occurs after repeated use of the DOP, in a day or more. But there are project file that open, but you can not save it again, you can not backup the project folder, but you can copy all events it into a new project.
I can make video with prob and send to u mail if needed
Win 10 Pro, i9 9700x, Asus x299 prime deluxe, corsair h115x, elite ballistix 16gb, sdd samsung, Nuendo 6,7,8, fireface 800

AlexBell
Junior Member
Posts: 142
Joined: Wed Mar 16, 2011 8:17 pm
Contact:

Re: :!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post by AlexBell » Tue Feb 06, 2018 12:18 pm

Try this:

Take an audio event, edit it into 2-3 sections, mark 1 section and select right-click, plug-ins and whatever plug-in. Use Izotope if you want guaranteed crash results. :-)

THe DOP opens, you get the "continue" or "new version" window, select "new version". The DOP then opens without the plug-in you selected. So go into the plug-in menu from the DOP, select the same plug-in once again, and bam!. Crashes 9/10 times on my system.

stingray
Senior Member
Posts: 1109
Joined: Thu Dec 16, 2010 12:55 am
Contact:

Re: :!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post by stingray » Thu Feb 08, 2018 9:34 am

AlexBell wrote:
Tue Feb 06, 2018 12:18 pm
The DOP then opens without the plug-in you selected.
I don't know how you arrive at this point. It doesn't do that here at all. :?

I think you are referring to a special case issue with Izotope. Cannot test here as I don't use it. But all other plugins function OK here.
See:
viewtopic.php?f=275&t=131965

AlexBell
Junior Member
Posts: 142
Joined: Wed Mar 16, 2011 8:17 pm
Contact:

Re: :!: save file problem: the project could not be saved the project is corrupt! No new project could be created

Post by AlexBell » Thu Feb 15, 2018 11:33 am

Hi, Izotope is definately that much worse, but I do get it with standard plug ins aswell.

Post Reply

Return to “General”

Who is online

Users browsing this forum: No registered users and 1 guest