It's very bad

@Former user - Hi there! Yes I know!! But @RogerS gave me a quick solution or work-around and it worked and it was very easy to do. It got rid of all the Pixelating, black frames and flickering!

But thanks for responding and seeing just how bad it was!

Debbie W.

 

Another problem, at frame 62,044 which is the frame after it recovers from multiple black frames it's not showing the correct frame, I think that's really frame 62,100, an I frame. I was confused as to how it was recovering on a non I frame, but it doesn't.

Green and black frames may appear randomly. Not everyone may encounter the similar situation.

As for MediaInfo, yes, it is quite 'complex' and extremely technical, but it is important to know the MP4 media.

Thanks @Former user for helping testing as well.

Green and black frames may appear randomly. Not everyone may encounter the similar situation.

As for MediaInfo, yes, it is quite 'complex' and extremely technical, but it is important to know the MP4 media.

Thanks @Former user for helping testing as well.

@set - @Former user - Thank you both so much for helping! 👍❤️

I see glitches and black frames on both my RTX 4060 mobile and RTX 2080 desktop GPU so it seems to affect a variety of hardware.

Hopefully you can keep using this workaround until the developers can fix 22.

The pixelation is quite simple to reproduce. I have here a project, where I have marked pixelation, black frames and blocking - in your project. In addition, the footage is not from a real camera - Vegas was never designed for that. And - it shows a variable frame rate, what is another issue for every NLE.

This goes into the internal discussion with the development team.

Let us wait what they say.

The pixelation is quite simple to reproduce. I have here a project, where I have marked pixelation, black frames and blocking - in your project. In addition, the footage is not from a real camera - Vegas was never designed for that. And - it shows a variable frame rate, what is another issue for every NLE.

This goes into the internal discussion with the development team.

Let us wait what they say.

 

@Wolfgang S. - Thank you for your post. I have used Vegas for a very long time. My first program that I received as a birthday gift was Sony Vegas 8.0 Pro. Then later, Magix took over. So, I am a good customer of Vegas and I like Vegas. I know when I’m having problems with Vegas and when I cannot find a solution, I ask. I mentioned earlier in this conversation that I have been doing post production for a radio station on a particular program they are broadcasting and I personally know the radio host. In talking about cameras, I stated earlier that when the radio host first started broadcasting via video nine (9) years ago he first used his iPhone camera to do LIVE Streaming on Facebook and then later, he bought a MEVO camera and he’s been using the MEVO camera every since. When the LIVE streaming is complete, I download the video to obtain the raw footage so I can do post production on it. So when you say, “…the footage is not from a real camera…”, that statement is perplexing to me. Of course the footage is from a real camera. The footage came from a MEVO camera. I do not understand why you said that.

I think what @Wolfgang S. means is, the media is not recorded in the camera whether it is iPhone or Mevo Camera, the camera is just sending video signal to Facebook's live streaming and Facebook web platform is recording it. So you download the video from Facebook's web platform, not taking from iPhone or Mevo Camera system.

I think what @Wolfgang S. means is, the media is not recorded in the camera whether it is iPhone or Mevo Camera, the camera is just sending video signal to Facebook's live streaming and Facebook web platform is recording it. So you download the video from Facebook's web platform, not taking from iPhone or Mevo Camera system.

@set - Thank you so much for explaining this; I appreciate that very much. You have been very helpful and kind and understanding. I did not know how this procedure worked with LIVE streaming with the camera only sending out a video signal to Facebook’s web platform. You learn something new everyday! However, whatever the case may be, I’ve been downloading this type of video for 9 years and have used Vegas to edit it and have produced high quality work in the post production work using Vegas Pro. Thank you again for your reply!

Sincerely,
Debbie W.

However, whatever the case may be, I’ve been downloading this type of video for 9 years and have used Vegas to edit it and have produced high quality work in the post production work using Vegas Pro. Thank you again for your reply!

Sincerely,
Debbie W.

Your video is recorded in x264, very common, the free video editor that comes with Windows10 plays it fine, and so did Vegas until now it's an obvious bug that needs to be fixed. Vegas is increasing compatibility with video formats not reducing.

However, whatever the case may be, I’ve been downloading this type of video for 9 years and have used Vegas to edit it and have produced high quality work in the post production work using Vegas Pro. Thank you again for your reply!

