@Former user What do you see as the playback issue with this?

I'm testing with a NVIDIA 4060 mobile and see out of order frames (choppiness that when played back frame by frame shows some are repeated, some are likely missing).

I set the field order to progressive if it matters in project properties.What deinterlace method are you using?

Where two events meet I do see glitching but only with smart adaptive mode:

Using @MikeLV's file, I observed that Vegas Pro 22-194 decoded the last two video frames as black, while every other application I use, decoded the last two frames correctly.

My Sony RX10-IV will shoot AVCHD (though I never use that format). I experienced the same decoding anomaly with AVCHD media from the RX10-IV camera on Vegas Pro 22-194.

Vegas Pro 21-315 decoded the last two frames as expected.

@Former user What do you see as the playback issue with this?

I'm testing with a NVIDIA 4060 mobile and see out of order frames (choppiness that when played back frame by frame shows some are repeated, some are likely missing).

I set the field order to progressive if it matters in project properties.What deinterlace method are you using?

deinterlace = blending. It was the frames not being in correct position that I noticed. This can change and areas that did not play correctly later play correctly.

This is playback and then VP22 playback compared to VP20 using difference.

@MikeLV, thanks for the sample. Noticing several issues. Forwarding the issue to development team.

I'm having problems with my Vegas22 build 194 video occasionally "stuttering" where two (mp4) clips come together. Looks like the dancers in the video suddenly go into some kind of spasm for a few seconds. I am also getting the occasional black frame - again, as far as I can tell so far, only right where two clips abut each other in a project. My workaround right now is to switch to a different camera at that point in the multicamera project. That works for getting product out, but it's not a real solution... I have to go to a camera shot that I wouldn't prefer to use.

I'm up against some very tight Christmas-time pressure for delivering these videos, so I don't have time to log and post a whole lot of technical info about my Vegas22 projects, but I just wanted to "chime in" to log that there's more than one of us having the occasional stuttering and/or blackframe problem. I never encountered this with earlier versions of Vegas (I go all the way back to the Sony days...)

-----UPDATE:

I re-created my project in Vegas Pro 21, and the stuttering/blackframe problems went away. When the Christmas video season is over, I'll upload some technical information. My plan just now is to stay with Release 21, and watch for an Update Notice for Release 22 194 in hopes that the problem will have been solved.

@ernie-tamminga When you have time could you make a post about your specific issue and include media and the GPU you use? We know there are issues with various formats of media- there have been probably 100+ posts since spring on decoding.

The MXCompound decoder is new; it debuted in build 300 of VEGAS Pro 21. While much more stable and faster than its predecessor, it has issues with a variety of media. The VEGAS bugfix list is all about that.
As a workaround you can go back to the older so4compound by checking "legacy AVC" or "experimental HEVC" decoding in options/preferences/ file io (depends on what footage you are using, hence the importance of details) and see if it helps you get projects out.

If either decoder is getting overloaded at a transition point between videos you can help it by prerendering some frames by making a selection and hitting shift + b (shift + m if you want it to persist).

Mike's footage here is with an old format not in wide use anymore (Interlaced AVC in AVCHD container) so while you may see similar symptoms it's not the same thing.
It's also completely different from what the original poster pointed out which are visual glitches, not black frames. We had issues like this when so4compound was introduced with VEGAS Pro 15 but it was subsequently refined. Detailed user reports and sample media will get MXCompound refined, too.

@RogerS I was told a long time ago by one of the gurus on here that although it says interlaced, the footage is actually progressive. I think he was right because I never have to deinterlace it. Also, my problem with the AVCHD footage is the same as the original poster's, i.e. it pixelates/corrupts in random places on the timeline, and that corruption does carry over into the final render too.

@MikeLV Interesting, so you don't have to deinterlace- but you set VEGAS to a progressive project, right?

I hope we can get someone to replicate the pixelation; it may be an AMD issue as so far nobody else who tested this file has seen pixelation or corruption. We found other problems.

I was told a long time ago by one of the gurus on here that although it says interlaced, the footage is actually progressive. I think he was right because I never have to deinterlace it.

Yes, some AVCHD cameras like my 12 year old Canon Legria (PAL) consumer camera do "record" 25p as 50i interlaced. But it's actually recorded as 25p but labelled as 50i. I forget the reason but it's something historical. It means that in Vegas I need to alter interlacing to progressive in each Events properties, or in Project Properties for deinterlacing use Non.

@MikeLV Interesting, so you don't have to deinterlace- but you set VEGAS to a progressive project, right?

I hope we can get someone to replicate the pixelation; it may be an AMD issue as so far nobody else who tested this file has seen pixelation or corruption. We found other problems.

