+1 for what Willem's describing. What I'd add to that is that (after squirelling away a backup copy of all veg files) is that you start with the nested veg project file. Open it as a standalone project and make sure it opens. then save it.

I've had a similar sounding problem and it traced back to the nested veg file. It was a project that had been bumped through Vegas 5, 6, and 7, each time with newly saved veg files, but the nested project wasn't also getting updated, and media had also been archived and restored. The fix was to make sure the nested project was right and versioned up to match the parent project.

Once that's settled and if the parent file still won't load then try peeling off and hiding half the media (but keep everything needed for the nested Veg together and available, I think). You can keep dividing the media in half until you find the file or files.

rob

here is what i do

open last version of project that is known to open

turn off audio waveforms

launch problem project from now open project by choosing open from file menu

for me, this almost always works

Hey Willem,

Thank you so much for the response. Unfortunately I tried your method that your recommended for me and still the project stalls at 62%, and will not go any further.

This truly is a puzzler. I moved a lot of my footage from my external HDD to my main computers HDD and Vegas didn't even ask me if I would like to find the "missing" files and specify a new location because I my project file and footage is all on my external HDD. I even uninstalled quicktime from my computer because my project has a lot .mov files and I just wanted to see how Vegas reacted if I just completely uninstalled quicktime and the .mov files that are already in the project.

I even tried disabling the view of the audio wave forms and such to see if Vegas would open the project and still nothing.

I am starting to think there is a major problem with Vegas. I reinstalled it countless times as well as trying to open the project in the 32 bit version of Vegas pro and still no luck. I am thinking about doing a complete clean install of Vegas pro and see if that will help, because I am at a lost and panicking because this project was huge and have been working on it for over 4 months straight.

The thing is, again, Vegas is not crashing. It just loads all the way to 62% and just flat out stops.

Any other advice from anyone will be greatly appreciated. Please.

UPDATE:

Just did a clean uninstall and reinstall for Vegas pro 11 and tried opening my project again, and unfortunately it still did not load all the way. I am beginning to worry. What more is there to do? Clearly there has to be another case similar to mine that people found a solution for.

I appreciate everyone for helping me, and any more advice will be greatly appreciated.

I couldn't tell from your response to Willem if you had completely followed his advised steps, and in loading which file did the stall occur. If you took the steps of putting half of the source files in a new folder and the load stopped before it began asking you to give new paths for the files, then your problem is with a file that you DIDN'T move. If this is what happened, move the remainder of the source files to a new directory also, and this time when opening the project, don't select the option to "use this path for other files also" (wording not precise but I'm not at my machine) Manually find and allow Vegas to load each file one at a time until you see Vegas stall. That last file selected is the problem. It sounds like you've got a big project, so expect to spend an excruciating amount of time doing this. I think Willem and others gave you some good advice on a solution and I wouldn't give up yet.

Now, after you've moved ALL of your source files to a new directory, if Vegas is stalling out before any dialog box opens saying it can't find your source files, then I'm afraid your .veg may be corrupt. (from what you've posted previously, I doubt the .veg file is the problem but it's been known to happen)

Also, did you try reverting to an older Quicktime version if you were using the most recent one? You also say none of your Vegas projects will open. Are all of your projects related to the current project (i.e. previously saved edits of the same project)? If you create a new empty project in Vegas and save it with a name, will it open? If so, add one file, save. Will it still open? If not, and it was a QT file you added, try again with a non-Quicktime file. Will the project them open? I think this will help determine if it's an install issue or a new internal conflict in your system. If you can do both of these things succesfully with a non-Quictime file, but not WITH a QT file, then I think you have either a corrupt file or an incompatible QT version.

I moved a lot of my footage from my external HDD to my main computers HDD and Vegas didn't even ask me if I would like to find the "missing" files and specify a new location because I my project file and footage is all on my external HDD.

If Vegas didn't ask where the footage went then either it's not getting that far while loading the project, or you didn't actually move the footage. How about this. Move all of the footage except for the first file in the timeline. That way you shouldn't need to wait to find out something's wrong. For that matter move all the media (or just move the Veg file). This way you can try opening the project with absolutely no media available. If it never asks for media (and never loads any) then I'd say your veg file's corrupted.

