I don't know why it's doing that, it sounds like the MPEG plug-in is having a problem pulling from two places at the same time, which it should be able to do just fine. I suggest you email tech support on this one, they will know if this issue has come up before, and track it through the necessary people. Although this forum has solved a fair share of bugs, a real stickler like this one might be better served by TS since they have the system for tracking it through.
///d@

sqblz,

Just curious. What sound card are you using? What Operating System?

I get this exact same message when I have many DV captured events with their captured soundtracks, on the timeline. I also use some Xfades. I'll have to try the clean snap to edge tip to see if that fixes it.
When I play clips from the Vegas explorer, I frequently get a momentary Vegas lock up, and then the Audio Time Out message pops up.

Ever since Win XP, my Sound Blaster Live Platinum card doesn't quite perform as smoothly as in 98SE.

I emailed SoFo tech support about 3 weeks ago for some advice, but have not heard back.
The problem occurred in Video Factory as well. Rendering is no problem however.
Other than that..........Vegas seems flawless. I don't have any other issues.

I'm going to try the Audigy card soon. Sure hope that's all it is.

I have a Pinnacle DV capture card, and have had no problems with TMPGenc renderings in Vegas.

Good Luck

I am having the same error with the new ADS Firewire kit for my external drive on my Sony Viao laptop (750mhz).

I purchased my first kit about 2 years ago have had a 60gb, 80gb, and a 120gb all 7200rpm in this enclosure -- no problem.

Last year I purchased a second kit moved the drive currently in use into the new drive kit - worked fine for a while then began getting the error. I put the drive back into the first drive kit and the problem went away. I thought the drive kit was defective so sent it back to ADS. they could not find any problem. They did replace a card inside as a courtisy. Got it back changed the drive back to the kit returned. Had the same error happen. I was thinking that it just was the new drive kits but maybe not if others are having this error too. The new drive kit has the latest DV bridge.

I still am using the original ADS drive kit it works flawlessly.

At no time were the files and projects changed in the HD itself. Only changed enclosures.

So my question is it VV3 that has a problem or is it the new DV bridge used in the kits?

sqblz,

Just curious, since I get this exact same message frequently using DV clips.
What is your hardware configuration? OS, Sound Card, Mobo / chipset?

hey! We're getting timeouts with the new ADS cases also. Our older case also works fine. ADS tech support finally answered my email and sounded puzzled - wants me to send them a screen capture.

This 'audio' error from VV3 clearly has nothing to do with sound cards - which aren't really used when working with DV anyway.

I'm going to include your quote with my screen caps. Cripes - if we can't trust ADS who can we trust?

Hello,

I have the same problem (Randomly), I wrote to SF and no solution by the moment. This problem occurs when I play any project from any Firewire HD (I tried a lot of Firewire HD), but usually I use a Lacie Studio Drive, this drive I used in my old machine (Dual P3) without any problem.

I use a laptop Dell Inspirion 8200 (P4 1600) with a RME Hamerfall DSP (The problem show with any sound card, I tried with a lot)

I tried with defragment every time and no way (I believe that works better without defragment), I use Diskeeper.

I tried with Windows 2000 Pro and XP, the problem show in the two OS.

I tried with APCI PC and Standart PC, and was the same.

I tried with built-in Firewire card and a cardbus Firewire adapter (ADS Pyro) and no way

SF products are the only ones with this problem (Vegas and Acid), all of the rest of my soft work well.

Bye

Sorry folks, I've been out for the last few days (and I will disappear on vacations for the next 3 weeks).

I am amazed (not glad) to see that I am not alone in this problem. From SoFo's reply and your own contributions, I think that we are grabbing something "deep", not very easily traceable.
My HW: MoBo ASUS A7V, Duron800, 512MB memory, 10000rpm dasd only for video, Firewire Pinnacle DV and Analog Pinnacle MP-10 (through parallel). SB Live soundcard on IRQ 5 alone.
I have multi-boot and when I do video I boot to Win98SE. No frills, no innovations in the Video Partition. Just plain optimized config for HW + SW. Vegas 3.0c

