Comments

farss wrote on 9/25/2007, 1:58 PM
Get yourself a copy of PFE32, it's a free programmers text editor.
Wordpad or any typical text editor is not the tool for looking at such files.
CorTed wrote on 9/25/2007, 3:50 PM
Thanks Bob for the suggestion.
Seems as though PFE32 is much like wordpad but can handle larger text files.
It also seems the .veg files are more than text files and PFE32 also can't read them properly.

Ted
farss wrote on 9/25/2007, 4:02 PM
PFE32 can read text files with lines of huge length.
It'd probably get muddled if there's any binary in the file i.e. it's not a pure ASCII file.
I've managed to write VBA code that spat out a .veg files but they were cuts only files.

Is this by any chance a veg file that used to open OK and now will not open without Vegas crashing?

I've had the same thing happen and to every copy of the same project, in fact every project for the one client that I'd archived. Same crash too, the media generator dll would crash. Sent a veg file to tech support but they couldn't unravel the problem either.

Bob.
CorTed wrote on 9/25/2007, 4:13 PM
Yep, opened ok before, but now does not. It may be what you are describing. I am still trying to figure out what is going on... I am not even putting all the blame on Vegas 8 yet, but I am seeing some realy strange things going on with my system. App crashing to desktop, .veggies after loading crashing the app. I'm hoping the team will issue a patched version soon as I am going crazy with the problems I seem to be having, and I hope their updates will fix my problems.....


Ted
blink3times wrote on 9/25/2007, 4:24 PM
You can try a free but good text/code editor that I use:

http://www.pspad.com/en/
farss wrote on 9/25/2007, 4:28 PM
Is your problem only with Vegas?

Sorry to state the obvious but first port of call would be to look for nasties like viruses. Then run some disk tests.

Not that any of that revealed anything in my case.
CorTed wrote on 9/25/2007, 4:39 PM
Yes I only seem have problems with Vegas.
farss wrote on 9/25/2007, 4:57 PM
Wish I could offer more help.

Obvious other things to try:

The .bak files, after copying things elsewhere.
Wierd thing in my case was I had the files backed up, didn't help either.

If you can open the files at all try exporting an EDL via the script and bring that back, might clear the problemo. Or try saving as a new .veg

When all else fails, send the .veg file to tech support.

Email file(s) to other Vegas users, see if they see the same problem, that *should* clear your PC as the source of the problem.

Bob.
pwppch wrote on 9/25/2007, 9:15 PM
There is no "code" in a veg file, just data.

A veg file is a RIFF file. Not much you can do with it, but there are viewers available. Do a Goggle on "RIFF viewer"

WARNING: Mucking around with a veg project in an editor will probably hose the project file. I would only mess around with a copy if I were you.

Peter
CorTed wrote on 9/26/2007, 7:45 AM
Thanks Peter, will try that!
No plans on mucking with it, just looking to see if anything funny is being loaded it.

Ted
dand9959 wrote on 9/26/2007, 8:28 AM
I had a similar issue some time ago...a VEG that worked one day failed to load the next. After much thrashing about, I discovered a video clip that was part of the project had somehow become 0 bytes in size. (Never did figure out how that happened.) Luckily I had a backup. Replaced the 0-size file with the correct original and things worked fine.
Jonathan Neal wrote on 9/26/2007, 8:36 AM
You can always use VegBun to export a list of the files you are using in a particular project, including nested vegs and the files therein.

http://madison.thewikies.com/vegbun.zip

Usage is as follows.

VegBun v1.0.0.0 Copyright (c) 2007 Jonathan Neal 2007-01-01
=============================================================

Usage: vegbun <vegas project> <method> <output directory>

Methods:
A - Generates new vegas project in output directory.
B - Does A, then copies media to output directory.
C - Does A, then copies media & extras to output directory.
D - Does A, then moves media & extras to output directory.