I was sure i could see something on the audio line, however now i cant and most times it doesnt play the artifact in preview only once rendered....

When did this bug start? are they fixing it?

This was fixed in 21 but trimming should be a viable workaround in 20.

I cant find any service packs or updates, they are not wanting to charge for this fix?

The last build release of Vegas Pro 20 was build 411. Given that Vegas Pro 21 was released 4 months ago, unfortunately it would not be expected that any further updates to Vegas Pro 20 would likely be forthcoming.

b411 is the one i am running..... did not have this issue when it was Sony !

The issue affects all builds of 20 as far as I'm aware and was fixed with the patches to VP 21. It seems to have appeared late in VP 19 (though I haven't experienced it).

It seems to have appeared late in VP 19 (though I haven't experienced it).

Me neither.

Background

https://www.vegascreativesoftware.info/us/forum/noise-at-the-end-of-a-clip--140457/?page=2#ca897211

https://www.vegascreativesoftware.info/us/forum/very-strange-audio-problem--138343/#ca865730

Interesting, as the clip that has the noise is right before the clip that came from an iPhone (apple) which was a MOV file.. !! nice they found the issue, cant see how they cant fix it though (with a hotfix)

@ashley said: "cant see how they cant fix it though (with a hotfix)"

It's likely more than a "hotfix's" load of code. This is the exact reason I only have Vegas 21 on my machine.

Having to trim a couple of frames isn't exactly a showstopper for me.

It wasnt in past versions, they introduced the code as "a mistake" and we have to pay to fix that problem they introduced?

The audio engine is being redone, among other things.

I'd recommend to anyone keeping VEGAS updated as it's basically a rolling update model at this point.

This noise at the end of a clip didn't affect everyone so appears unique to some systems. Yet we never managed to work out what was causing it?

Make sure you're rendering at the same frame rate as your original video and project.

In other words, rendering at absolute 60fps and the project being at 60fps rather than 59.940

It wasnt in past versions, they introduced the code as "a mistake" and we have to pay to fix that problem they introduced?

In short, yes. If you don't want to update to at least update 1 of VEGAS Pro 21 (note that the initial release of 21 still had the issue) then you need to go back to VEGAS Pro 18 or older. But you'll lose out on all of the file reading updates that have been made since then as well. Yes, something happened (in an update to VEGAS Pro 19) and the issue remained through 20 and into 21. Fortunately the issue was finally found and fixed. However, unless there's some really radical issue, I wouldn't plan on seeing another update to version 20.

If you just buy the "smart scription", you can remain on the "current" version.

My issue here is its clearly a BUG that i didnt create, this would never happen with the SONY software they would have fixed it, however for some reason i have to "pay" to have a brig fixed they in traduced> Should i be looking at using other software that the developers dont expect me to pay for bug fixs they introduced?

this would never happen with the SONY software they would have fixed it,

That's funny. I seem to remember many bugs Sony introduced in Vegas that did not get fixed until later versions... And people made the same complaints you are making now. But I seriously would not expect an update to 20 to fix this issue just as I'm not expecting an update to 19 to also fix this same issue. They're developing 21 now. That's where the fixes will be.

My issue here is its clearly a BUG that i didnt create, this would never happen with the SONY software they would have fixed it, however for some reason i have to "pay" to have a brig fixed they in traduced> Should i be looking at using other software that the developers dont expect me to pay for bug fixs they introduced?

@ashley It would be a nice gesture for them to do this, though I've only seen it happen twice before with program-breaking issues (which this is not). Basically think of VEGAS as a rolling beta as major components like the audio and video engine are being overhauled and the overhaul doesn't break neatly across the "annual" (arbitrary) version numbers.

If you're not on the latest version you will be stuck with bugs new and old.

Is other software better? Adobe is a subscription model so you are always on the latest (and pay for the privilege). Resolve is a one-time fee as they don't need to make money on the software side.

So to tidy this up... we are now using DaVinci Resolve (which is free, they do a paid version as well, most for scripting and other power uses).

Its replaced Vegas Pro and Adobe After Effects (it does both VERY well), we have re-created some media logos in it so no longer require Adobe After Effects, also with some real basic scripting (os.date("Copyright %Y") this now puts the copy write notice on the playing media logo AND changes the year for what ever year you happen to be in, yep, that easy, so you no longer need to keep rendering out your header media each year, the current use will update the date live before it renders.

Also the way it stores projects is via a flat file database, this allowing you to move from one PC to another VERY easy, they also do Proxy Media so its not always reading your huge files during edit AND they have a free server (installable on the LAN) that will allow you to share all these projects to others in the office, and work from the same database at the same time.

Mastering Davinci Resolve in just 7 days (and not complaining about some of the impasses in DR)?  Wow, I used DR without getting great results in such a short time....why doesn't everyone realize how easy it is with the workflow of this perfect software and leave Vegas? 😎
Seriously, somehow I can't see how VP13 is supposed to be better or even more bug free than the current versions, at the end of the day all the ranting here with casual disregard for those helping makes little sense.