Yes that is accurate, I choose progressive in my project setting, no deinterlacing is needed, which is good, saves a lot of render time.

Going back to the pixelation issue as I just discovered another anomaly:

First, I dropped the footage that I shared with you on my timeline, and observed no pixelation issue no matter how many times I played it or clicked around in the timeline during the event. So perhaps for it to happen, it needs to be a longer event.

Next, I opened my ~40 minute project where I did notice the issue and I clicked around until I saw it happen. Then I put a marker at that spot. Then I clicked around until I found another corruption issue and marked that spot too. I then closed the project and re-opened it. The first marker this time was clear, no corruption, but the second marker is showing the same corruption. But if I click enough times on that marker, the corruption goes away?! Really strange stuff.

duh, this is not going to be easy as it happens in the random place and random time.

@MikeLV Just to confirm this is with VEGAS Pro 22, build 194, right? Your signature says 21.300 but I assume that it's just not updated.

Let me try dropping your sample into longer projects and see if corruption appears. If there are Fx, etc. that make it more likely please let us know. So far none of us have seen it who tried this footage (not doubting your experience, just trying to repeat it!)

@RogerS Yes I'm using the latest version, sorry about that I will update my signature.

The issue happens with or without any fx applied.. Yes this is troublesome, but it looks much like the @Debbie-Whitmer's first photo, i.e. it's not the whole image that distorts, just part of it, which always seems to be the (moving) subject, not the background as far as I can tell.

I just rendered this short section from the timeline and discovered something else about the issue. The distortion, at least in this case, seems to come from another section of the video. He's holding the guitar one way while talking, and then when the distortion happens, the guitar is more horizontal. He didn't move the guitar, so that distortion comes from somewhere else in the event, too weird!

I was looking for more sections upload and found one. I started to mark it off on the timeline to encode, played it again and the distortion went away and doesn't come back in that particular section. So the issue is totally intermittent, it comes and goes on its own. Hope they can figure it out.

Just wanted to check in on this issue; is there any development? When there's a fix, will this thread be updated, or somewhere else?

There have been no updates to 22 yet and it's probably vacation time. Check the change log when a new build is released.

Ok will do.. Is there a way to get notified when a new build is released (other than the program telling me) ?

Ok will do.. Is there a way to get notified when a new build is released (other than the program telling me) ?

Hi @MikeLV - I wish i knew too.  I originally posted here about this problem back in November 3, 2024 and drop boxed to Vegas support a sample of my pixelated video for them to analyze it along with the Media Info and there has been no corrective update yet as I keep checking the Vegas Pro 22 software.  It’s been a little over 2 months ago since this was initially reported.   Not sure what is taking so long for an update but hopefully it will be soon.  But in the meantime, Vegas support has been very helpful here and kind as well.  

I wonder if it would be better if we opened support tickets on this issue.. Perhaps if they see more than one come in, they'll prioritize a fix. Have you already contacted support (not via the forum) about the issue?

I wonder if it would be better if we opened support tickets on this issue.. Perhaps if they see more than one come in, they'll prioritize a fix. Have you already contacted support (not via the forum) about the issue?

Hello @MikeLV - I have only informed about this pixelation issue through this forum and I was under the impression that the Vegas support team was already notified as it was requested that I upload my video to Drop Box to be analyzed and the Media Info was also given to them. It's been so long that I do not know how to submit a support ticket on it. In the past, it was my understanding that it was always through the forum that updates eventually came. In addition, in this forum, it was given to me a temporary fix and that fix has been working for me. I think as for now, I'll keep checking the software for updates. BTW, Happy New Year!

I have only informed about this pixelation issue through this forum and I was under the impression that the Vegas support team was already notified as it was requested that I upload my video to Drop Box to be analyzed and the Media Info was also given to them

The forum is a peer-to-peer / user-to-user forum and is not a method of accessing Support assistance. You were likely asked by other forum members or Moderators (who are volunteers but not MAGIX employees) to upload media but that would have only to have been to help forum members to try to assist/advise you - but this is not a formal Support request.

To lodge a formal Support request, you need to click on the Support icon in the forum's header, select 'Vegas Pro' and scroll down to the bottom of the page and click on the 'Contact Support' button -

https://www.vegascreativesoftware.info/us/support/vegas-pro--1/

You don't need to do anything further as we did share this media with developers. If there is additional media you need help with feel free to share that too.

If you wish to open support tickets you can, of course. Just don't expect an immediate solution as this needs a fix in software.

@MikeLV - Hi there! It looks like there is finally an update for Vegas Pro 22! Clap! 👍 It's now Vegas Pro 22.0 (Build 239). Check out your "Check for Software Updates" under your "Help" menu if you have not done that yet! 👍