Bad Pixelation happening in Vegas Pro 22 (build 194)

Comments

set wrote on 1/25/2025, 6:08 AM

Let us know your experience in b239 @Debbie-Whitmer

Setiawan Kartawidjaja
Bandung, West Java, Indonesia (UTC+7 Time Area)

Personal FB | Personal IG | Personal YT Channel
Chungs Video FB | Chungs Video IG | Chungs Video YT Channel
Personal Portfolios YouTube Playlist
Pond5 page: My Stock Footage of Bandung city

 

System 5-2021:
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHz
Video Card1: Intel UHD Graphics 630 (Driver 31.0.101.2127 (Feb 1 2024 Release date))
Video Card2: NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 (Driver Version 551.23 Studio Driver (Jan 24 2024 Release Date))
RAM: 32.0 GB
OS: Windows 10 Pro Version 22H2 OS Build 19045.3693
Drive OS: SSD 240GB
Drive Working: NVMe 1TB
Drive Storage: 4TB+2TB

 

System 2-2018:
ASUS ROG Strix Hero II GL504GM Gaming Laptop
Processor: Intel(R) Core(TM) i7 8750H CPU @2.20GHz 2.21 GHz
Video Card 1: Intel(R) UHD Graphics 630 (Driver 31.0.101.2111)
Video Card 2: NVIDIA GeForce GTX 1060 6GB GDDR5 VRAM (Driver Version 537.58)
RAM: 16GB
OS: Win11 Home 64-bit Version 22H2 OS Build 22621.2428
Storage: M.2 NVMe PCIe 256GB SSD & 2.5" 5400rpm 1TB SSHD

 

* I don't work for VEGAS Creative Software Team. I'm just Voluntary Moderator in this forum.

Debbie-Whitmer wrote on 1/25/2025, 6:45 AM

Let us know your experience in b239 @Debbie-Whitmer

@set- Hi there! I've just tested a little thus far but before, VegasPro 22 (build 194) used to render slower than Vegas Pro 20 (build 411). But before rendering to Vegas Pro 22 (build 239), I went to Options>Preferences>File I/O and unchecked "Enable legacy AVC decoding" because that was a temporary work around for me before the update. After the update to Vegas Pro (build 239), it now renders as fast as VegasPro 20! I rendered a 49 minutes, 34 seconds Radio Broadcast that I do post production on and it rendered in 15 minutes. That's a good thing! 👍

Last changed by Debbie-Whitmer on 1/25/2025, 6:49 AM, changed a total of 1 times.

My name is Debbie Whitmer. Here are my computer specs:
Processor: AMD Ryzen 9 3900X 12-Core Processor – 3.80 GHz
Installed RAM: 64.0 GB
System Type: 64-bit Operating System, x64-based processor
Pen and touch: No pen or touch input is available
Video Card: NVIDIA GeForce RTX 3070 version 565.90 (Studio Driver)
Operating System: Windows 10 Pro Version 22H2, OS Build 19045.5011 --AND-- Windows 11 Pro, Version 23H2, OS Build 22631.4317

Debbie-Whitmer wrote on 1/25/2025, 8:06 AM

A list of the Build 239 Improvements and Bug fixes are in this thread https://www.vegascreativesoftware.info/us/forum/update-vegas-pro-22-build-239--148287/


@EricLNZ - Thank you so much for posting this information! 👍

My name is Debbie Whitmer. Here are my computer specs:
Processor: AMD Ryzen 9 3900X 12-Core Processor – 3.80 GHz
Installed RAM: 64.0 GB
System Type: 64-bit Operating System, x64-based processor
Pen and touch: No pen or touch input is available
Video Card: NVIDIA GeForce RTX 3070 version 565.90 (Studio Driver)
Operating System: Windows 10 Pro Version 22H2, OS Build 19045.5011 --AND-- Windows 11 Pro, Version 23H2, OS Build 22631.4317

