Charlesdem, it has not been fixed yet in 4.0c although everyone may not experience it many do including myself. See this thread.

http://www.sonicfoundry.com/forums/ShowMessage.asp?MessageID=182184&Replies=30&Page=10

It doesnt show up in renders however. Not big enough of an issue to not purchase Vegas in my opinion.

sorry - I did read about that and forgot.

I'm sorry this is affecting you, but I certainly think it's still worth the purchase!

When I tried it, the old project I loaded into v4 had enough edits to make it sound terrible, just can't play back that to my customers. They would probably stop in the middle of recording, asking "what's that noise there?"...

My second engineer also tried it once and once only, almost went crazy over some guitar edits, and won't touch the program again until this bug has been fixed.

So you see, it would really affect my work, unfortunately. Does anyone have an idea how soon a new build can be expected? Please... I want my V4C...

I know what you mean. I feel like making up a placard that reads: "It's only in playback. It renders fine" to hold up over and over.

Exactly, I've also got a Creamware DSP-system which only works in real-time, and also mix on analog sometimes, so I love the idea of using ASIO instead of wav-drivers. (especially when I want 24 analog outputs under my Win2K which is simply not happening with wav...)

<<"It's only in playback. It renders fine">>

lol... I find myself saying that so much these days! I often have to render just a little section to prove it's ok.

>><<"It's only in playback. It renders fine">>
lol... I find myself saying that so much these days! I often have to render just a little section to prove it's ok. <<

I'm not laughing at all! I mix through a console and primarily use outboard processing. Therefore I'm still using Veg 3. Due to the reports about all these bugs in 4, I haven't even bothered to install it (I bought Vegas 4 when it was first released). ;-(

drbam

I'm getting a little off topic here, but I'm curious as to how the majority of the posters to this forum use Vegas. Do you mainly use it to multitrack or are you doing some serious editing? (What I mean by that is taking an event and chopping the hell out of it.) It seems the folks that are doing hardcore editing are finding their fair share of the problems. You can lump me in that last catagory.

I use Vegas 3 for recording, serious editing and mixing. I create the mix in Vegas but also send 16 out through a console to use outboard efx - mostly high quality verbs. Until plugin verbs can match that of a better Lexicon (PCM line), which is pretty doubtful, I will continue to work this way. I also use Sound Forge 6 for some editing but more and more I am finding that Vegas can do what I need and often times quicker. As I've noted in other posts, I haven't even installed Veg 4 yet due to all the problems. :-(

drbam

I record into Vegas, then edit, edit, edit and arrange and use it as my mixing software.
The only outboard gear I use are preamps/compressors/eqs to get the audio into Vegas. It's all internal to Vegas from then on. Final mixes are rendered to wav or aif depending on the final mastering system.
Perfectly recalled mixes make me smile. :)
bgc

I have the same problem too. It's very frustrating that this is still not resolved in 4.0C!!!!! Hopefully 4.0D will have the fix. Meanwhile, I finally got fed up and went back to 3.0 and haven't had a problem since.

Same bug for me. My Vegas Audio 2.0 LE works better than VEGAS 4c , although more limited in functionality. At least there's no clicking, hissing and popping -- stretching during simultaneous playback/record -- it's unusable for me. Had to go back to Vegas Audio 2.0 LE.

Can't imagine it's my system -- 1 GIG RAM 2.2 GHZ P4, 60 GIG UDMA

Using DELTA 44 sound card.