A few serious bugs in Vegas 2.0a

Tonehenge wrote on 8/24/2000, 4:03 AM
Has anybody experienced....
a) Random crashes after recording a take, but not getting
the opportunity to save it (Sound Forge's recovery feature
would be lovely here)

b) This is SERIOUS... .veg edit files becoming mysteriously
corrupted and unopenable

c) Moving the window sizes during playback causes stutter
of sound (NEVER a problem with Vegas Pro 1.0b)

This is a lovely piece of engineering, but these bugs
(particular a + b) are heartburners...

Comments

RickZ wrote on 8/24/2000, 7:11 AM
Hi Glen,

>>>
a) Random crashes after recording a take, but not getting
the opportunity to save it

b) This is SERIOUS... .veg edit files becoming mysteriously
corrupted and unopenable

These sound like hard disk problems, have you tried checking your
disks with scan-disk ?

When I'm recording with VA2.0a, I have the 'prompt to save take' box
UN-checked. As soon as I hit Enter to pause the recording, the file
is saved. Hit Ctrl-R, start another take, Hit Enter, etc. All the
Wav files are there when I'm done. Save the current .veg, and the
whole session is saved.

Hope this helps . .
Regards,
Rick Z
Dylan_Walters wrote on 8/24/2000, 12:21 PM
Hi Glen,

You can post your hardware configuration in detail (hard drives,
motherboard, audio interface)?

Thanks,

Dylan

Glen Chambers wrote:
>>Has anybody experienced....
>>a) Random crashes after recording a take, but not getting
>>the opportunity to save it (Sound Forge's recovery feature
>>would be lovely here)
>>
>>b) This is SERIOUS... .veg edit files becoming mysteriously
>>corrupted and unopenable
>>
>>c) Moving the window sizes during playback causes stutter
>>of sound (NEVER a problem with Vegas Pro 1.0b)
>>
>>This is a lovely piece of engineering, but these bugs
>>(particular a + b) are heartburners...
Ethernetguru wrote on 8/25/2000, 2:56 PM
Yes, I sure have! Not so much the first one, but definitely the
second. *.veg edit files becoming corrupted is something we deal with
on a daily basis. Tech support has had no ideas for us. The only way
we have of fixing it, is renaming the folder where the source files
are stored, and then letting Vegas find the new files one by one.
This works ok, but is only a temporary fix. We have had the "fixed"
files crach again and again.

The other problems we have had are missing codecs in the NTSC DV
format, therefore disabling us from rendering projects, slow frame
rates, even though they are listed as 29.97. This causes audio and
video to be out of sync.

Transitions that disappear.

Missing or corrupted audio in rendered files.

System Specs: PIII/450 with 256MB Ram, 13GB system drive, 18GB audio
drive, 60GB Medea SCSI RAID video drive.
Pyro OHCI 1394 card
Matrox 400 DualHead video card

As of now, we have a project completed and due for delivery next
week, but are unable to render it at all! We are waiting for someone
from Sound Forge to call us back with any kind of suggestions as to
what to try next. We have used SF products for several years, and
like them, but we are beginning to wonder with the bugs in Vegas
Video 2.0a.

If anyone here has any ideas, please post them or email them to me.
Thanks!

Chester Hull
Production Manager
Pro Sound Productions
chester@prosoundproductions.com
Glen Chambers wrote:
>>Has anybody experienced....
>>a) Random crashes after recording a take, but not getting
>>the opportunity to save it (Sound Forge's recovery feature
>>would be lovely here)
>>
>>b) This is SERIOUS... .veg edit files becoming mysteriously
>>corrupted and unopenable
>>
>>c) Moving the window sizes during playback causes stutter
>>of sound (NEVER a problem with Vegas Pro 1.0b)
>>
>>This is a lovely piece of engineering, but these bugs
>>(particular a + b) are heartburners...
brettsherman wrote on 8/31/2000, 12:10 AM
Did you have the same problems with 1.0b? Just wondering whether I
should wait to upgrade. Corrupt .veg files are a real problem.

Chester Hull wrote:
>>Yes, I sure have! Not so much the first one, but definitely the
>>second. *.veg edit files becoming corrupted is something we deal
with
>>on a daily basis. Tech support has had no ideas for us. The only
way
>>we have of fixing it, is renaming the folder where the source files
>>are stored, and then letting Vegas find the new files one by one.
>>This works ok, but is only a temporary fix. We have had the "fixed"
>>files crach again and again.
>>
>>The other problems we have had are missing codecs in the NTSC DV
>>format, therefore disabling us from rendering projects, slow frame
>>rates, even though they are listed as 29.97. This causes audio and
>>video to be out of sync.
>>
>>Transitions that disappear.
>>
>>Missing or corrupted audio in rendered files.
>>
>>System Specs: PIII/450 with 256MB Ram, 13GB system drive, 18GB
audio
>>drive, 60GB Medea SCSI RAID video drive.
>>Pyro OHCI 1394 card
>>Matrox 400 DualHead video card
>>
>>As of now, we have a project completed and due for delivery next
>>week, but are unable to render it at all! We are waiting for
someone
>>from Sound Forge to call us back with any kind of suggestions as to
>>what to try next. We have used SF products for several years, and
>>like them, but we are beginning to wonder with the bugs in Vegas
>>Video 2.0a.
>>
>>If anyone here has any ideas, please post them or email them to me.
>>Thanks!
>>
>>Chester Hull
>>Production Manager
>>Pro Sound Productions
>>chester@prosoundproductions.com
>>Glen Chambers wrote:
>>>>Has anybody experienced....
>>>>a) Random crashes after recording a take, but not getting
>>>>the opportunity to save it (Sound Forge's recovery feature
>>>>would be lovely here)
>>>>
>>>>b) This is SERIOUS... .veg edit files becoming mysteriously
>>>>corrupted and unopenable
>>>>
>>>>c) Moving the window sizes during playback causes stutter
>>>>of sound (NEVER a problem with Vegas Pro 1.0b)
>>>>
>>>>This is a lovely piece of engineering, but these bugs
>>>>(particular a + b) are heartburners...