MikeLV wrote on 1/25/2025, 12:03 PM

Thank you for the news. I haven't updated to the new build yet, but in reading the change log, the only thing I see that mentions AVC (which I presume is the same as AVCHD?) footage is:

  • The Pixel Aspect Ratio is now properly applied for all AVC media

Is that the fix for the issue @Debbie-Whitmer and I were having where the video would distort in random places?

Debbie-Whitmer wrote on 1/25/2025, 4:20 PM

Thank you for the news. I haven't updated to the new build yet, but in reading the change log, the only thing I see that mentions AVC (which I presume is the same as AVCHD?) footage is:

  • The Pixel Aspect Ratio is now properly applied for all AVC media

Is that the fix for the issue @Debbie-Whitmer and I were having where the video would distort in random places?

Hello @MikeLV and eveyone. I hope you are all having a good day! I did some further testing regarding this pixelation issue. Just letting you all know in using Vegas Pro 22 (build 239) I did NOT notice any pixelation YET while editing and after rendering the same video that I originally posted under this heading having pixelation problems.  However, in using all the default settings with Vegas Pro 22 (Build 239), I DID have some jerking, flickering and some black screens in various places and then it would come back to normal again which, of course, is unacceptable.  However, to overcome this issue, I had to go to Options>Preferences>File I/O and I MUST check mark “Enable legacy AVC coding.”  Both “Enable legacy AVC decoding” -AND- “Enable experimental HEVC decoding” are now both check marked on this page. 

Since I can overcome this jerking,flickering and black screen obstacles with the aforementioned remedy, I will do that as it gives me a finished rendered video without errors.

 

My name is Debbie Whitmer. Here are my computer specs:
Processor: AMD Ryzen 9 3900X 12-Core Processor – 3.80 GHz
Installed RAM: 64.0 GB
System Type: 64-bit Operating System, x64-based processor
Pen and touch: No pen or touch input is available
Video Card: NVIDIA GeForce RTX 3070 version 565.90 (Studio Driver)
Operating System: Windows 10 Pro Version 22H2, OS Build 19045.5011 --AND-- Windows 11 Pro, Version 23H2, OS Build 22631.4317

MikeLV wrote on 1/25/2025, 4:55 PM

@Debbie-Whitmer, I don't believe that the HEVC setting should have any effect on the previous issue as that's an entirely different format than AVCHD. But from what you're describing it sounds like the previous problem still exists, but it has morphed into some other manifestation (jerking, flickering and black screens). Given your comments, would you recommend against updating to Build 239 and continue to use the legacy AVC option? Or is it still a good idea to update?

Debbie-Whitmer wrote on 1/25/2025, 5:32 PM

@Debbie-Whitmer, I don't believe that the HEVC setting should have any effect on the previous issue as that's an entirely different format than AVCHD. But from what you're describing it sounds like the previous problem still exists, but it has morphed into some other manifestation (jerking, flickering and black screens). Given your comments, would you recommend against updating to Build 239 and continue to use the legacy AVC option? Or is it still a good idea to update?

 

@MikeLV Yes, you are correct; I was just letting everyone know that both HEVC and Legacy AVC coding were both check marked on the File I/O page.

Regarding your question, I think that if more people report having the "jerking, flickering and black screens" issues with the default settings, then Vegas should find a solution for that as that would permanently be inside of a person's video after using Vegas Pro 22 which is unacceptable and unprofessional especially if a company is paying you to do their videos. However, for ME, by going to the "Options>Preferences>File I/O tab" (which was suggested I do this a long time ago as a temporary fix for the pixelation issue) and check marking the "Enable legacy AVC coding", it is a solution which solved all the aforementioned issues.

I was so glad that Vegas finally released Vegas Pro 22 build 239 and while reading the long list of bug fixes, that is always a good thing as a whole but invariably other issues come up. As the old saying goes, "It's always something." LOL! But all in all, I really like Vegas and have been using it since Vegas 8 I think, it's user friendly for the most part and brilliantly made. And everyone has always been so kind and helpful when a problem arises and I have had all my issues that I was having fixed throughout the years.


 

