Bad Pixelation happening in Vegas Pro 22 (build 194)

Debbie-Whitmer wrote on 11/3/2024, 2:36 AM

11-3-2024 - I need help please! I’m having a problem with Vegas Pro 22 (build 194) I just purchased yesterday; I installed Vegas Pro 22 and the "Vegas Deep Learning Models" that it came with. I’m currently using Vegas Pro 20 (build 411) and there is absolutely nothing wrong with Vegas Pro 20 and it works beautifully. I have both Windows 10 Pro and 11 Pro but I’m using Windows 10 Pro right now. (As a side note, I do post production for a radio station that streams LIVE for its broadcast and the broadcast can be between 1 to 2 hours long.) But now, in using Vegas Pro 22 (build 194), WHILE EDITING, Vegas Pro 22 intermittently causes the man’s face who does the broadcast to be pixelated very badly and then goes back to normal. And then, sometimes right after that, I will get a flash of a solid black screen and then goes back to normal again. And sometimes that black screen will flicker. And after I render it to test it out, the pixelation and black screen and some flickering remains. The raw video I’m using for post production after I downloaded it from LIVE streaming is perfect and there’s nothing wrong with it so I know that Vegas Pro 22 is causing all this pixelation/black screen situation. This is totally unacceptable. Vegas Pro 22 does this pixelation in its default settings. I’ve tested and tested and even used my Vegas Pro 20 settings and put them into my Vegas Pro 22 settings (really not that many changes) and nothing works for me. My computer hardware and Operating System (OS) is in my profile. I do have two (2) snapshots displaying this problem and I can upload them here if I can find where to do that. If you know what’s causing all of these aforementioned problems or what settings I need to change to stop all of pixelation and black screen and flickering from happening, PLEASE let me know ASAP. If I cannot get this fixed, I’m going to have to return Vegas Pro 22 for a refund. Thank you so much for your immediate attention. I look forward to your replies.

Sincerely,
Debbie Whitmer

Comments

pierre-k wrote on 11/3/2024, 2:56 AM

are your files in 4k? Do the artefacts look the same as in this video?

https://www.vegascreativesoftware.info/us/forum/vp21-b300-and-big-problem-with-mxf--145196/?page=5#ca921387

set wrote on 11/3/2024, 4:55 AM

Mediainfo of the source media you are working with?

RogerS wrote on 11/3/2024, 6:45 AM

@Debbie-Whitmer If you can provide MediaInfo and a sample of the same kind of footage you are using (a capture done in the same way) it would help with troubleshooting. VEGAS Pro has a new media decoder that is faster and more stable than what 20 had but it has trouble with some file types. With your help we can get it fixed.

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

A workaround for now could be to enable legacy AVC decoding in preferences/ file io (assuming the source is AVC) or setting hardware decoding to none in preferences/ file io.

Debbie-Whitmer wrote on 11/3/2024, 8:09 AM

are your files in 4k? Do the artefacts look the same as in this video?

https://www.vegascreativesoftware.info/us/forum/vp21-b300-and-big-problem-with-mxf--145196/?page=5#ca921387

@pierre-k - Hello! Thank you for responding! No, the output of the LIVE Streaming videos that the radio broadcaster does is only 1280p x 720p. When I download that raw video from Facebook and then do post production on it, my final rendering is going to be 1280p x 720p in order to conserve disk space on my hard drive as I've been doing this broadcast for 9 years now. The highest resolution that I have ever done is 1920p x 1080p on my own personal videos that I create by scratch. But in any event, I did upload two screen shots of what this pixelation looks like and it does not look at all like the example you gave me. Please see the uploaded screenshots.

Debbie-Whitmer wrote on 11/3/2024, 8:27 AM

Mediainfo of the source media you are working with?

@set - Hi there. Thank you so much for responding! The "source media" that is used is the broadcaster streams LIVE on Facebook and uses a MEVO Camera. But he's been using it for years and I've been doing the radio broadcast for 9 years. The radio broadcaster initially used his iPhone to record but later changed to the MEVO camera; so I have done post production using both the iPhone and MEVO camera as the source.

So first, after I purchased Vegas Pro 22, I did a test and I took one of his recent broadcasts that had already been completed in Vegas Pro 20 without any problems at all, and launched the Vegas Pro 20 icon using Vegas Pro 22 icon so I could see if it would render okay; I always do this when I get a new Vegas Pro upgrade. After I rendered it, I reviewed it and that's when I noticed the pixelation. Then I launched only Vegas Pro 22 and ONLY dragged the raw video into Pro 22 just to play it inside of the Pro 22. And the result is by just watching it play inside of Vegas Pro 22 there's pixelation including these black screens and flickering and then after rendering, the same problem exists in the final output. The only problem I'm having is the results from Vegas Pro 22!

