I have a half hour project with several weeks of editing work in it. Now all of a sudden I cannot open the project file or any of the numerous backups I have. MSP 7 opens 75 per cent of the file and then gets stuck. After about one minute I get a message saying that Video Editor has encountered a problem and need to close...
I can open very recently saved smaller project files, but none of the bigger ones, which are the most important ones. I have these files and backups on several disks, and cannot open any of them.
I have over 50 Gigas of free disk space. I am running Win XP SP 2 Home Edition, Atghlon 3000, 512MB DDR.
Until now I never had a problem like this. I don't think it is the files which are corrupted (since they all seem to have the problem, no matter what is the date when saved or on which disk).
Any advice would be greatly appreciated!
Thanks,
Maukka
Cannot Open Project Files!!!
-
MonroePoteet
New installs? Network disks offline?
Have you installed any new software that might have replaced DLL's on the system? How about any network drives that aren't reconnected?
Otherwise, sounds like an MSP re-install, or your latest OS service PAK.
mTp
Otherwise, sounds like an MSP re-install, or your latest OS service PAK.
mTp
Sometimes, you can work around this kind of problem by opening a new project with a new name and importing your old project into it. Of course, it depends on the cause.
[b][i][color=red]Devil[/color][/i][/b]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
[size=84]P4 Core 2 Duo 2.6 GHz/Elite NVidia NF650iSLIT-A/2 Gb dual channel FSB 1333 MHz/Gainward NVidia 7300/2 x 80 Gb, 1 x 300 Gb, 1 x 200 Gb/DVCAM DRV-1000P drive/ Pan NV-DX1&-DX100/MSP8/WS2/PI11/C3D etc.[/size]
-
Maukka
Not a problem that is limited to MSP, but I have found to any number of apps where 'autosave' is set to on. Try turning it off, and saving manually after a big change. I find an app trying to autosave (and locking up while doing so), especially while I am in the middle of something a real pain.
Regards,
Greg
Regards,
Greg
Greg,
I just ran into the same problem of not being able to open a project file and in my case I found what I believe to be the root cause for the project not opening.
I had edited a sound file outside of MSP7 and somehow I set more than one cue with the same name. I was able to import the project and save it as a new project but then could not open the new project. This happenned several times until I stumbled on this cue issue. Once I cleared the cue in the audio program the original MSP project was able to open up. I was specifically working on this sound file and replacing it so am not sure of how the multiple same cue names got in or how this interferred with the project opening. Either way i was one frustrated editor and now am a happy camper.
It would be interesting if soemone else can duplicate this.
Steve
I just ran into the same problem of not being able to open a project file and in my case I found what I believe to be the root cause for the project not opening.
I had edited a sound file outside of MSP7 and somehow I set more than one cue with the same name. I was able to import the project and save it as a new project but then could not open the new project. This happenned several times until I stumbled on this cue issue. Once I cleared the cue in the audio program the original MSP project was able to open up. I was specifically working on this sound file and replacing it so am not sure of how the multiple same cue names got in or how this interferred with the project opening. Either way i was one frustrated editor and now am a happy camper.
It would be interesting if soemone else can duplicate this.
Steve
-
heinz-oz
I would turn off the auto save option and empty the preview temp file. Could be that you are running out of disk space.Heinz Oz,
I've been editing for over two years with numerous large products. I am very familiar with temp files, cache conditions, corrupted save files, free disk space, etc.
Not being able to open a project file but being able to insert a project file into a blank project and getting it to work is definitely a software issue with MSP7.
Steve
I've been editing for over two years with numerous large products. I am very familiar with temp files, cache conditions, corrupted save files, free disk space, etc.
Not being able to open a project file but being able to insert a project file into a blank project and getting it to work is definitely a software issue with MSP7.
Steve
-
ejskater16
Yeah, I had that same problem. Mine was a 15 minute project, with lots of editing / filters / tracks .... and when I go to open it it stops at 75%, then brings the error saying VE had to close... the only way I got around it was by just relentlessly attempting to open it up over and over until finally it worked. This is a VERY annoying problem, and I wish it could be fixed in one of Ulead's Service Packs! With a "professional" editing app, it should be expected that the program can be trusted to handle "professional" projects!
-
Maukka
I figured out where the problem was:
Crossfaded audio files which I had edited in MSP Audio Editor 7 had somehow got corrupted, and my project file was unable to link to them, and therefore could not open the project at all.
I inserted the project to a new project, but could not simply delete these clips from the project because they were inaccessible...
I then relinked these audio clips to some other clips located in another folder, and then deleted them. Voilà, now the project file opens as it should!
The audio folder in which these crossfaded files were located is inaccessible, even for Windows Explorer. So I wonder... is it a problem with my hard disk (which otherwise is functioning fine), or did the crossfaded audio files somehow corrupt the entire folder, making it inaccessible to any software?
I note that someone else in this thread did say that he had similar prolems after having edited audio files outside MSP.
I now wonder if it is safe to use files crossfaded with Audio Editor, or is there a bug which will inevitably cause this to happen again. I would hate to go through anything like this again. Spent days in debugging.
Thanks for everybody's constributions! They were helpful.
Now I'm fnally getting back to editing my video...
Maukka
Crossfaded audio files which I had edited in MSP Audio Editor 7 had somehow got corrupted, and my project file was unable to link to them, and therefore could not open the project at all.
I inserted the project to a new project, but could not simply delete these clips from the project because they were inaccessible...
I then relinked these audio clips to some other clips located in another folder, and then deleted them. Voilà, now the project file opens as it should!
The audio folder in which these crossfaded files were located is inaccessible, even for Windows Explorer. So I wonder... is it a problem with my hard disk (which otherwise is functioning fine), or did the crossfaded audio files somehow corrupt the entire folder, making it inaccessible to any software?
I note that someone else in this thread did say that he had similar prolems after having edited audio files outside MSP.
I now wonder if it is safe to use files crossfaded with Audio Editor, or is there a bug which will inevitably cause this to happen again. I would hate to go through anything like this again. Spent days in debugging.
Thanks for everybody's constributions! They were helpful.
Now I'm fnally getting back to editing my video...
Maukka