I try to upload using this button but i got error last time ,now is okay. I just drag and drop the video, i use this video very much and i make sometimes video from around 100 clips so i can't cut every time last 2 pixels from every clip... it's very annoying.

Where do the clips come from? Post media info on one of them. Instructions here https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

before I bought the 20 version, i worked for many years with the 13 version and i never had a similar problem. After i bought version 20 of every clip i use, in the end there are almost always those 2 pixels that I have to cut, I haven't looked for a solution because i edit very long clips (about 8 hours each) and it has never bothered me because anyway the end of the video itself is cut off. Soon I'm starting to make clips that will be assembled from 100+ other clips and it will be a hell of a pain to cut 2 pixels on each individual clip, it's just a waste of time.

I don't know what causes it but here is what I'd do for a workaround;

1) Create a New Project
2) Put the OUTRO video on the timeline (say yes if it asks for adjusting project settings according to the video)
3) Cut off the part you don't want at the end of the video
4) Save the project. "OUTRO_nested.VEG" (or any name you like)
5) Use the `OUTRO_nested.VEG` file in your projects instead of your original video.

This way, you create a `copy` of OUTRO that has the tailing part already cut off, so you won't be repeating the cutting process everytime you use that video in your projects.

It's a known issue that the developers have acknowledged and are working on. Please test future updates as they become available and let us know your experience with them.

@TheSoundTV Turning off the clip property "Loop" might be a work-around. Also look at the setting "Quantize to Frames".

Thanks for the answers!

I think the Quantize to Frames disabled may solve the problem. I will need some time and I will tell you the result

@Musicvid said:

"It's a known issue that the developers have acknowledged and are working on. Please test future updates as they become available and let us know your experience with them."

This is a Vegas Pro 19 and up issue (at least). I just went back to Vegas Pro 14 to finish some work. If you don't think the noise at the end of the sample video is loud enough to be a bother, just know that I'm easily annoyed with little ticks and clicks that are generated by editors.

@TheSoundTV

"... in the end there are almost always those 2 pixels that I have to cut..."

Please stay around the forum long enough to learn the difference between a pixel and a frame.

Vegas Pro through the ages...

Vegas 20-214

@Musicvid said: "Please test future updates as they become available and let us know your experience with them."

Vegas Pro 19-648 still has the issue.

Yeah , the problem is still here and is the same in your video. I hope devs find a solution about this.

Well, glad I'm not the only having this issue... I've had previous standalone versions of Vegas, but I just got the Pro 365 Subscription for version 20 and this is the first time I've encountered this. It's more annoying for me than anything as long as I remember to cut off that last half second, but I have almost forgot a couple times

I have the exact same issue with my Vegas Pro 20 (updated). Likewise find it very annoying. Have asked for support from the Vegas technicians about the problem. Will let you know if they say anything really helpful. The fault seems to me to be in the building of the peaks in the audio track when you load it into the timeline. If it's a software issue, then that's pretty pathetic in my view. Had no such issue with Vegas 17.

When this happens in the future, try right clicking on the media file (probably any media file) in project media, then open the video so it plays in a media player, then close and go back to vegas. I did this once and it fixed the audio distortion/noise. Problem is I've tried doing this since, and it doesn't do anything.

I had thought vegas going from foreground to background and back to foreground somehow fixed the problem, turns out it only worked that once, so likely chance/coincidence

The fault seems to me to be in the building of the peaks in the audio track

I have seen some strangness with the peaks. sometimes it shows the loud the distortion, sometimes not, other times the peaks will flatline where the distortion is. It's very weird and transient.

Further to @john_dennis superb analysis over the years, I can confirm this was introduced with Vegas 19 build 636 and above. Vegas 19 build 550 is not affected. All versions of Vegas 20 are broken.

The simple solution I find is to click the middle box at top right of screen (the one that is there with any programme) so it puts the programme down into the bottom bar, click the Vegas Pro icon, and the edit screen appears again. Wait till the blue circle stops spinning (two seconds or so) and the noise disappears.

I don't pretend to know why it works, but it's quicker than the other solutions mentioned here. Hope this helps.

I think I have the same problem, has anyone managed to solve this?
 

@m3lquixd @TheSoundTV @noisywan @Colin-Anderton

Please verify that this is fixed in Vegas Pro 20-402

@john_dennis, I'm still seeing the issue in build 402...

@jetdv

Thank you for testing. I went back and ran five render options and all failed as before except HEVC which was truncated by two frames.

@m3lquixd @TheSoundTV @noisywan @Colin-Anderton

Please verify that this is fixed in Vegas Pro 20-402

 

Tested with 2 mp4 AVC files and I see the issue. It's not fixed.

I did notice something odd, though. I loaded a project that has the issue on the one clip which I had shortened. I added that same clip to the timeline again. This time it did NOT have the issue. I expanded the original one back out and it did NOT have the issue.

I'm wondering if this is something deeper. If I start with a fresh opened project, it doesn't happen? If I've done my editing and then add that clip at the end it does? So maybe it's somewhat related to what's been done before adding a clip that causes this to happen?