Sincerely,
Debbie W.

Debbie-Whitmer wrote on 11/3/2024, 9:56 AM

@Debbie-Whitmer If you can provide MediaInfo and a sample of the same kind of footage you are using (a capture done in the same way) it would help with troubleshooting. VEGAS Pro has a new media decoder that is faster and more stable than what 20 had but it has trouble with some file types. With your help we can get it fixed.

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

A workaround for now could be to enable legacy AVC decoding in preferences/ file io (assuming the source is AVC) or setting hardware decoding to none in preferences/ file io.

@RogerS I’m so sorry but I’m not familiar with the screen shot results with the link you provided with providing these kinds of media info’s using “MediaArea.net/MediaInfo". When I give you a screen shot, I just use my “Print Screen” key on my keyboard which copies the screen into memory and then I used Adobe Photoshop to paste it in and then output it to a .jpg picture to upload it here.

I’m trying to answer your questions as best I can; the technical terminology can be a bit confusing at times.

When I render, I only output to a .MP4 file upon completion.

I went to the Options/Preferences and, by default, only “Enable experimental HEVC decoding” is check marked. But “Enable legacy AVC decoding” is not marked. So, therefore, I will go ahead and checkmark that to see if it helps.

I do see the File I/O tab in preferences and my Hardware Decoder to use is currently set to “Auto NVIDIA GeForce RTX 3070” which is my graphics card. So, when you said set it to “none” the option I have says “Off” so I’ll go ahead and set the Hardware Decoder to “Off”.

And when I get ready to render, I always use:

FORMATS: MAGIX AVC/AAC MP4

TEMPLETS: “Internet HD 720p 29.97 fps” OR “Internet HD 720p 29.97 fps (NVENC)”.

I currently have the above Template set to “Internet HD 720p 29.97 fps”

So, I will go ahead checkmark the “Enable legacy AVC decoding” that you recommended above and also change the Hardware Decoder to “Off” to see if that would help. Or maybe I should try only setting one option at a time before I do both at the same time? I’ll try one at a time and then both at the same time to test it.

I will go ahead and try to upload a video clip of the troubled pixelated area I’m having, before making any new changes, so you can see the pixelation.

I so appreciate everyone’s help!! I work best with just telling me which menus to go to inside of Vegas and which thing to change. Thank you and I’ll be back to share the results a little bit later; perhaps in a few hours. Please continue to “hang with me” for the final results. But I do have to leave right now. Thanks again!

P.S. Oh, I tried to upload my .MP4 clip so you could see the troubled area and it says "Error" Don't know why. Hmmm.

Debbie W.

RogerS wrote on 11/3/2024, 10:04 AM

You don't need to take a screenshot. Open Mediainfo, copy the text in the info tab and paste it back in here.

"Open your file with it, and switch it to text view ("View" > "Text")
Highlight all the text in the window, copy it and paste it in your forum post."

Or I'll do it for you if you upload the original clip to Dropbox or Google Drive or anywhere else I can download it from (not the forum upload feature).

You should first figure out if the media is AVC or HEVC which VEGAS can tell you if you look at its properties. Based on that you can check the matching box in preferences file io and report back if any work. Turning off the hardware decoding is a next step (though really a last resort as it will hurt performance).

The render format doesn't matter as this error is happening before the render stage.

Debbie-Whitmer wrote on 11/3/2024, 10:08 AM

You don't need to take a screenshot. Open Mediainfo, copy the text in the info tab and paste it back in here.

"Open your file with it, and switch it to text view ("View" > "Text")
Highlight all the text in the window, copy it and paste it in your forum post."

Or I'll do it for you if you upload the original clip to Dropbox or Google Drive or anywhere else I can download it from (not the forum upload feature).

You should first figure out if the media is AVC or HEVC which VEGAS can tell you if you look at its properties. Based on that you can check the matching box in preferences file io and report back if any work. Turning off the hardware decoding is a next step (though really a last resort as it will hurt performance).

The render format doesn't matter as this error is happening before the render stage.

@RogerS - Did you see my above message? I was able to finally upload a video clip for you and gave you a lot of information there. But for right now, I need to go. People are waiting on me. Thank you!

Wolfgang S. wrote on 11/3/2024, 10:27 AM

You misunderstood the request. An original file is required, that can be downloaded. No snapshoots, no uploaded video. But an uploaded original file to a webspace, that can be downloaded and analysed.

RogerS wrote on 11/3/2024, 10:43 AM