I may be near the point of view of SoFo, meaning that I am trying to Xfade 2 pieces of the same MPEG-1 clip and that may fool the codec.
Example,
I have this clip in the timeline: abcdefghijklmnopqrstuvwxyz
I split it: abcdefghijkl mnopqrst uvwxyz
I eliminate one of the miniclips: abcdefghijkl uvwxyz
I extend the boundaries of the two miniclips: abcdefghijklmn stuvwxyz
I overlap/crossfade them: abcdefghijkl(mnst)uvwxyz . I get the error message.
I join the miniclips: abcdefghijkluvwxyz . The error message goes away.

The most strange part of it is that I can get this message in one Xfade an not in another. And in just one circumstance, getting out of Vegas and in again, cured the problem !!

Go figure ...

Sorry to hear about the ADS thing. I have a Granite FireVue xternal HD case which holds ALL my media content. I STILL get the problem even if I move the project and it's media over to my slave internal drive.

The reason I was suspecting my sound card is because I can keep the time outs from occuring by doing any ONE of the following:
1) Muting the audio track. Disabling ALL plugins made NO diff.
2) Disabling my sound card in Device manager or Sounds and Audio Devices(WinXP).
3) Completely uninstalling the SC and removing WDM, then enabling my mobo's onboard AC97 sound - which required a driver install. Using the mobo's onboard sound, the time out errors STOPPED occuring.
4) Deleting the ORIGINAL audio track (in the timeline) that was captured with the DV clip, and using music or ANY other sound for the sound track.
I also get the error if I browse / play DV clips using the Vegas Explorer Window.

I would like to think it has something to do with this WDM issue. I didn't have this problem in 98SE. My SB LIve Platinum worked flawlessly in 98SE. In XP, to get my rear speakers to fire, I have to open an application which plays back sound, then open my mixer and "RE-SELECT" 4 SPEAKER OUTPUT (which is already selected). Windows Media Player in XP will let all 4 speakers fire without doing the above step.

I'm still going to upgrade the sound card, just to see if I can resolve the speaker problem. I don't think this Time Out thing is going to be an easy fix.
Last week I installed Video Factory 2.0c, and it gave me the same error. No other Multimedia Apps. produce errors of any kind.

I'm using the Epox 8KHA+
WinFast (nVidia) graphics card
ALL Western Digital HD's
SB Live! Plat. s.card.
512MB DDR
AMD 1.4 T-Bird
Pinnacle Firewire card(Red) XP provided the drivers. No Studio software or drivers have ever been installed......no thank you.

Various combo's of VIA 4-in-1 drivers, Bios flashings....etc, etc. have been tried.

Is Anyone Else Getting This Audio Time Out error occasionally?

sqblz,
I frequently close and re-open Vegas when the errors start up. This sometimes helps cut down the occurences of the time out.
I can keep the error message box from popping up by hitting the ENTER key as soon as the playback glitch occurs. The program will be frozen for about 10-30 seconds, then it CLEARS and I can continue right where the cursor stopped/locked up.
I see we have the Pinnacle DV and SB Live card in common. Doesn't the ASUS board use VIA chipsets? Hmmmmm. I will have the new Audigy installed by the time you come back from vacation. I'll post any success I have with that, but I'm not holding my breath.
I really need a new sound card anyway, this one needs to go back into my old rebuilt Gateway PC.
We have SoFo stumped on this one. Not enough feedback yet......

I'll also use the ole' Gateway PC (700MHz AMD) with 98SE and try to get the same error.

Thanks.

I talked to our audio engine folks, and the Vegas 3 audio engine does have some inefficiencies when reading from the same stream from multiple places at the same time, which is exactly what happens when you cross-fade a clip with itself. Using a compressed audio format would exacerbate the problem, as would using a drive that might not handle a bunch of seeks and short reads coming in quick succession.

A work-around would be to make a copy of the clip and crossfade to that; the program will treat each as a separate stream and not have to seek around in the media as much. A quick way to do this would be to right-click on one of the events, choose "Apply Non-Real-Time Event FX", pick an FX (such as Graphic EQ), hit OK, uncheck the FX in the chain (so it's just a pass-through), and hit OK. Vegas will create a copy of just the audio used in the event in a new file, and point the event to that audio. This can be seen in the "Takes" menu off the event.

///d@

Thanks SD, I'll try that!

This isn't a problem that I lose sleep over. I just love troubleshooting. "If it don't work....I wanna know why."
It's only a slow down. Sort of like waiting for Premiere to do it's pre-renders :-)
.........and it's ONLY the preview. Renderings are superb.
Using Vegas, I recaptured a 32 min rendering to DV tape done in VFactory 1.0. I broke the capture into 2 parts.
However, after dragging the 2 captured DV files, with their audio tracks, to the timeline of a blank instance of Vegas, and snapped the 2 events end to end with NO edits.......as if to PTT from the timeline.......It locked and eventually popped up the Audio time Out error message. Of course, it printed back out to tape just fine......both parts seamlessly. That new PTT feature is GREAT!
Vegas and the new codec made the parts that were sped up or slowed down play back much, much smoother. Cool! Looks like it's been "digitally remastered!