It seems very unlikely that Vegas itself is screwed. If Vegas can open other projects but not *this* project then it's either the project file or the media.

Rob

O.P. said


So Vegas is loading other projects, just not this one.

Rob

I actually tried importing a .mov file into Vegas by itself and there was a problem with the quicktime plug in, it wasn't installed properly. So what I did was revert to an older version of quicktime (7.6.0) and then tried importing a quicktime file again and it worked. So I thought my problem was solved, but when I tried to open the project with all the quicktime files in it, the project stalled at 62% opening again. Perhaps I have to go to an even earlier version of quicktime? I have been reading this forum and the problem seems similar to mine:

http://vimeo.com/forums/topic:23517

I actually left my computer on over night to render out a part of the project in Adobe After Effects because it was going to take a couple hours and it was late. Then when I came back the following night and imported the newly created .mov file from After Effects into Vegas Pro, it was still working okay. Its when I closed Vegas and tried to open it again did this problem start up. Do you think Quicktime updated itself over night when I wasnt around and thats what caused this hiccup? The new version is 7.7.2 I believe. But if so, when I revert to an older quicktime version, my project wouldnt open.

I even did that method of moving ALL my source footage somewhere else and opening up the project but it still went and stalled at 62% and nothing else, no vegas trying to find my missing files, nothing.

If the quicktime files are the culprits for stopping my project from fully loading, is there a way to get them out? Like I said, I moved ALL my source footage including all my quicktime files to another folder and Vegas still wouldnt load. And the quicktime files are fine because when I import them into a blank project they import fine and I can put them on the timeline no problem.

Finally, when I try to open my project and it stalls at 62%, I just leave Vegas alone and see if something will happen. About 20-25minutes later, Vegas crashes and I send a crash report to Sony. So Vegas doesnt ask me to find missing files and such, it just stalls then crashes.

I am thinking about wiping my computer clean and starting factory fresh and seeing if that will help as a last resort. But judging by this, it doesn't look like that will even help, but I dont know.

Again thanks for the responses and I hope this problem can be resolved. I do not want to have to edit the whole project all over again.

Sorry for all your problems. I have never attempted to run Vegas without QT installed, so I'm not sure what it will tell you if you would completely uninstall QT (search registry and get rid of all references) and try to open your project. If it makes it to a point where it says "unrecognized file type" or something of that nature, it's possible it still may be a Quicktime issue. And I hesitate to even bring this up, but the .veg file does contain some readable information about each file and plugin used in a project, mixed with random characters. In the past I have made copies of the .veg , opened in Wordpad and copied to a word processor and used "find and replace" to get rid of the random characters. It's never really helped me in any way to solve a problem, but if you see a lot of correctly named files and then garbage, it could help confirm that the .veg file is corrupt. I haven't looked through this thread in detail so I may be missing or duplicating, but was autobackup enabled on Vegas? It's a longshot, but if the time between backups was long enough, you may find one that will open even if the current .veg is corrupt..

wow that sucks. i have a couple bits to add, but wow that sucks :(

QUICKTIME
1) don't use version of QuickTime before 7.6.0
2) Any version of 7.6x should be a fairly safe bet. - musicvid
3) Install version 7.6.2 of QT for compatibility with Vegas Pro 8. - Nick Hope
4) Some of our more experienced users still have QT 7.6.2 or 7.6.8 - musicvid
5) Avoid latest version of QuickTime. Wait for the reports.

PLUGINS
This is kinda desperate, but if you uninstall all the plugins (waves, newblue, freebies, etc) on your computer, you would be able to avoid glitches caused by plugins.

I had a similar problem with AAV Colorlab (free Vegas plugin), as it doesn't like Premiere. If PP was running, Vegas projects would crash whenever Colorlab was activated. More relevantly, the Vegas project wouldn't load if Premiere was open as Colorlab prevented it. Once I removed the plugin the problem went away.

I've also had problems with audio plugins refusing to load, bringing everything to a standstill; but this happens when Vegas is starting-up, before the project itself begins loading.

I don't know if it's been suggested yet, but if you have a place where you could post a link to your .veg file, some of us could try opening and see if we get to a point where it begins looking for source files. It may help eliminate some possibilities...