Sincerely,
Debbie W.

Your video is recorded in x264, very common, the free video editor that comes with Windows10 plays it fine, and so did Vegas until now it's an obvious bug that needs to be fixed. Vegas is increasing compatibility with video formats not reducing.

@Former user - Thank you so much for your response, your help, and your support! It is greatly appreciated!

Thanks @Debbie-Whitmer for providing the sample as it is. I have downloaded it and also forwarded to developers for further checking. Please keep it for a while so the developers can also download the sample as well.

I have checked the mediainfo:

General
Complete name                            : E:\VEGAS Pro Experiments\20241104 Debby Whitmer MP4 pixellation issue\VEGAS-PRO-22-TEST-AT-DEFAULT-SETTINGS-AND-PIXILATION-PROBLEMS\VEGAS-PRO-22-UPLOADED-FOR-TESTING-PIXELATED-PROBLEM-WITH-DEFAULT-SETTINGS.mp4
Format                                   : MPEG-4
Format profile                           : Base Media
Codec ID                                 : isom (isom/iso2/avc1/mp41)
File size                                : 283 MiB
Duration                                 : 59 min 23 s
Overall bit rate                         : 666 kb/s
Frame rate                               : 30.000 FPS
Writing application                      : Lavf59.27.100

Video
ID                                       : 1
Format                                   : AVC
Format/Info                              : Advanced Video Codec
Format profile                           : Main@L3.1
Format settings                          : CABAC / 3 Ref Frames
Format settings, CABAC                   : Yes
Format settings, Reference frames        : 3 frames
Codec ID                                 : avc1
Codec ID/Info                            : Advanced Video Coding
Duration                                 : 59 min 23 s
Bit rate                                 : 594 kb/s
Width                                    : 1 280 pixels
Height                                   : 720 pixels
Display aspect ratio                     : 16:9
Frame rate mode                          : Variable
Frame rate                               : 30.000 FPS
Minimum frame rate                       : 29.412 FPS
Maximum frame rate                       : 30.303 FPS
Color space                              : YUV
Chroma subsampling                       : 4:2:0
Bit depth                                : 8 bits
Scan type                                : Progressive
Bits/(Pixel*Frame)                       : 0.021
Stream size                              : 252 MiB (89%)
Writing library                          : x264 core 157
Encoding settings                        : cabac=1 / ref=1 / deblock=1:-1:-1 / analyse=0x1:0x111 / me=hex / subme=2 / psy=1 / psy_rd=1.00:0.20 / mixed_ref=0 / me_range=16 / chroma_me=1 / trellis=0 / 8x8dct=0 / cqm=0 / deadzone=21,11 / fast_pskip=1 / chroma_qp_offset=0 / threads=8 / lookahead_threads=2 / sliced_threads=0 / nr=0 / decimate=0 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=1 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=1 / keyint=60 / keyint_min=31 / scenecut=0 / intra_refresh=0 / rc_lookahead=20 / rc=crf / mbtree=1 / crf=27.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / vbv_maxrate=2000 / vbv_bufsize=4000 / crf_max=0.0 / nal_hrd=none / filler=0 / ip_ratio=1.40 / aq=1:1.30
Color range                              : Limited
Color primaries                          : BT.709
Transfer characteristics                 : BT.709
Codec configuration box                  : avcC

Audio
ID                                       : 2
Format                                   : AAC LC SBR
Format/Info                              : Advanced Audio Codec Low Complexity with Spectral Band Replication
Commercial name                          : HE-AAC
Format settings                          : NBC
Codec ID                                 : mp4a-40-5
Duration                                 : 59 min 23 s
Bit rate mode                            : Constant
Bit rate                                 : 64.0 kb/s
Channel(s)                               : 2 channels
Channel layout                           : L R
Sampling rate                            : 48.0 kHz
Frame rate                               : 23.438 FPS (2048 SPF)
Compression mode                         : Lossy
Stream size                              : 27.2 MiB (10%)
Default                                  : Yes
Alternate group                          : 1

Quick look, this is a highly compressed MP4 and also has Variable Frame Rate. I have opened the project and confirmed of several pixellations occured, along with random black frames and green frames.

I assume the new decoder mxcompoundplug.dll used to read MP4 might be challenged, but better the developers do further analysis.