My name is Debbie Whitmer. Here are my computer specs:
Processor: AMD Ryzen 9 3900X 12-Core Processor – 3.80 GHz
Installed RAM: 64.0 GB
System Type: 64-bit Operating System, x64-based processor
Pen and touch: No pen or touch input is available
Video Card: NVIDIA GeForce RTX 3070 version 565.90 (Studio Driver)
Operating System: Windows 10 Pro Version 22H2, OS Build 19045.5011 --AND-- Windows 11 Pro, Version 23H2, OS Build 22631.4317

MikeLV wrote on 1/25/2025, 5:35 PM

@Debbie-Whitmer @set @RogerS So I went ahead and updated, disabled the legacy AVC option, opened one of my videos and started clicking around the timeline. Sure enough the image distortion is still happening as shown by this distorted face. It seems the issue hasn't been addressed in Build 239.

Debbie-Whitmer wrote on 1/25/2025, 5:48 PM

@Debbie-Whitmer @set @RogerS So I went ahead and updated, disabled the legacy AVC option, opened one of my videos and started clicking around the timeline. Sure enough the image distortion is still happening as shown by this distorted face. It seems the issue hasn't been addressed in Build 239.

@MikeLV - Oh no! Oh my! That's the pixelated nightmare picture that no one wants to see! Then this needs to be fixed ASAP! In the interim, please try to enable legacy AVC to see if that helps. It did for me.

 

My name is Debbie Whitmer. Here are my computer specs:
Processor: AMD Ryzen 9 3900X 12-Core Processor – 3.80 GHz
Installed RAM: 64.0 GB
System Type: 64-bit Operating System, x64-based processor
Pen and touch: No pen or touch input is available
Video Card: NVIDIA GeForce RTX 3070 version 565.90 (Studio Driver)
Operating System: Windows 10 Pro Version 22H2, OS Build 19045.5011 --AND-- Windows 11 Pro, Version 23H2, OS Build 22631.4317

Debbie-Whitmer wrote on 1/25/2025, 6:22 PM

@Debbie-Whitmer @set @RogerS So I went ahead and updated, disabled the legacy AVC option, opened one of my videos and started clicking around the timeline. Sure enough the image distortion is still happening as shown by this distorted face. It seems the issue hasn't been addressed in Build 239.

@MikeLV - In using the default settings in Vegas Pro 22 (Build 239) and NOT having legacy AVC check marked, I started tapping around in the video I was testing with and, indeed, I got pixelation as well as you can see and MORE black screens. This needs to be fixed ASAP.



 

My name is Debbie Whitmer. Here are my computer specs:
Processor: AMD Ryzen 9 3900X 12-Core Processor – 3.80 GHz
Installed RAM: 64.0 GB
System Type: 64-bit Operating System, x64-based processor
Pen and touch: No pen or touch input is available
Video Card: NVIDIA GeForce RTX 3070 version 565.90 (Studio Driver)
Operating System: Windows 10 Pro Version 22H2, OS Build 19045.5011 --AND-- Windows 11 Pro, Version 23H2, OS Build 22631.4317

MikeLV wrote on 1/25/2025, 6:37 PM

I guess we can just start a facial disfigured club! 😂 Yeah, the legacy AVC setting does fix it as a workaround, although, I don't know if that setting causes problems elsewhere or not; haven't noticed any.

Debbie-Whitmer wrote on 1/25/2025, 6:43 PM

I guess we can just start a facial disfigured club! 😂 Yeah, the legacy AVC setting does fix it as a workaround, although, I don't know if that setting causes problems elsewhere or not; haven't noticed any.

LOL! to the "facial disfigure club!" I haven't noticed any problems using the legacy AVC setting. But thank you for letting me know that the legacy AVC setting worked for you.