If we were lucky enough to get the project to open with missing media, it would be easy to delete the last file you added and clean the media pool and get it back to you.

Since you're running from a removable drive, the simplest way to eliminate media would be to copy the veg file to a fixed drive and then just completely remove the removable one.

It seems to me though that if you've removed all of the media and the bad project still stalls and hangs Vegas at 62%...then there's something else going on. Maybe a corrupt veg file, maybe a bad or corrupt plugin used about 62% of the way down the timeline...It'd be useful maybe to know just what Vegas is doing while it's loading. Ah for a terminal window to view output from Vegas....

<edit>Just did a little sanity check. I copied a project file from a removable disk to my desktop and then disconnected the disk. Then opened Vegas with the project file. Vegas 11-64 opens the project to 100% before it asks me where my media went. This is a very simple project full of quicktime files. I was just using it to scan through clips and save still frames so there's nothing complex about it. But the point is that Vegas doesn't seem to even ask for the missing footage until the project's loading progress reaches 100%.</edit>

I don't use nested projects, but rmack350's post made me wonder exactly what is going on at 62% load. If you move a nested project to a different location, does Vegas ask for the new path like it does with media, or just fail to load? This may be worth trying too.

And I agree that sharing the Veg file might be helpful. Actually, if there's a nested veg then sharing all the veg files might help. If nothing else it might eliminate an idea or two.

Rob

@TonyBoyV

Are there any files with your project name with .veg.bak?

If so, rename them one at a time by deleting the .bak part so it is then project name.veg and try loading them one at a time. You will need to rename the current project name.veg to something like x-project name.veg to preserve it and allow windows to rename the .bak file.

If not then you do not have auto-save or whatever it is called turned on.

A bit late for this but I have installed Carbonite on all of my edit suites and it keeps incremental backups in the background (not immediately apparent if you just look at their website).

That feature saves me all the time.

It really looks like the .veg is corrupt.

If you take the media offline and it still doesn't load that eliminates the possibility of corrupt media. Except the only other thing to check for: see if you have any pre-rendered video and blow that away too. But it really sounds like the .veg is toast. Sorry.

Could it be quicktime is running out of memory?. I have had this problem a while back where i had a bunch of MOVs from DSLRs.. The project was saved then after a re-open, it would stall while loading. This was a while ago i cannot remember if it got stuck during Vegas startup, or during loading the media. Could be the same problem. It sounds similar at least.
The solution was to use an alternative to QT. here:
http://www.filehippo.com/download_quicktime_alternative/

Its a stripped down, bare-bones version of QT (its a decoder only, it cannot encode).
It worked for me back then.
So maybe try uninstalling your QT, then give this a try.

EDIT: "Before this problem, the last thing I did was import a quicktime file into Vegas. Then I closed Vegas, worked a little in Adobe After Effects, then tried to open Vegas again and then all of a sudden it wouldn't load all the way"...
This also backs up the memory theory. One file too many, same problem i had.

Hope this helps.
Paul.

Long thread to go through, but has the suggestion been made yet to see if the nested veg will open as a project? If the problem is in the nested veg that could be why he's only getting to 62%.

Long thread to go through, but has the suggestion been made yet to see if the nested veg will open as a project? If the problem is in the nested veg that could be why he's only getting to 62%.

Yup. +1

Hello Everyone,

I am please to report that I have finally figured it out. What I did was search for my autosave projects and luckily I found one that autosaved right before this problem came about a couple of days ago.

I am so relieved!

I still dont know what caused this problem, and I took the advice of installing quicktime lite just in case quicktime wasnt getting enough memory in the project or something. All of my quicktime files in my project are pretty huge, all up around the 1 GB range, so I guess Vegas has a hard time trying to load this huge project as a whole, but if I break it up it should be fine. It sucks because I can't download Itunes as that will also install the latest version of quicktime and that might cause my project to lock up again. Maybe its safe to go to quicktime 7.6.0?

Anyways, I really appreciate all of your guys' help in trying to solve this problem, and I hope that anybody that runs into the same or similar problem as me can look at this forum and see all the great advice I got and to help them with their endeavors in editing. You guys are the greatest.


Thank you all and God Bless

That's good news. Glad to hear it!

Rob