All projects, in rendered or preview, on all codecs, and now just I confirmed.. all PCs... i.e., I installed Vegas on a fresh PC and the same thing is happening. The new PC is a different CPU and audio chipset so this should not have happened. Meanwhile on the old PC, I reinstalled Realtek drivers (I know Realtek is the bane of the PC world), updated everything, reinstalled Vegas and got the same results. I thought your idea for rending just audio was a good one and still got the same thing, see attached

So from the large pool of pool of blame assignment, I believe this is all in Magix camp vs: Realtek, Microsoft. Just to confirm, I opened some media files that I made last year on this same machine with the issue and there was no pop. I can play other media files with no popping noise but if Vegas rendered it (recently) then there is a popping noise at the start. I thought it would be a driver issue and tried new Realtek drivers, the stock MS driver. Nothing works. So I go back to the fact that everything did work on this machine in the past, so it's probably a Magix thing.

Noise at the end of a clip

More diagnostics: what if you put in a fadein at the beginning of (all) the audio track(s)? How about if you delete a half-second of the audio at the beginning? Does it then pop where the audio begins or still at the beginning of the video?

P.S. if it is rendered in, it's unlikely the audio driver. And if you bring the rendered file back on to the timeline, you would be able to see the noise spike in the pseudo-waveform display.

What a shame that this still seems to be a problem.
I get this wretched click sound at the end of each clip containing audio when rendering, just like the sample earlier.
I never got this with the Vegas Studio, and I thought I was being clever when I upgraded to Pro, but not so.
It seems as though I have lost more than I gained.
So when I render several video clips, each separate clip always ends with a clip. even though I have faded the audio. So to get rid of the clip, I have to clip the end of each audio so that it does not appear in the rendered version.

I am running version 19 of Pro, but am loathed to fork out another £100 plus for something that might just introduce more problems. It would be nice to know that this problem has at last actually been fixed.

Steve

@Steve-Marsh I would strongly suggest you upgrade to version 22. That issue and many others have been fixed. I usually have VEGAS running for DAYS at a time and often forget to save until I'm finished editing some of my projects.

Isn't it a shame that I have to fork out the upgrade charge, just to fix a bug in their original software. I just hope that if I buy this upgrade, that there are not other bugs which I have to pay to get removed on a subsequent version..

The solution to your problem.

I followed jetdv's suggestion and bought v22 and it looks as though the click issue has been fixed, but now
WHEN I ADD A CLIP FROM MY PANASONIC CAMERA, IN M2TS FORMAT ,THE VIDEO IS BLANK
and I have not found anyone that has a solution to this!!!

From Vegas Pro 22's specifications page, M2TS isn't listed as a supported video format:

Import

Video
Apple ProRes, Blackmagic RAW, HEVC/H.265, AVC/H.264, AV1, MP4, MPEG-2, MPEG-1, AVI, WMV, M4V, Sony XAVC / XAVC-S / XDCAM EX / HD 422 / MXF / ProDisc / HDCAM SR, MPEG IMX, DV, HDV, AVCHD, Panasonic P2, RED RAW

If you do a forum search re M2TS, you'll find quite a few comments about difficulties with M2TS and related BluRay files over several Vegas Pro versions.

Surely m2ts files are usually AVC/H264 or even mpeg-2 and shouldn't be a problem. My impression is that it's basically a file type in the same way that mp4 is a file type.

@Steve-Marsh Share a sample of your problematic camera files on OneDrive, Google Drive, etc. and post a link here. Someone will look at the issue more closely.