V4 w64 error

tbrowning wrote on 2/28/2003, 10:10 PM

OK. The first time I thought I did something wrong, but now it did it again...

I was recording a live concert in V4, and the length of time caused the stereo audience mics file to go over the magic 2.0MB limit. Therefore, Vegas saves it off as a w64. I did this very often in VV3 as we record the Church Service every week, and it often goes long.

But now, everytime I have done this in V4, I get a corrupt file that Vegas reports as being 0 length even though it is 2.2 gigs on the drive.

Anyone else seen this behavior? Anybody got time to try to repro it?

Most importantly, anybody know how to recover the audio?

Tom

Comments

Geoff_Wood wrote on 3/1/2003, 12:22 AM

Act of God ?

;-)

geoff

MarkWWW wrote on 3/1/2003, 10:37 AM

I don't know why this has happened - never experienced it myself, though I virtually never record anything as long as that.

But I can offer a suggestion as to how to recover the audio. Have a look at the thread starting here where someone else had a similar problem and I explained how to recover the audio using Sound Forge.

Best of luck

Mark

twright wrote on 3/24/2003, 7:22 AM

I see this problem too. It is easy to duplicate, just try to record an audio file with a size that exceeds 2 GB.

In VV3 I would record a large file, click the 'Done' button to keep the recording (VV3 would automatically switch from 'wav' to 'w64' if the file size exceeded 2GB), VV3 would build peaks for a while, then the waveform would show up on the timeline ready for editing.

With Vegas 4, nothing happens after I click the 'Done' button. No peaks are built, no waveform appears on the timeline, and there is nothing to edit. A large (> 2GB) file with a 'w64' extension is created, but Vegas can't read it. If file recorded is less than 2G, it is saved as 'wav' and everything works fine.

Can anyone succesfully record an audio file greater than 2GB in size?