Anyhow.......more troubleshooting. Let me try this on another PC.

Thanks

I'm getting the lockup and audio error on my SIS645 (not VIA) with Audigy card. Mainly when I shuttle a lot.

I've never really believed it was actually an audio problem - especially since it gets pretty rare if I defrag my drive before editing. Anyway, I don't think the workaround will work for me as I usually have at least 4-5 tracks of audio going at a time. Besides, it's never happened on an audio fade here that I've noticed - just in the middle of clips.

SD and pcfx
Coming from vacation after 2 legs of 19-hour flight each (!!!)
Thanks for your feedback. I understand that Xfading into itself is the culprit. While it is not corrected, the workaround of creating a copy like SD suggested seems just fine.
Thanks again

Hi sqblz,
19 hour leg? Where did you go? Where do you live?
I'm happy to report, that MY ...."Trouble Mixing Audio....The Operation Timed Out" ERROR MESSAGES are GONE!
I can't get them to come back if my life depended on it. I even opened up 3 instances of Vegas, each playing back a complex audio / video project, then opened up Premiere and had it render an mpeg, then browsed around in Windows XP. Not a glitch could be heard. My confidence in this version (3.0C) is back. I'm actually impressed at how stable it really is.

So, what was my fix? Well, I'm not sure, but there were a couple of "issues" that surfaced when I did a total external HD data transfer over to my new 120GB internal drive. I may have had some slightly corrupt files over on that Firewire drive, and didn't know it until it was time to move them. There was one folder and one DV .avi file that gave me a hard time. The avi file had to be dragged into Vegas and have a streaming type rendering done to it. Then I deleted it's .sfk. The original would not budge.
The firewire drive has been pretty reliable, but I had done one of those Fat32 to NTFS conversions using the Command Prompt method awhile back, maybe.........?

The other hardware change, along with the new internal HD, was a sound card swap.
I could not get my SB Live! card to work quite right in XP. Sound would only come from the front speakers.......until I opened the Creative mixer and select "4 spkrs", even though it was already set that way. Then I would get a gentle pop and the rear spkrs would work again. I tried all the driver/software updates for it. Nothing helped. So, now it's back in the other PC on Win 98SE......working beautifully.
I now have an Audigy card (OEM) in this sytem, and all is well! However, the install was interesting. It took forever to get just the Drivers, Creative mixer, and the Diagnostics installed..........jeez, I almost gave up and was ready to do a warm reset when it finally finished. After rebooting, there was no sound, but there was a yellow exclamation point next to a WINMM WDM Audio Driver. Right click, uninstall, reboot, and there it was, the annoying Audigy splash avi with sound from all 4 speakers. Installed the latest drivers, ran the diagnostics, tested the digital output........OK it's perfect.
It was then, after installing both the new HD and the Audigy, that I finally got around to opening Vegas and loaded my "troublesome" projects. They played.....and played.....10 days later, still no sign of trouble. So, I don't think it was a new sound card that made the errors go away, but maybe the uninstall and install process that took care of some XP compatibility issues.
I think it was the "bad data" over on the firewire drive. I'm taking a closer look at this drive. It's been repartitioned/reformatted since then, but something still isn't right. I may do the write zeros test to it.....start over. Currently, it seems to be OK.
One other "Cool" thing. Ever since the install of the Audigy, my MoBo/chipset temps have dropped by 4 deg.F., and I swear even my CPU temp is down by 1 or 2. Huhhh?

Sorry, I couldn't be more help. I hope anyone who ever gets anything other than smooth AUDIO / Video playback while editing in Vegas, will find their fix as well!
Of course, I'm not talking about the preview window and a few dropped frames here and there....:-)

Thanks Sonic Dennis!
Guess I won't need that "work around".

Patrick C.R.