If you have the option checked in Preferences to create
a .bak file, you may be able to go back to a previously
saved version and at least salvage some of your work.

If so, you should have the following files somewhere in
that directory:

xxx.veg
xxx.veg.bak

Rename the "xxx.veg" that you think is corrupted
to "xxx.veg.old" and then rename the "xxx.veg.bak" file
to "xxx.veg", then try to open the project again.

Good luck!

KAC ...

Thanks for the suggestion, I did this already and it didn't
work. I know what the specific problem is though. I
opened a new vegas test project and loaded one track of
audio. I then replicated what I had done previously in the
corrupted file, which was to add another bus (bus B) and
then assign that bus the REVERB plugin. I then saved it
and exited. When I tried to open that test project again,
it came up with the exact same error. So, it must be
related to loading the REVERB plugin. I then upgraded my
Vegas version to version D. There was some notation about
something like this having been fixed in the new version.
However, after upgrading and restarting the computer etc...
it still has this problem even when I start off with a
fresh project. There is something wrong with it erring out
as it loads the REVERB plugin. Here is the exact error
details:

Sonic Foundry Vegas Audio
Version 2.0d (Build 384)
Exception 0xC0000005 (access violation) READ:0xFFFFFFFF
IP:0x1021CAA
In Module 'VEGASK.DLL' at Address 0x1000000 + 0x21CAA
Thread: GUI ID=0xFFFB9D59 Stack=0xBAF000-0xBB0000
Registers:
EAX=00000000 CS=016f EIP=01021caa EFLGS=00250293
EBX=04384078 SS=0177 ESP=00baf218 EBP=043781c8
ECX=00ce4fd4 DS=0177 ESI=00ce4dd0 FS=2127
EDX=01159860 ES=0177 EDI=bff76dd7 GS=0000
Bytes at CS:EIP:
01021CAA: 8B 10 FF 52 0C 8B 83 80 ...R....
01021CB2: 03 00 00 8B 8B 68 03 00 .....h..
Stack Dump:
00BAF218: 00000000
00BAF21C: 00CE4FD4 00CD0000 + 14FD4
00BAF220: 00000000
00BAF224: 00BAF4F0 00AA0000 + 10F4F0
00BAF228: 0437C066 03F90000 + 3EC066
00BAF22C: 043781C8 03F90000 + 3E81C8
00BAF230: 00000004
00BAF234: 00000000
00BAF238: 00000001
00BAF23C: 0000AC44
00BAF240: 00000000
00BAF244: 00000000
00BAF248: 00000016
00BAF24C: 00000000
00BAF250: 3873D131 35630000 + 310D131
00BAF254: 11D32D0F 100D0000 + 1C62D0F
> 00BAF284: 0110A6D7 01000000 + 10A6D7 (VEGASK.DLL)
00BAF288: 0438746C 03F90000 + 3F746C
00BAF28C: 00000032
00BAF290: 00BAF4D4 00AA0000 + 10F4D4
00BAF294: 8004E00A 8001B000 + 3300A
> 00BAF2B0: 00420009 00400000 + 20009 (VEGAS.EXE)
00BAF2B4: FFFFFFFF
00BAF2B8: 00000000
00BAF2BC: 00000000
00BAF2C0: 81E174DC 81E10000 + 74DC
> 00BAF2CC: 020021B7 01960000 + 6A21B7 (LSXMPXP2.DLL)
00BAF2D0: 00000000
00BAF2D4: 00000005
00BAF2D8: 00000001
00BAF2DC: 00000000
> 00BAF2E0: 00460000 00400000 + 60000 (VEGAS.EXE)
00BAF2E4: 0C0900BA 06AE0000 + 55B00BA
00BAF2E8: 00000001
00BAF2EC: 00BAF3CC 00AA0000 + 10F3CC
00BAF2F0: 00000002
> 00BAF308: 00468368 00400000 + 68368 (VEGAS.EXE)
> 00BAF380: 005BDAA8 00400000 + 1BDAA8 (VEGAS.EXE)
- - -
00BAFFF0: 127719EE 100D0000 + 26A19EE
00BAFFF4: 83D4CFEC 83D2D000 + 1FFEC
00BAFFF8: BFF89DD5 BFF70000 + 19DD5 (KERNEL32.DLL)
00BAFFFC: 00000000

I have also had this happen with Vegas Audio. For me it
was also a reverb plug-in on a bus. The reverbs that Vegas
doesn't like for me are:

- FreeVerb - all versions
- TCVerb - native and full version.

There seems to be something wrong with the interaction of
certain plug-ins with the Vegas coding. Which is wierd
because they should all be DX compatible and they all work
in other programs...Wavelab, Cakewalk, etc.

Biff

"There seems to be something wrong with the interaction of
certain plug-ins with the Vegas coding. Which is wierd
because they should all be DX compatible and they all work
in other programs...Wavelab, Cakewalk, etc."

Yes, this is very true. I finally managed to get the Antares plugs working in Vegas but only if I don't use any VST-DX
adapters - which is a great pity as I'd really like to be able to use my VST plugs in Vegas the way I can in any other of my
audio programs. Also, with my collection of plugs if Vegas scans for plug-ins when opening it will always crash and reboot
before it's fully open. So I have to keep a version of my registry around where it's not scanning for plugs. I'd love to find out
what triggers it to scan so that I can disable that trigger.

Well, the only reverb I have on my system is from
Soundforge 4.0e. I think that is the reverb it's using. I
didn't even like the reverb it created (was pretty crapy)
and took that track off that bus. It seems pretty stupid
that it craps out reading a plugin from one of it's own
products. I'm getting really pissed and thinking about
trashing all their products... this was an entire months
work of editing down the drain and now I'm in a jam and
technical support hasn't responded back to me.

My experience (at least with Vegas 2.0d) is that it doesn't like some of Sonic Foundry's plugins, including SF Amplitude Modulation.

What you are experiencing is horribly bad baby-simple
programming and inept programming module transfers during a
programming construction. I am a DirectX programmer and
this happens quite a bit , but usually only during Alpha
stages, then MAYBE beta stages of program construction.
Count your blessings and move your audio files back wherer
they were - Cakewalk programs (except the newest "10"
release has fixed this) audio files have to be located in
specific areas for project management unless you save a s a
Cakewalk Bundle File, which compresses the WAV files and
copies them compressed and "attached" to the MIDI file
and .pk file. BTW, did you ever notice how many programs
use the .pk file extension - not to mention the .flt
and .flp and .ras extension. When in the hell are German,
Native Instruments, and Microsoft programmers as well as
Video, Graphic Atrs and Audio programmers EVER going to get
together and FOLLOW MICROSOFTs EXTENSION NAMING CONVENTION
which via internet is AVAILABLE TO ALL SOFTWARE DEVELOPERS
IN THE WORLD? I say Microsofts conventions because they
are the only ones that seem to adhere to some what of a
somewhat agreed upon standard of file extension naming.

Acually by the mention of an access violation, the REVERB
plug-in is most likeley not compatable with the current
version of DirectX. My discovery has been that whenever we
upgrade our DirectX engine - we MUST RE-INSTALL ALL OR MOST
OF OUR PLUGINs (the ones that just drag and drop .dll
or .fxb's don't seem to behave as rudely as your REVERB plu
gin) This same re-install advice actually works to fix
VST's that seem to crash programs. But, in this case,
judgiong from the dump, DON't blame the host program. BTW,
defeat your Anti-Virus program temporarily while you are
working on any audio project. You will actually save about
10mb of active real RAM that way and you will elimnate more
Processor lag, which is a good thing when it comes to Audio
file work.