My name is Debbie Whitmer. Here are my computer specs:
Processor: AMD Ryzen 9 3900X 12-Core Processor – 3.80 GHz
Installed RAM: 64.0 GB
System Type: 64-bit Operating System, x64-based processor
Pen and touch: No pen or touch input is available
Video Card: NVIDIA GeForce RTX 3070 version 565.90 (Studio Driver)
Operating System: Windows 10 Pro Version 22H2, OS Build 19045.5011 --AND-- Windows 11 Pro, Version 23H2, OS Build 22631.4317

set wrote on 3/4/2025, 5:10 PM

https://www.vegascreativesoftware.info/us/forum/update-beta-release-vegas-pro-22-beta-build-243-feedback--148571/#ca934526

Retesting this issue in VP22b243

(If you want to report your finding and experiment in the openbeta build 243, please state on that specified thread - not here)

Last changed by set on 3/4/2025, 5:11 PM, changed a total of 1 times.

Setiawan Kartawidjaja
Bandung, West Java, Indonesia (UTC+7 Time Area)

Personal FB | Personal IG | Personal YT Channel
Chungs Video FB | Chungs Video IG | Chungs Video YT Channel
Personal Portfolios YouTube Playlist
Pond5 page: My Stock Footage of Bandung city

 

System 5-2021:
Processor: Intel(R) Core(TM) i7-10700 CPU @ 2.90GHz   2.90 GHz
Video Card1: Intel UHD Graphics 630 (Driver 31.0.101.2127 (Feb 1 2024 Release date))
Video Card2: NVIDIA GeForce RTX 3060 Ti 8GB GDDR6 (Driver Version 551.23 Studio Driver (Jan 24 2024 Release Date))
RAM: 32.0 GB
OS: Windows 10 Pro Version 22H2 OS Build 19045.3693
Drive OS: SSD 240GB
Drive Working: NVMe 1TB
Drive Storage: 4TB+2TB

 

System 2-2018:
ASUS ROG Strix Hero II GL504GM Gaming Laptop
Processor: Intel(R) Core(TM) i7 8750H CPU @2.20GHz 2.21 GHz
Video Card 1: Intel(R) UHD Graphics 630 (Driver 31.0.101.2111)
Video Card 2: NVIDIA GeForce GTX 1060 6GB GDDR5 VRAM (Driver Version 537.58)
RAM: 16GB
OS: Win11 Home 64-bit Version 22H2 OS Build 22621.2428
Storage: M.2 NVMe PCIe 256GB SSD & 2.5" 5400rpm 1TB SSHD

 

* I don't work for VEGAS Creative Software Team. I'm just Voluntary Moderator in this forum.

RedRob-CandlelightProdctns wrote on 4/26/2025, 10:00 PM

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 experienced the same with my XA11 footage today, and progressed the same as you -- first enabling Legacy, then disabling hardware decoding all together to get it working in timeline and render.

 

Vegas 21.300

My PC (for finishing):

Cyperpower PC Intel Core i7-7700K CPU @ 4.2GHz, 64GB mem @ 2133MHz RAM, AMD Radeon RX470 (4GB dedicated) with driver recommended by Vegas Updater (reports as 30.0.15021.11005 dated 4/28/22), and Intel HD Graphics 630 driver version 31.0.101.2112 dated 7/21/22 w/16GB shared memory. Windows 10 Pro 64bit version 10.0.19045 Build 19045.

My main editing laptop:

Dell G15 Special Edition 5521, Bios 1.12 9/13/22, Windows 11 22H2 (10.0.22621)

12th Gen Intel Core i7-12700H (14 cores, 20 logical processors), 32 GB DDR5 4800MHz RAM, Intel Iris Xe Graphics, NVIDIA GeForce RTX 3070 Ti Laptop GPU w/8GB GDDR6 RAM, Realtek Audio