imaginACTION_films wrote on 3/1/2012, 9:15 PM
Can you please fill out your system specs so we can help?
Steve Mann wrote on 3/1/2012, 11:58 PM
How did you "reload" Vegas?

Also, post your system specs in your profile.
ushere wrote on 3/2/2012, 4:43 AM
sounds like a missing codec?
johnmeyer wrote on 3/2/2012, 10:49 AM
Ah, the system spec police again. Your system specs have absolutely zero to do with your question. Absolutely nothing at all.

Instead of asking that silly and useless question, the much more important question is what file the VEG is trying to open when the error message occurs. Can you tell which video, audio, or still photo file is trying to be opened? If not, can you remember, more or less, which files were in the project? If so, you can drag them, in groups. to the timeline in a new project until you get the message.

Another possibility is that the VEG itself was created in a later version of Vegas than 7.0.
Jay Gladwell wrote on 3/2/2012, 10:53 AM

"Instead of asking that silly and useless question..."


Grazie wrote on 3/2/2012, 11:28 AM
Wow! 5 years and one post, and this is it!

This HAS to be SCS's Most Favoured Customer? That's MFC?

Gotta be Friday . . ?


Grazie wrote on 3/2/2012, 11:33 AM
Does your system fall into this pile? I'm guessing its even better. But have you done anything MORE to your system than this?

The following lists the minimum system requirements for using Sony Media Software Vegas software:
Microsoft® Windows® 2000 SP4 or XP (Windows XP SP2 required for HDV and XDCAM)
800 MHz processor (2.8 GHz recommended for HDV)
200 MB hard-disk space for program installation
600 MB hard-disk space for optional Sony Sound Series Loops & Samples reference library installation
256 MB RAM (512 MB RAM recommended for HDV)
OHCI-compatible i.LINK® connector*/IEEE-1394DV card (for DV and HDV capture and print-to-tape)
Windows-compatible sound card
DVD-ROM drive (for installation from a DVD only)
Supported CD-recordable drive (for CD burning only)
Microsoft DirectX® 9.0c or later (included on application disc)
Microsoft .NET Framework 2.0 (included on application disc)
Internet Explorer 5.1 or later (included on application disc)

As JM says, we'd need to know the parameters of the Project - really?



Grazie wrote on 3/2/2012, 11:34 AM
Can you MAKE VV7 projects still?

Have you reinstalled VV7?

Much to ask and consider here . . . . .


johnmeyer wrote on 3/2/2012, 1:02 PM
Wow! 5 years and one post, and this is it!Man, it sure it getting rough to be a first-time poster in these forums. If you don't do everything just right, you get sarcasm, useless questions, and unhelpful comments.

I, for one, do not like the "turn" this forum seems to be taking.
Grazie wrote on 3/2/2012, 1:09 PM
No, it is not sarcasm. I'm truly amazed that this is his/her first calling on our help. And I mean it, with all the troubles all of us have had with issues, coming here with this one is remarkable.


Grazie wrote on 3/2/2012, 1:22 PM
As I was saying. And it is Tom, isn't it, can you make any VV7 projects still?


MUTTLEY wrote on 3/2/2012, 2:06 PM

Tom, as Grazie asked I'm curious if this is with a project you were working on before your system got fried or does it happen even with a new veg? If it's a project from before your system got fried I'd guess there's a chance that it may have gotten corrupted as a result of the system getting "fried". I've had similar situations where I had to try and use data recovery software to get things off of a drive after some catastrophic failure with mixed results. Even on images some would be half there but half a garbled mess.

I wont debate the validity of system specs in this situation but certainly see no harm in asking. With all due respect John, as you do bring so much to the forum, I'm a little taken aback by your lashing out at those that appear to have sincerely shown an interest in Tom's situation. I know that when I have a problem and post on a forum I'm encouraged when people ask questions and are at least attempting to help.

I'm confounded further by your saying:

"Man, it sure it getting rough to be a first-time poster in these forums. If you don't do everything just right, you get sarcasm, useless questions, and unhelpful comments."

It seems to me your jumping on others who were trying to help would make a worse first impression to a first time poster than someone simply asking for system specs. Not to mention you were the first to be sarcastic if not condescending. I don't know how you can say "I, for one, do not like the "turn" this forum seems to be taking." with a straight face when you were the instigator.

