Thank you for the reply Rob, but actually ALL of my vegas projects are not opening, so I don't know if this is a software issue or something in my system, but it cant be because it was working just a few minutes ago.

It may have something to do with a process happening in the background. I even uninstalled and reinstalled Vegas Pro 11 and still that same problem comes up.

Any other advice will help please.

UPDATE

I just installed the newest build of Vegas Pro 11 (Build 683) and now my project loaded to 62% and would not go any further while I waited.

I read on other forums that the problem might be with Quicktimes "FileIOSurrogate.exe" because I do have a lot of Quicktime (.mov) files in my project while I was editing because I was doing my effects in Adobe After Effects and exporting them out as .mov files and importing them back into Vegas. But this cant be the reason why its not loading because while I was waiting to see if Vegas would load my project past 62%, I checked my processes and "FileIOSurrogate.exe" was not running in the background.

Also like I said, I was working with a lot of .mov files in the project before this problem came up. So why now would it stall loading?

I hope I am providing enough information for this problem. Thank you

There was a recent update to Quicktime 7.7.2

Did you install that?

If so maybe this broke something with Vegas (it wouldn't be the first time)

If you did maybe try uninstalling Quicktime and installing the previous version.

You can find previous versions here: http://www.oldversion.com/QuickTime.html

Try this:
File/Import/Media
search your .veg file
After imported try File/Open your .veg file.
This "trick" helped me many times and i never used mov files!!
Instead it seems to me it depend how long is the timeline.

I thought FileIOSurrogate belonged to 64-bit Vegas, not Quicktime. And although I've seen lots of suggestions to run Vegas itself in compatibility mode, I missed the suggestion to specifically run FileIOSurrogate in compatibility mode. You're sure that's correct?

So you say that Vegas can't load your project, can't load any projects, and couldn't even load an brand new empty project. Right?

It's not normal behavior, but probably not unheard of. There are lots of possibilities like:
--Hard drive full?
--Recently updated a sound card driver?
--Recently updated quicktime?
--Using nested veg files in your project? (open those alone and make sure they're okay)
--Running Norton antivirus?

That's just a scattershot list of ideas that come to mind, assuming that we can eliminate the possibility of corrupted media files.

If you're running 64-bit Vegas you might try downloading and installing the 32-bit version.

Rob

You know, people have had so many varied problems with Vegas that there's an awful lot of talk on this forum, and maybe even some good advice scattered around. I'd recommend using the forum search function and just settle in for a couple of hours of reading. It's what most responders would end up doing to answer your question so you might as well do it too, and don't stop at the first hint of a solution.

And fill out your computer details in your user profile before someone harasses you about it.

And don't SHOUT in your subject line. It sets people on edge.

Rob

Hmmm

Having looked at your posts, am I correct in thinking most of your output is with Audio? I also notice that you started to have trouble with VP10. Was that also video too?

Having your specs may just assist us. As Rob has suggested there has been much trouble using VP11, and many ways people are attempting to cure issues, which also may NOT be of our making. However, SCS has pushed the bar higher than any of us thought would happen, so we have more opportunities to squeeze the pips on the s/w and the hardware that should be supporting it.

Let's see them specs, so we can get 'em outta the way.

Toddles

Grazie

FileIOSurrogate is a 32 bit executable that 64 bit versions of Vegas launch when Vegas is started. There is no compatibility mode issue. This process, as its name implies, appears to be related to opening, reading and writing files. If Vegas crashes, this program is not automatically closed by Windows because being an executable, it's treated as a separate process. And since this process is already running if you restart Vegas. it can't start FileIOSurrogate again. The end result is that Vegas hangs trying to load a .VEG file because it couldn't launch and connect to the File I/O server.

You should check to see if FileIOSurrogate is running BEFORE you try to start 64 bit Vegas. If it is, kill the process and then re-start Vegas.

Thanks for the tips Rob. The information I got about the FileIOSurrogate executable came from this post on the Vimeo forums:

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

I know its rather old, but the problems seems to be in the same ball park I believe.

As a matter of fact, Vegas does load older projects fine, but not my current one. It just stalls at 62% while loading the project.

I have also thought about all those possibilities that you've listed and my hard drive is getting pretty full but not in the red zone yet.

- I updated quicktime a couple weeks ago and editing was fine until now, so I don't know about it being a quicktime problem fully.

- I do have one nested project in my current project.

I dont believe I have corrupted media files because it would crash if it did. But in my case, Vegas just hangs and I have to kill it in my process list with "Ctrl+Alt+Delete."

I will try installing the 32-bit and see if that works, but if anything I will probably system restore my computer to a time before this problem happened, and in a worst case scenario and last resort I will probably just completely wipe out my system and start factory fresh and hope that solves the problem.

Hello Gary,

I understand what you are saying. But my problem is that the FileIOSurrogate.exe is not even listed in my process list as I am trying to load my specific project. So could it be that the reason why Vegas pro is not opening my project is because the connection between Vegas and the FileIOSurrogate is not there? If thats the case how do I re-establish that connection?

Grazie,

What kind of specs are you looking for? At the top of this forum, in my first post, I listed my OS and my specs for my system, but here they are again.

Win7 64bit
AMD Phenom II X6 1090T Processor
12GB RAM
NVIDIA GTX460

And this is listed in my profile as well, but please let me know if there is anything else that I should provide, in order to help solve this problem. Thank you.

Here is one method I learned from the folks here about opening up projects that don't want to be opened. I recently had a problem opening a project and I found that just one of the project files was corrupted.

MOVE all the files associated with the project to another folder or RENAME the folder they are in.

When you open the project Vegas will ask for the location of the missing files. Chose the "Specify a new location or replacement file" option. Bring in the files one at a time by answering "no" to the dialog box asking if you want to use the same location for all the rest of the files.

You go through this procedure until you find the file(s) that are making Vegas balk.

Sorry if my explanation is sort of vague! I hope you can experiment and solve the problem.

"I understand what you are saying. But my problem is that the FileIOSurrogate.exe is not even listed in my process list as I am trying to load my specific project. So could it be that the reason why Vegas pro is not opening my project is because the connection between Vegas and the FileIOSurrogate is not there? If thats the case how do I re-establish that connection?"

Tony you never confirmed if you are using 64 bit Vegas. If no, then forget FileIOSurrogate, it isn't used by the 32 bit version. If yes, have you tried restarting Windows since the problem first showed up? On occasion, Windows gets confused while keeping track of process resource allocations. Restarting windows wipes the slate clean and usually fixes problems of this nature. FileIOSurrogate.exe is installed by Sony Vegas and is located in the x86 sub-directory under your "Vegas Pro 11.0" directory.

Tony,
dropping in just to tell you that your system specs are not showing in your profile at the moment.
Select to show them in "My Account > Forum Settings". See the line "Display system information on my forum profile page", select and Submit. You can check what we see in your system profile by clicking your user name.

Gary,

Yes I am using 64 bit Vegas pro 11. A method I read on another forum is that it might be a compatibility issue with the FileIOSurrogate. So I tried changing the compatibility to "Windows XP (Service Pack 2) of the FileIOSurrogate because I believe the default is Windows XP (Service Pack 3) and still Vegas would not open.

I have tried restarting my computer as well as system restoring my computer to an earlier point in time but still no luck. However, when I did system restore my computer and tried opening my Vegas pro project, I checked my process list and sure enough the FileIOSurrogate executable was working in the background, but my project still would not load all the way. The executable also only shows up when I try to load a project and disappears after a while when I close it.

This is not a crash issue because Vegas would be crashing during this process. I can still click the red "X" at the top right and Vegas asks me if I would like to cancel the background operation that its doing and instead I kill the Vegas in the task manager.

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. But how can that be if I have multiple quicktime files in my project and it would open up fine before? Why now? Is it a connection issue with a server or something?

Please advise anyone and thank you very much for the responses, I really appreciate it.

Tony, have you tried reinstalling Vegas?

Anyway, you can run "resmon", find Vegas110 in either the overview or CPU tab. Right click on it and select "Analyze Wait Chain..."



Normally running programs will not have a persistent wait chain. This *may* help you figure out what Vegas is waiting for.

"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."

The file you imported might be corrupt.

Were you using Adobe After Effects on any of the files in the project?

Thank you everyone for the responses, I really appreciate it. To sum it all up for everybody from my original post:

- Vegas is not crashing, it just stalls at 62% while trying to load my project
- I tried reinstalling Vegas and it hasn't solved anything.
- the problem I believe is with the "FileIOSurrogate.exe" running in the background when I try and open my project, maybe a connection issue to the server or something.
- I have multiple QuickTime files in my project that I rendered out of adobe after effects and possibly the last .mov file that I imported cause it to stall. If that's the case how do I go into my project and fix it if vegas won't even load the project all the way?
- I system restored my computer to an earlier point in time to see if that would solve it and it didn't. As a last resort I plan on doing a fresh install of my OS if this doesn't get resolved.

did you try my trick?

Marton,

Thank you for the response. Yes I tried your method and when I try to open my project this way, by importing the .veg file of my project as a media file, vegas freezes and then I am force to close it. It doesn't crash in the typical sense where I send a crash report to the Sony support team, rather I have basically end it in my process list with "cyrl+alt+del"

So in a nutshell I am still stuck.

Don't you make backups of your project with incremental version numbers as you work?

Bob.

Tony, if you suspect one of your video files, why not remove it, or all, from the project folder (move to a different folder, rename it) and then open the project. Vegas will ask for a location or replacement file, tell it to ignore one at a time till you get the culprit.

Maybe that will work.

Willem.