Help! Punch in fiasco

bplogic wrote on 7/1/2003, 8:46 PM
Hello all. I had been running Vegas 3.0c and 4.0b on windows 98se. Worked great, but I finally decided I had to take the plunge with xp.
Everything seemed great until I did my first tracking after the upgrade. For some reason, whenever I punch in on a track, there's a 10% chance that the recording I did will get lost on the main screen. The actual wave file is always right there where it's supposed to be, but sometimes it doesn't show up on the screen, so I have to go into the explorer window and drag into place. Very time consuming, especially with clients looking on! It's especially bad when punching 12 or 14 tracks at once.
Anyone run into this before? I haven't been able to figure out what it is about that 1 time out of 10 that makes the new region disappear. Do I have something set incorrectly? Am I inadvertantly doing something to cause this? Help!

System:
Winxp pro
1.2 gig athlon on a shuttle mobo with via kt133a
640mb pc133 ram
ide and firewire drives
echo layla (asio and purewave drivers mainly).

Thanks
Matt

Comments

Kyoto wrote on 7/1/2003, 9:02 PM
Yes, this occasionally happens to me too. Maybe one time in 50. I'm using XP with an Aardvark Aark 24, P4, Vegas Video 3.0c. At first I also thought I did something wrong, but now my gut feeling is it's some bug in Vegas.

Maybe someone else knows more about this issue!
PeterVred wrote on 7/2/2003, 10:57 AM
Are you making splits in the event before/after punch-in point? and then punching the cut-out event?
or are you spliting event once, then dragging event sides away and inserting a new event?

I have been running XP for a little over a year and it has been better than 98.
I did just upgrade my mobo and am using onboard sound instead of my SB Audidy
and am having some little bugs, not like yours however.

Pete
bplogic wrote on 7/2/2003, 2:38 PM
I'm doing both. But, I think I may have figured out some factors as to why this has been happening. Kyoto, I wonder if you could check some of this stuff out and see if it makes your problem any better/worse

1. When I'm working off of a firewire drive, I seem to have more problems than I would working off of the internal IDE audio disk.

2. It may be a buffer issue. In V4, I boosted the ASIO buffer up some, and it made a big difference. Still having problems though, but instead of 1 in 5 or 10 it's more like 1 in 30 or 40. I'll try a bigger buffer still to see if it fixes it, but that buffer will be bigger than the one I was using on Win 98se that was rock solid.

Does anyone have any idea why working on a firewire drive could create issues like this? Can anyone verify that a too-small buffer causes problems like this?

Matt