@set - @RogerS - Just letting you know that I downloaded MediaInfo from the Microsoft store. I also watched a video on YouTube in how to operate it. Once I saw how it was demonstration, I tried it and it is easy to use. Once MediaInfo has access to the video file in question, it instantly brings up the internal coding information within that video file and then I can just copy and paste the information in here. This MediaInfo is new to me and I initially didn't know how to use it. But now I do! Thanks again for all your help!

Debbie W.

Glad you see it really isn't difficult- some key things to look for is AVC vs HEVC, 8-bit or 10-bit and variable framerate vs constant framerate. That will give you some idea of what you're dealing with.

Glad you see it really isn't difficult- some key things to look for is AVC vs HEVC, 8-bit or 10-bit and variable framerate vs constant framerate. That will give you some idea of what you're dealing with.

@RogerS - One more thing you may be interesting in knowing. I found out how to get Vegas Pro 22 to render really fast!  If you recall, I had the pixelation, black frame, flickering and green screen problems in just playing the video inside of Vegas Pro 22 with its default settings and you suggested that I go into Options/Preferences/File I/O and turn OFF the “Hardware Decode To Use” and to checkmark “Enable legacy AVC decoding” which I did and it remarkably took away all my problems just like that!  Thank you so much!

Now it came time to render and I told you with the “Hardware Decode To Use” turned OFF, it rendered but it was rendering much slower compared to Vegas Pro 20 which renders super fast.  I went ahead and took my Vegas Pro 20 settings and put them into Vegas Pro 22 (not that many changes).  But here’s the thing, I do not understand WHY this works after you told me to turn OFF the “Hardware Decode To Use” section but the following does indeed work for me.  After I’m through editing and I get ready to render, all I have to do is TURN BACK ON the “Hardware Decode To Use” reflecting my NVIDIA Geforce RTX 3070, and it renders SUPER FAST!  It’s only a few minutes slower than Vegas Pro 20.  Vegas Pro 20 will render my approximately 1 hour radio broadcast, including all the added elements for post production in 15 minutes!  Testing the same thing with Vegas Pro 22, it will render in 20 minutes.  A bit slower but I can live with that.  But it's still fast. When you look at the preview window while it’s rendering, the radio broadcaster is moving in super fast motion and that’s what I want to see!   So, there you have it!    

Debbie W. 

VEGAS Pro 22 and 20 are very different so you can't directly compare the settings.

The advice you asked about was for 22. "enable legacy AVC decoding" in 22 means using the regular decoder that worked with 20, which normally works fine with the hardware decoder enabled. This decoder had 5 years of testing by the time of 20 so was fairly mature though had limitations. The new decoder you are using in 22 was only introduced this spring and still has issues with certain file types and GPUs.Turning off hardware decoding is a workaround that avoids glitches but kills performance.

Really we want to get to a point where you can us the new decoder (not legacy) with hardware decoding in 22 and not have to change settings based on whatever footage we are using at the moment. Your testing is good to find the best settings this type of footage though it may not hold true if you use different footage tomorrow (from a phone, cameras, etc.)

VEGAS Pro 22 and 20 are very different so you can't directly compare the settings.

The advice you asked about was for 22. "enable legacy AVC decoding" in 22 means using the regular decoder that worked with 20, which normally works fine with the hardware decoder enabled. This decoder had 5 years of testing by the time of 20 so was fairly mature though had limitations. The new decoder you are using in 22 was only introduced this spring and still has issues with certain file types and GPUs.Turning off hardware decoding is a workaround that avoids glitches but kills performance.

Really we want to get to a point where you can us the new decoder (not legacy) with hardware decoding in 22 and not have to change settings based on whatever footage we are using at the moment. Your testing is good to find the best settings this type of footage though it may not hold true if you use different footage tomorrow (from a phone, cameras, etc.)

@RogerS - I understand. Thx! You've been a great help!

Debbie W.

 

So when you say, “…the footage is not from a real camera…”, that statement is perplexing to me. Of course the footage is from a real camera. The footage came from a MEVO camera. I do not understand why you said 
 

The point is, that this is a workflow that has the potential to bring you in troubles. Driven by two aspects: the codec generated by this MEVO camera may not be optimised for editing. And what facebook does again with that codec is also not so clear. Seems to be recompressed very likely. Fact is: you end up with a highly compressed footage, one hour compressed to 250 MB. The reason to do that is quite clear for facebook - that saved a lot of bandwidth (and costs) for the company facebook.

