Weird issue : video clips "pixelate" after rendering

Timothy-Dhalleine wrote on 8/6/2024, 8:20 AM

Hi everyone,

So I've had this issue for a few years with some clips while editing (especially with some drone videos, all shot in MP4. / 4K). The clips themselves look amazing (FYI I shoot with a DJI Mavic Air 2 for the drone, Nikon Z8 for the camera) and everything looks normal while previewing on Vegas Pro 21, however, after rendering some of these clips pixelate. While this is subtle (you may struggle to notice it on the screenshots, it interferes with the overall quality of the video in a terrible way (note : I am a pro filmmaker, so I need everything to be perfect for my clients).

This is not permanent : after I render, it's like parts of some specific clips go from 4K to 360p in some short sections. If I render the video again, maybe it will be better, maybe it will be worse. It's completely random and mostly happen in drone videos and timelapses.

FYI I render in MAGIX AVC/AAC MP4. | Internet UHD 2160p 59.94fps.

Fingers crossed someone here can help me - thank you!

Best,
Tim

 

 

Comments

3POINT wrote on 8/6/2024, 9:58 AM

 

FYI I render in MAGIX AVC/AAC MP4. | Internet UHD 2160p 59.94fps.

Fingers crossed someone here can help me - thank you!

 

 

Try Voukoder for Vegas for rendering such detailed videos. I never use Magix AVC/HEVC for quality renders.

Howard-Vigorita wrote on 8/6/2024, 12:26 PM

@Timothy-Dhalleine I thought that drone shot hevc. I get the best quality rendering hevc with the Magix Hevc/MainConcept encoder selecting the 10-bit option using cbr with a rate that is the closest match to the bitrate of the footage.

There might also be level mismatches between what you see before and after rendering. Suggest you do a render and display it in a viewer sized to match and positioned along side your Vegas preview screen to verify that imaging looks the same. Your screen shots have allot of low-level material which might be undergoing a range remap somewhere and causing pixelation in a mismatched render. If you need a limited-range render of a Vegas full-range project for YouTube compatibility, make sure your external viewer is set to do a limited-2-full range view transform. Otherwise render full-range projects to full-range in the render preset under the project tab.

Gid wrote on 8/6/2024, 12:31 PM

@Timothy-Dhalleine Hi,you wrote this in one of your previous posts -

Labtop : ASUS ROG Zephyrus G14

AMD Ryzen 9 6900HS with Radeon Graphics | 3.30 GHz

RAM : 16,0 GB

Windows 11.

Vegas Pro 20

Can you click your icon at the top of this page - My Profile & fill in your Signature with this info, it will then always show at the bottom of your comments,

You also posted MediaInfo of a previous file so you have that app. can you share the info of this file.

Vegas Pro 21
Vegas Pro/Post 19
Boris Continuum & Sapphire, 
Silhouette Standalone + Plugin, 
Mocha Pro Standalone + Plugin, 
Boris Optics,
NewBlue TotalFX
Desktop PC Microsoft Windows 10 Pro - 64-Bit
ASUS PRO WS WRX80E-SAGE SE WIFI AMD Motherboard
AMD Ryzen Threadripper PRO 3975WX 3.5GHz 32 Core
Corsair iCUE H150i RGB PRO XT 360mm All-in-One Liquid CPU Cooler
RAM 256GB ( 8x Micron 32GB (1x 32GB) 2666MHz DDR4 RAM )
2x Western Digital Black SN850 2TB M.2-2280 SSD, 7000MB/s Read, 5100MB/s Write
(programs on one, project files on the other)
Graphics MSI GeForce RTX 3090 SUPRIM X 24GB OC GPU
ASUS ROG Thor 1200W Semi-Modular 80+ Platinum PSU 
Fractal Design Define 7 XL Dark TG Case with 3 Fans
Dell SE3223Q 31.5 Inch 4K UHD (3840x2160) Monitor, 60Hz, & an Acer 24" monitor.

At the moment my filming is done with a Samsung Galaxy S23 Ultra 5G & a GoPro11

I've been a Joiner/Carpenter for 40yrs, apprentice trained time served, I don't have an apprentice of my own so to share my knowledge I put videos on YouTube.

YouTube videos - https://www.youtube.com/c/Gidjoiner

Lots of work photos on Facebook - https://www.facebook.com/gid.joiner/photos_albums

3POINT wrote on 8/6/2024, 1:29 PM

@Timothy-Dhalleine I get the best quality rendering hevc with the Magix Hevc/MainConcept encoder selecting the 10-bit option using cbr with a rate that is the closest match to the bitrate of the footage.

The best way to waste bitrates....but sure it will give you best quality...but probably also issues with delivery...

Howard-Vigorita wrote on 8/6/2024, 1:58 PM

Most of what I do is for upload to YouTube these days and no issues there. The hevc format is inherently more compact than avc even though it prefers cbr. If delivering for further editing, ProRes is usually preferred by colorists with low powered gpus but that needs substantially higher bitrates.

mark-y wrote on 8/6/2024, 2:21 PM

...however, after rendering some of these clips pixelate.

Unless this happens every time you play them in exactly the same spot for the same duration, the solution is entirely between your system, your player, and whatever else might be going on like background processes, network / internet traffic, and multitasking.

