I had a problem like that, a 6 channel CC that i used on two clips, but it said the plug was missing and I was able to get past it by (I think) ignoring it... so unless you used the plug on all your clips for that project I don't understand why it wouldn't let you just get past it... ?
I think I'm screwed
- Thread starter capitalP
- Start date
aw grasshopper
Well-known member
US -
You would think you could ignore it but it does not seem to work that way. I do know, on my other computer, that I had missing audio plug ins for one of my projects and it opened just fine. However, a third party video plug in caused Vegas NOT to open until I put that plug in back on the system. And, no, I did not use that plug in on all my clips. Matter of fact, I only used it for the opening title. Just thought I would pass this along as a possible answer.
Have a great day.
Grasshopper
You would think you could ignore it but it does not seem to work that way. I do know, on my other computer, that I had missing audio plug ins for one of my projects and it opened just fine. However, a third party video plug in caused Vegas NOT to open until I put that plug in back on the system. And, no, I did not use that plug in on all my clips. Matter of fact, I only used it for the opening title. Just thought I would pass this along as a possible answer.
Have a great day.
Grasshopper
That's a good point -- if you don't have all the same plugins installed on each computer where you have Vegas, it can be problematic if you use
that plugin's FX on a clip in your project. Not always, maybe not even most of the time, but sometimes.
that plugin's FX on a clip in your project. Not always, maybe not even most of the time, but sometimes.
capitalP
Veteran
It's funny you mentioned this, but this is exactly what I've been working on. All my AVI files are in an external hardrive, so I made a copy of the corrupt file and put it on my external hardrive, then I gave a friend of mine my hardrive and he installed Vegas on his computer. To make a long story short he's getting the same error message. So now I know it's not my computer but the file itself.
But it gets weirder. When I try to open the file on my computer it gets to 60% then the error message appears and it closes, but my friend said he got it up to 100% then the same error message appears and it closes. Weird, but it still won't open.
Scharky, thanks for the suggestion, but I just realize I don't have any quicktime file on the project tmeline.
I didn't even get that far to adding FX yet, so I know it's not any type of plugins. The sad part is, some scenes I put together were so well edited, I just hope I can put the same touch the second tme around...
so starting NOW, I'm going to start editing from scratch and save the file with a differrent name each time I make changes to the edits. What really gets me the most is, I have no record of which takes I used to put certain scenes together, so I'm going to have to watch each take which is sometimes 9 or more for each scene and narrow it down to 3 then make one selection. And did I mention this is a Feature? Pain...
Thanks everyone for their thoughts and suggestions. Maybe this will work out for the best, the second time arround edit will be even smoother and better then the last cut. :dankk2:
aw grasshopper
Well-known member
CapitalP -
I am sure most, if not all, of us have been in your shoes and share your pain. It is a lesson we never forget however. Who knows, maybe the next time through you actually like what you come up with better than the first time through. Could be God's way of telling you to do better
.
Good luck.
Grasshopper
I am sure most, if not all, of us have been in your shoes and share your pain. It is a lesson we never forget however. Who knows, maybe the next time through you actually like what you come up with better than the first time through. Could be God's way of telling you to do better
.Good luck.
Grasshopper
capitalP
Veteran
This is a thought, but I've emailed a technical question last week and still no reply, so I'm thinking by the time they get to helping if they even help I'll be half way through the re-edit.
CapitalP -
Could be God's way of telling you to do better
Good luck.
Grasshopper
Now that is hilarious, you could be right. God could be telling me I SUCK! :laugh:
capitalP
Veteran
Update:
You guys won't believe this, but after much headaches and contacting sony tech support and using the advice here on the boards, my currupt project file was not able to open. So after days of crying, I started a whole new edit of the film.
And guest what! Same problem. I'm getting the same identical error code with the new project. Don't know what it is. I even had friends try and open the project on their own computer and same error code. I did something different from the last project, I saved a different version(dated) of the project each time. The one that's not opening is the last saved version. which is 9-13-07.
I installed Vegas 7 and hopes of the project opening, same error. Now I don't know what to do. Now I'm afraid if I start a whole new edit again, same results will occur, and I can pick-it up from an earlier saved version, but I know it might happen again. Because the 9-11-07 saved file also give shuts down after opening, but it opens all the way, the 9-13-07 won't open at all. And the 9-8-07 version opens fine. So I thought it was a memory issue, so I went and got an extra GB of memory and that did not help.
My only other option would be to completely try and edit the film on another NLE... but I would hate to have to learn another NLE, I really like Vegas, but at this point I'm not left with any other options..
This has to be the weirdest thing I've ever encountered on a computer. I never had no kind of problems before with Vegas, I've edited a 45 minute project and no problems. This is weird. I had hopes of the film being done in Feb, but now I don't know, maybe someone put a Hex on me.. who knows.
And here I thought, Pre-production of the film was tough, and actual production was even tougher, I know post production wasn't gonna be smooth sailing, but I had no idea it would drive me crazy.
You guys won't believe this, but after much headaches and contacting sony tech support and using the advice here on the boards, my currupt project file was not able to open. So after days of crying, I started a whole new edit of the film.
And guest what! Same problem. I'm getting the same identical error code with the new project. Don't know what it is. I even had friends try and open the project on their own computer and same error code. I did something different from the last project, I saved a different version(dated) of the project each time. The one that's not opening is the last saved version. which is 9-13-07.
I installed Vegas 7 and hopes of the project opening, same error. Now I don't know what to do. Now I'm afraid if I start a whole new edit again, same results will occur, and I can pick-it up from an earlier saved version, but I know it might happen again. Because the 9-11-07 saved file also give shuts down after opening, but it opens all the way, the 9-13-07 won't open at all. And the 9-8-07 version opens fine. So I thought it was a memory issue, so I went and got an extra GB of memory and that did not help.
My only other option would be to completely try and edit the film on another NLE... but I would hate to have to learn another NLE, I really like Vegas, but at this point I'm not left with any other options..
This has to be the weirdest thing I've ever encountered on a computer. I never had no kind of problems before with Vegas, I've edited a 45 minute project and no problems. This is weird. I had hopes of the film being done in Feb, but now I don't know, maybe someone put a Hex on me.. who knows.
And here I thought, Pre-production of the film was tough, and actual production was even tougher, I know post production wasn't gonna be smooth sailing, but I had no idea it would drive me crazy.
You might have a virus. Have you done a sweep?
David meant if you scanned for Viruses. Did you?
However I do agree with you. From the sounds of it, at this point I'd move on to creating a brand new installation of Windows, from scratch. This is something you must do at this point unless your problem is a virus. Either way 99.9% certain, the problem is not Vegas, and either way it is a good idea to start from scratch when you have horrible problems like this.
I hope the install solves your problem. If so then there is no need to read on after this sentence! Woohooo!
If that doesn't do it, then you have an unstable system which corrupts your project when you push it to it's limits with a heavy timeline after long intensive sessions. When you test for stability you run mathematical problems non-stop for up to 24hs straight. An unstable system will give an incorrect result to the calculation but not necessarily immediately. A truly stable system is not something that is actually defined, it depends on what you call stable... 24hs? 12hs with no errors is excellent, but 3hs is usually enough for less intensive uses such as web-browsing word processors and even crazy excel usage or games, most of the time. Unfortunately editing HD video is about as hard-core as you are going to get when talking about taxing your computer. The processor the memory and the NorthBridge are the ones to worry about. While Vegas doesn't need a lot of memory it doesn't mean that it isn't using the X amount of memory it requires at incredible speeds. The NorthBridge is the chip that carries the info from component to component, and it's main task is to do this between the CPU and RAM. However an old power supply unit can also cause these to fail. Old units may not be able to provide stable power for long periods and as soon as these components get bad voltage... poof... there goes stability.
The problem is that finding the culprit is a time intensive task of trial and error. I am guessing that by now, you might be tired of pouring time and patience into the project. If so I feel your pain man... so if a clean install doesn't do it then there are two ways to proceed:
_ I suggest you find a place where you can buy and return an HP and get one of their new desktops with 2GB of ram and a Quad... one of theirs should be able to pass 24hs of testing... then hope to finish before you have to keep the computer for good.
_ Or build one for added performance and serious $$$ savings... it is easy. I'll be glad to tell you what to get and even walk you though the whole thing if you get the parts on a weekend. You can get the parts in about a week, physically build it in about as little as 1hs, and then all you need to do is install the OS and all your software again and off you go.
Good luck!
However I do agree with you. From the sounds of it, at this point I'd move on to creating a brand new installation of Windows, from scratch. This is something you must do at this point unless your problem is a virus. Either way 99.9% certain, the problem is not Vegas, and either way it is a good idea to start from scratch when you have horrible problems like this.
I hope the install solves your problem. If so then there is no need to read on after this sentence! Woohooo!
If that doesn't do it, then you have an unstable system which corrupts your project when you push it to it's limits with a heavy timeline after long intensive sessions. When you test for stability you run mathematical problems non-stop for up to 24hs straight. An unstable system will give an incorrect result to the calculation but not necessarily immediately. A truly stable system is not something that is actually defined, it depends on what you call stable... 24hs? 12hs with no errors is excellent, but 3hs is usually enough for less intensive uses such as web-browsing word processors and even crazy excel usage or games, most of the time. Unfortunately editing HD video is about as hard-core as you are going to get when talking about taxing your computer. The processor the memory and the NorthBridge are the ones to worry about. While Vegas doesn't need a lot of memory it doesn't mean that it isn't using the X amount of memory it requires at incredible speeds. The NorthBridge is the chip that carries the info from component to component, and it's main task is to do this between the CPU and RAM. However an old power supply unit can also cause these to fail. Old units may not be able to provide stable power for long periods and as soon as these components get bad voltage... poof... there goes stability.
The problem is that finding the culprit is a time intensive task of trial and error. I am guessing that by now, you might be tired of pouring time and patience into the project. If so I feel your pain man... so if a clean install doesn't do it then there are two ways to proceed:
_ I suggest you find a place where you can buy and return an HP and get one of their new desktops with 2GB of ram and a Quad... one of theirs should be able to pass 24hs of testing... then hope to finish before you have to keep the computer for good.
_ Or build one for added performance and serious $$$ savings... it is easy. I'll be glad to tell you what to get and even walk you though the whole thing if you get the parts on a weekend. You can get the parts in about a week, physically build it in about as little as 1hs, and then all you need to do is install the OS and all your software again and off you go.
Good luck!
Last edited:
capitalP
Veteran
Yes! I did do a virus scan with Norton and the system was clean.
I do thing you're right USLatin about the system, for some reason I don't think my computer can handle that amount of work load. I do have an heavy timeline and I do push it to the limit. With that being said, I'm afraid if I reinstall windows and I work on a new project and I put in tons of hours on a the project, the same thing will happen.
At this point I think it might be best to take your advice and built a system from scratch.
I do thing you're right USLatin about the system, for some reason I don't think my computer can handle that amount of work load. I do have an heavy timeline and I do push it to the limit. With that being said, I'm afraid if I reinstall windows and I work on a new project and I put in tons of hours on a the project, the same thing will happen.
At this point I think it might be best to take your advice and built a system from scratch.
capitalP
Veteran
And... here's something I did as a percausion. The last edit of the project I did(which is 35minutes), I rendered the whole project as an AVI uncompress file just as a percausion.
So I brought the Rendered project into a new Vegas Timeline, so now I have it as one whole video file, I'm gonna use that and start editing from that point by importing new video clips.
I don't wanna have to work this way, but it's a thought. Then who's to say that new project won't give an error once I start adding new clips etc...
So I brought the Rendered project into a new Vegas Timeline, so now I have it as one whole video file, I'm gonna use that and start editing from that point by importing new video clips.
I don't wanna have to work this way, but it's a thought. Then who's to say that new project won't give an error once I start adding new clips etc...
you got it man, I'll be glad to walk you through it... I might be finally switching out Motherboards and finally swapping PSU's with the one that I've had sitting next to the case waiting to be put in... so we might end up building together... and I'll be glad to tell you how to OC it a bit if you are up for it
I am basically expecting 3.6GHz with the new MoBo, it is a great time to build, now the MoBo market is changing rapidly these coming months so we'll see what's already out when you are ready to order... hopefully we'll end up with same MoBo... if the MoBo, CPU and RAM are the same then the OCing will be so similar that you'll basically be able to just punch in some numbers I'll e-mail you and you'll be 95% done...
I am basically expecting 3.6GHz with the new MoBo, it is a great time to build, now the MoBo market is changing rapidly these coming months so we'll see what's already out when you are ready to order... hopefully we'll end up with same MoBo... if the MoBo, CPU and RAM are the same then the OCing will be so similar that you'll basically be able to just punch in some numbers I'll e-mail you and you'll be 95% done...
Cool Lights
DVXuser Sponsor
I'm sure that just about everyone has a story like this and what you're doing now is about the only really logical way of going forward: rendering out the last workable project file and going from there. I've had things like this happen to me before in other editors and I always scraped and clawed my way through it by intermediate renders and fresh project files at each step. My guess is that most likely your project has obtained such a size that you're hitting some obscure bug in Vegas that's interacting with some issue in your computer.
24fps4ever
Well-known member
are you using raylight, if so I can bet thats the problem, see sometimes I forget to start raylight before I open my projects with mxf files inside and it crashes vegas, so try installing raylight then open the vegas project, see if that helps
capitalP
Veteran
No I’m not using Raylight, I don’t even know what it is or what it does but if it’s another way that might help me save this file then I’m for it. Do u have a link so I can buy/upload
Thanks.
The Rendered project for some reason seems jittery when played back on the new timeline. My project properties are exact, don’t know what it is… But besides rebuilding a new computer and saving time that’s my next best bet, but if the video don’t look identical to the individual clips then I don’t want to continue this way. I’m going to render a DVD play it on my T.V and see how it looks.
Really appreciate it.