But you wish to edit the footage, as I understood after downloading it from facebook again. That gives you a very very limited quality only.

Maybe you do not care about that, since you have done that for many years. But to expect that a video editor like Vegas can handle that properly - well, maybe again in the future, if the development team addresses this issue. What is there decision only.

But you should be aware of that limitation in terms of quality. Probably, I would record to a codec that is less compressed and more suitable to be edited. And upload the edited footage in a better quality. Up to you anyway.

By the way, I use Vegas since Vegas Pro 4.

So when you say, “…the footage is not from a real camera…”, that statement is perplexing to me. Of course the footage is from a real camera. The footage came from a MEVO camera. I do not understand why you said 
 

The point is, that this is a workflow that has the potential to bring you in troubles. Driven by two aspects: the codec generated by this MEVO camera may not be optimised for editing. And what facebook does again with that codec is also not so clear. Seems to be recompressed very likely. Fact is: you end up with a highly compressed footage, one hour compressed to 250 MB. The reason to do that is quite clear for facebook - that saved a lot of bandwidth (and costs) for the company facebook.

But you wish to edit the footage, as I understood after downloading it from facebook again. That gives you a very very limited quality only.

Maybe you do not care about that, since you have done that for many years. But to expect that a video editor like Vegas can handle that properly - well, maybe again in the future, if the development team addresses this issue. What is there decision only.

But you should be aware of that limitation in terms of quality. Probably, I would record to a codec that is less compressed and more suitable to be edited. And upload the edited footage in a better quality. Up to you anyway.

By the way, I use Vegas since Vegas Pro 4.

@Wolfgang S. - Thank you for your response. You have a great day!

I'm using the same version and build and am also experiencing the pixelating issue at random points in the video at the OP reported. My footage is the same footage I've been using for years, AVCHD from my Canon XA10. The corruption is not in the original footage, it's only seen on the Vegas timeline, and it carries over to the final render. Is there any update on a fix for this issue? I skimmed through the thread and it appears there was a workaround which I guess I'll have to try if there isn't a proper fix?

Update: I checked "Enable Legacy AVC Decoding" and it removed the pixelation I was observing in one spot, but not others, i.e. that option doesn't work around the problem after all.

2nd Update: After reading some more in another thread, I also turned off hardware decoding altogether in that same preference window and it appears to get rid of the pixelation issue from what I can see. I hope there will be a fix for this.....

I'm using the same version and build and am also experiencing the pixelating issue at random points in the video at the OP reported. My footage is the same footage I've been using for years, AVCHD from my Canon XA10. The corruption is not in the original footage, it's only seen on the Vegas timeline, and it carries over to the final render. Is there any update on a fix for this issue? I skimmed through the thread and it appears there was a workaround which I guess I'll have to try if there isn't a proper fix?

Update: I checked "Enable Legacy AVC Decoding" and it removed the pixelation I was observing in one spot, but not others, i.e. that option doesn't work around the problem after all.

2nd Update: After reading some more in another thread, I also turned off hardware decoding altogether in that same preference window and it appears to get rid of the pixelation issue from what I can see. I hope there will be a fix for this.....

12-15-2024 - Hi @MikeLV - Exactly. You did exactly what I originally did by changing those preferences and it works and it removes the pixelating at random points. However, when I go to see if there are any updates for Vegas Pro 22 Build 194 by selecting HELP>CHECK FOR SOFTWARE UPDATES, "No updates were found" so there have been no updates since this original problem. Like you, I'm still waiting for any updates for Vegas Pro 22 Build 194. I'm glad the temporary fix worked for you. Have a great day!

There are no updates to VP 22.194 at this time. You can also see the latest build in the news forum here.

In general anyone reporting issues with specific media and the new (non-legacy) MxCompound decoder please consider uploading a sample for testing and to speed development in VEGAS.

I think my video files are too big to upload a sample. As I mentioned, they're just normal AVCHD in the highest quality that my Canon XA10 can produce. There wasn't a problem with the random spots of corruption in Vegas until this current version though.

@MikeLVDo you still own this camera? Can you shoot 10 seconds out the window? If you need a place to upload it to I can make a link available. We really need to be able to replicate this to get it fixed.