2160p at 60 fps can be a bit taxing for many viewers for the same reasons, and the modest computer systems the vast majority of viewers will have. 1080 p30 is about the norm for 80% of consumers.

You may have better luck rendering to x265 in Voukoder or Handbrake, especially if you keep the compression modest.

If you would like independent confirmation of the integrity of your render, feel free to upload a short, actual render to Drive or Dropbox (not the forum or Youtube!), and post the link here.

RogerS wrote on 8/6/2024, 6:34 PM

What build of VP 21 are you using and does it happen with all of them? I find some decoding issues with 300 and newer that can show up on renders. At the moment I'm staying on build 208. Final renders are usually x264 with Voukoder.

Try to keep Radeon Graphics updated, there are issues with some driver versions.

Custom PC (2022) Intel i5-13600K with UHD 770 iGPU with latest driver, MSI z690 Tomahawk motherboard, 64GB Corsair DDR5 5200 ram, NVIDIA 2080 Super (8GB) with latest studio driver, 2TB Hynix P41 SSD and 2TB Samsung 980 Pro cache drive, Windows 11 Pro 64 bit

Dell XPS 15 laptop (2017) 32GB ram, NVIDIA 1050 (4GB) with latest studio driver, Intel i7-7700HQ with Intel 630 iGPU (latest available driver), dual internal SSD (1TB; 1TB), Windows 10 64 bit

VEGAS Pro 19.651
VEGAS Pro 20.411
VEGAS Pro 21.208
VEGAS Pro 22.93

Try the
VEGAS 4K "sample project" benchmark (works with VP 16+): https://forms.gle/ypyrrbUghEiaf2aC7
VEGAS Pro 20 "Ad" benchmark (works with VP 20+): https://forms.gle/eErJTR87K2bbJc4Q7

Timothy-Dhalleine wrote on 8/13/2024, 12:47 PM

Hey everyone,

Huge SORRY for the delay in replying (I spend most of my days in the mountains) and thanks for all the useful info. I use Vegas 21.0 Build 315. Same issue happened before on Vegas 20.0.

Thanks to your comments I could confirm this was a rendering issue. The problem disappears as I render on MAGIX HEVC/AAC MP4 (Internet UHD 2160p 59.94fps (Intel QSV). Rendering to x265 in Voukoder is also a solution!

The problem almost always happens using detailed footage and rendering as MAGIX AVC/AAC MP4 (Internet UHD 2160p 59.94fps) so it seems this rendering option should be avoided for detailed footage.

 

3POINT wrote on 8/13/2024, 1:23 PM

The problem almost always happens using detailed footage and rendering as MAGIX AVC/AAC MP4 (Internet UHD 2160p 59.94fps) so it seems this rendering option should be avoided for detailed footage.

 

Glad that you could confirm also my findings about the quality of Magix renders. When you're really critical you will see also quality degradation in HEVC renders. I use only Voukoder X265 rendering with NVENC support for quality renders, which renders also much faster.

pierre-k wrote on 8/13/2024, 2:18 PM

This case reminds me of something.

I've noticed this problem before as well. I used Luts and every time there were artifacts in dark scenes.

Solution for me:


Every time I start rendering, I switch the project to 32bit (video Levels)

Let me know if this helped you.

I would say that the old Sony AVC or Voukoder is much better quality than the Magix AVC.

3POINT wrote on 8/13/2024, 2:47 PM

This case reminds me of something.

I've noticed this problem before as well. I used Luts and every time there were artifacts in dark scenes.

Solution for me:


Every time I start rendering, I switch the project to 32bit (video Levels)

Let me know if this helped you.

I would say that the old Sony AVC or Voukoder is much better quality than the Magix AVC.

No thanks, this gives me an unacceptable slow down of the render speed. I just compared once again a Magix HEVC 2160p50 VBR NVENC render with a Voukoder HEVC 2160p50 VBR NVENC render. Magix gets an average of 42fps while Voukoder renders with an average of 60fps. Switching to the proposed 32bit (video levels) gives a level shift (because my original is full level) and a dramatical decrease in render speed to just a few fps.

I stay with Voukoder...

UltraVista wrote on 8/13/2024, 7:28 PM

The problem almost always happens using detailed footage and rendering as MAGIX AVC/AAC MP4 (Internet UHD 2160p 59.94fps) so it seems this rendering option should be avoided for detailed footage.

 

Glad that you could confirm also my findings about the quality of Magix renders. When you're really critical you will see also quality degradation in HEVC renders.

@3POINT I did extensive testing of this phenomenon a while ago, it's much easier to trigger with Magix AVC hardware encoding. I question why people even encode in H.264 today, I think it must be out of habit. When I have a specific use for H.264 due to compatibility and my encode will be the end product I use x264. But far less now due to the apparent relaxation of H.265 licensing, so now I find myself encoding in x265 where my encode will be the final, and Hardware H.265 for when it's re-encoded by a server.

It still is possible to get the artifacting from Magix HEVC hardware so for piece of mind Voukoder is almost the perfect solution except for the rumors of it's low quality with 32bit projects and 10bit media. It is likely true but looks good enough.