Perhaps you're having a bad day or this is just a pet-peeve of yours but either way I'd encourage you to think about it.

- Ray
Underground Planet
johnmeyer wrote on 3/2/2012, 4:05 PM
I'm a little taken aback by your lashing out at those that appear to have sincerely shown an interest in Tom's situation.It is true that these people did take the time to post, and perhaps that by itself indicates some level of "sincerity." However, the reason I doubt their commitment is that these same people have, over and over and over again, in dozens of posts, asked the person for their system specs when their system had nothing whatsoever to do with the problem they were describing. What's more -- and this is once again the case here -- they made no attempt to offer any useful advice that might actually help the person complete his or her project.

I guess I could keep silent, and perhaps I should. However, if I do that, then these same people will continue to be unhelpful and will discourage those who are new to the forum, or are frequent "lurkers, from ever posting. And, if that happens, it doesn't help anyone because it is these new people who usually have come across something new and different to offer.

As for sarcasm, that is the wrong word entirely to describe my response because there was no irony or hidden meaning in my remarks. Nor was what I posted in any way condescending because I was not implying that I know more than anyone else.

Of course, my comments were quite definitely very blunt and quite pointed, and they were intended to directly challenge everyone to try to be helpful rather than to put new posters through this ritualistic hazing that I have decried on numerous occasions, but which they still persist in doing.

I tried once before in this thread:

Vegas 10 and 11 Crashing

to get them to stop, but I guess this thread shows that my efforts have been wasted.

farss wrote on 3/2/2012, 4:47 PM
utterly agree with you on this. If it was just a few heredoing this then I would feel less annoyed but when years ago I reported a bug and clearly indicated it had been reproduced on several systems, with several versions of Vegas running under two versions of Windows and I still get told the problem cannot be escalated without me supplying my system's specs that was the straw that broke the camels back for me.

I'd also add that like you I must have read over 100,000 posts over the years. I cannot recall one instance of where the problem was resolved based on information revealed in a user's system specs. It may as of V10 and later reveal something related to the type of GPU I guess but this user is running Vegas 7 and the problem he's having seems hard to correlate to anything to do with his system. If it does the vital information will reside in much finer system detail not revealed in the broad brush of his system specs.

ushere wrote on 3/2/2012, 5:34 PM
still think it's a missing codec.....

TheHappyFriar wrote on 3/2/2012, 10:48 PM
What error does Vegas give when you open a veg in an older version that it was made in?
FilmingPhotoGuy wrote on 3/3/2012, 4:00 AM
Also, if your VEG had 3rd party plugins that are not installed in this installation then you will get an error. With V10 you can still click OK and continue without the plugin but in V8 or 9 it wouldn't even open the Veg.

What is the exact error message? Does it open partially then give an error?
WillemT wrote on 3/3/2012, 4:01 AM
Opening a VP11 project in VP10 gives:

vkmast wrote on 3/3/2012, 5:06 AM
Tried copy/paste a project with some plug-ins from 11 to 10. Opened partially with an error like this
farss wrote on 3/3/2012, 5:44 AM
I think I may have just recalled something from my memory banks that might be applicable. Obviously V7 is from a long time ago so take this with a grain of salt.

Firstly I have had exactly the same problem but a very long time ago. Project files wouldn't open, Vegas just reported they were corrupted and support couldn't help either. Now thing was, I had backed them up onto several hard disks and optical media and none of a whole group of projects would open no matter where they'd been archived. At the time I was never able to resolve this problem and just rebuilt the project, thankfully I still had copies of the rendered output and they were fine.

What just occured to me was somewhere in the dim past there was one build of Vegas that created project files that were not forward compatible. The bug was fixed in the next build. However if somehow all your project files were saved in the build with the bug and you've downloaded a later build maybe you've been bitten by this bug. Maybe it explains the problem I had as well.

As I said this is all from my dodgy mental archive.

TheHappyFriar wrote on 3/3/2012, 5:55 AM
Tried copy/paste a project with some plug-ins from 11 to 10. Opened partially with an error like this

Well, that's good it just doesn't paste the stuff that isn't in V10. That can kind of fix a problem like this.