I don't need a screen capture of the glitches but as Wolfgang states the original file uploaded to a file sharing service, not this forum's upload video feature. Whenever you have time is fine.

Debbie-Whitmer wrote on 11/3/2024, 11:26 AM

I don't need a screen capture of the glitches but as Wolfgang states the original file uploaded to a file sharing service, not this forum's upload video feature. Whenever you have time is fine.

@RogerS - Hi. Here is the 15 second video clip that I uploaded to Dropbox to be downloaded and analyzed of the pixelation inside of Vegas Pro 22. OR were you wanting the entire raw video which is almost 1 hour long or is the 15 second video RENDERED with Vegas Pro 22 sufficient?

In the meantime, I will change those settings inside of Vegas Pro 22 that you recommended and test it to see how that works:

https://www.dropbox.com/scl/fi/bcqdw4uhue58l06eg1fum/VEGAS-22-VIDEO-CLIP-TESTING-RENDERED.mp4?rlkey=skehj5ojuft9o3z9k87vtp1ww&st=7ibd2tmq&dl=0

Thank you!

mark-y wrote on 11/3/2024, 12:33 PM

@Debbie-Whitmer

@set asked for the MediaInfo Properties for you Source Video; a link to your rendered file isn't helpful without that report. MediaInfo is a specific application you would download and use according to the exact directions provided in this Vegas Help Article. Thank you for posting.

Also, uploading videos to the Vegas player is not very helpful, because they have been transcoded and offer no useful information other than visual playback.

Set has been here for well over a decade, and his reasons for requesting this specific data are the way to go to get help from your forum peers.

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

Wolfgang S. wrote on 11/3/2024, 1:55 PM

I don't need a screen capture of the glitches but as Wolfgang states the original file uploaded to a file sharing service, not this forum's upload video feature. Whenever you have time is fine.

@RogerS - Hi. Here is the 15 second video clip that I uploaded to Dropbox to be downloaded and analyzed of the pixelation inside of Vegas Pro 22. OR were you wanting the entire raw video which is almost 1 hour long or is the 15 second video RENDERED with Vegas Pro 22 sufficient?

In the meantime, I will change those settings inside of Vegas Pro 22 that you recommended and test it to see how that works:

https://www.dropbox.com/scl/fi/bcqdw4uhue58l06eg1fum/VEGAS-22-VIDEO-CLIP-TESTING-RENDERED.mp4?rlkey=skehj5ojuft9o3z9k87vtp1ww&st=7ibd2tmq&dl=0

Thank you!

Unfortunately, that is still not what was requested. This seems ot be the rendered file out of Vegas. BUT what we need are the original files that you use in Vegas, to generate this output.

Reason: what should we do with the rendered file? We have to try to repro that - means: we need the original footage, but not a rendered product.

And it should not be a video of one hour. Is there nothing shorter available, that shows that issue, if it is so significant?

Wolfgang S. wrote on 11/3/2024, 1:59 PM

And: we need your

project settings,
your settings for the gpu acceleration and
i/o preferences, and
your render settings

Here snapshoots from the settings would be great.

Debbie-Whitmer wrote on 11/3/2024, 2:40 PM

@Debbie-Whitmer If you can provide MediaInfo and a sample of the same kind of footage you are using (a capture done in the same way) it would help with troubleshooting. VEGAS Pro has a new media decoder that is faster and more stable than what 20 had but it has trouble with some file types. With your help we can get it fixed.

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

A workaround for now could be to enable legacy AVC decoding in preferences/ file io (assuming the source is AVC) or setting hardware decoding to none in preferences/ file io.

@RogerS - Guess what?!? It worked!! Just making those two changes that you suggested made all the pixelation, sudden dark screens, and occasional flickering all come to a stop!! When I dragged the raw video inside of Vegas Pro 22 just to play it, I marked where the troubled places were so I could go to it quickly, and it was no longer pixelated!! That was amazing!!

Now, I did several tests using Vegas Pro 22 with my post production that was already made in Vegas Pro 20. I just opened up the Vegas Pro 20 icon in that completed project folder and opened it with Vegas Pro 22 instead.

The first test was done with the “Enable legacy AVC decoding” CHECKED, as you suggested, but left the “Enable experimental HEVC docoding ON which was already checked. With all the other elements I added to the post production, Vegas Pro 22 rendered the almost hour-long video post production in 24 minutes.

Then the second test, I left the “Enable legacy AVC decoding” CHECKED, as you suggested, but this time I UNCHECKED the “Enable experimental HEVC docoding”. Then I rendered it and it rendered in 23 minutes. So, doing it this way was about 1 minute faster in rendering it.

However, just to let you know, ALL of my post productions that I do in which the raw video is approximately 1 hour long along with all of the elements I add to it for post production, Vegas Pro 20 renders it in 15 minutes! It would be so nice if Vegas Pro 22 would speed up a little bit faster in the rendering process because Vegas Pro 20 right now renders faster for me. I’m just not sure how to make Vegas Pro 22 render faster at this point.

But in any event, God answered my prayer today because I asked Him first to help me with this and then He answered it through you!!

And thank you all for your help who replied with your help and kindness!! Thank you so much!

Sincerely,
Debbie W.

Debbie-Whitmer wrote on 11/3/2024, 2:44 PM

And: we need your

project settings,

your settings for the gpu acceleration and

i/o preferences, and

your render settings

Here snapshoots from the settings would be great.

Hello @Wolfgang S. - Thank you for your response. If you saw my latest post to @RogerS , @RogerS' solution fixed it with such an easy fix for which I am grateful! Thank you for your help!

Debbie W.

Debbie-Whitmer wrote on 11/3/2024, 2:52 PM

@Debbie-Whitmer

@set asked for the MediaInfo Properties for you Source Video; a link to your rendered file isn't helpful without that report. MediaInfo is a specific application you would download and use according to the exact directions provided in this Vegas Help Article. Thank you for posting.

Also, uploading videos to the Vegas player is not very helpful, because they have been transcoded and offer no useful information other than visual playback.

Set has been here for well over a decade, and his reasons for requesting this specific data are the way to go to get help from your forum peers.

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

@mark-y - Hello! I do not know how to use MediaInfo at the point, and I was busy testing but my problem has already been resolved. @RogerS gave me the solution with such an easy fix and I responded back to @RogerS in my post to him with all the details I did during my testing of what he recommended. Take a look at if if you wish. My problem has now been solved. Thank you for your help and suggestion!

Wolfgang S. wrote on 11/3/2024, 2:55 PM

And: we need your

project settings,

your settings for the gpu acceleration and

i/o preferences, and

your render settings

Here snapshoots from the settings would be great.

Hello @Wolfgang S. - Thank you for your response. If you saw my latest post to @RogerS , @RogerS' solution fixed it with such an easy fix for which I am grateful! Thank you for your help!

Debbie W.

Unfortunately, this is not a fix really. It may be a workaround (with some significant disadvantages) at the moment, but not a fix in the actual architecture of Vegas.

3POINT wrote on 11/3/2024, 2:59 PM

@Debbie-Whitmer For (much) faster high quality renders, try Voukoder for Vegas and choose a NVENC supported x264 or x265 rendertemplate.

Debbie-Whitmer wrote on 11/3/2024, 3:01 PM

@Debbie-Whitmer For (much) faster high quality renders, try Voukoder for Vegas and choose a NVENC supported x264 or x265 rendertemplate.

Thank you @3POINT !!

Debbie W.

Debbie-Whitmer wrote on 11/3/2024, 5:02 PM

And: we need your

project settings,

your settings for the gpu acceleration and

i/o preferences, and

your render settings

Here snapshoots from the settings would be great.

Hello @Wolfgang S. - Thank you for your response. If you saw my latest post to @RogerS , @RogerS' solution fixed it with such an easy fix for which I am grateful! Thank you for your help!

Debbie W.

Unfortunately, this is not a fix really. It may be a workaround (with some significant disadvantages) at the moment, but not a fix in the actual architecture of Vegas.

@RogerS, @Wolfgang S., @mark-y, @set, @mark-y

11-3-2024 - Okay, I uploaded a .ZIP file of the files in this discussion to Dropbox regarding the Pixelation, Black Screen and flickering problems I was having at your Vegas’ team request. The original .MP4 file is also included in the .ZIP file, however, I spliced it up in pieces where the problems are so you can see directly inside of Vegas Pro 22 and the small pieces are the only thing inside of Vegas Pro 22. There is a readme file included. This is the best I can do with what I know how to do. After sufficient time has passed for an analysis, I will be deleting this .ZIP file. The link is below. Thank you!

https://www.dropbox.com/scl/fi/iz7sy421ct6nq616a6dr9/VEGAS-PRO-22-TEST-WITH-DEFAULT-SETTINGS-AND-PIXILATION-PROBLEMS.zip?rlkey=tizlrmyh0vvih2yimzz985h03&st=43zq5xkm&dl=0

Former user wrote on 11/3/2024, 5:24 PM

It's very bad

(distortion on motion)

(this frame plays fine in other editors)

Debbie-Whitmer wrote on 11/3/2024, 5:40 PM

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.

set wrote on 11/3/2024, 5:40 PM

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.