Magix AVC Issue with 4K rendering

Benjamin wrote on 11/8/2019, 9:03 PM

Hi, one of my recent recordings using Share keeps messing up whenever I attempt to render it with the Magix AVC codec. I used the Nvencoder to begin with at 4k, 60fps, 100k bitrate but whenever I play it back post render there are two 5s or so glitches in the 17 minute video with certain frames attempting to repeat themselves. Redoing it with Mainconcept avc fixed that but then another problem occured post render with a green tint appearing on nearby walls during quick mouse turns for a split second before returning to normal. The raw footage and the Sony Vegas preview are fine.

Is Sony XAVC a good alternative for 4k gameplay rendering? I might have to try that one out next if I can't find a fix for the above issue.

Comments

john_dennis wrote on 11/8/2019, 9:21 PM

http://www.vegascreativesoftware.info/us/forum/share-your-favorite-happy-otter-scripts-custom-command-line--116294/

Benjamin wrote on 11/8/2019, 9:53 PM

http://www.vegascreativesoftware.info/us/forum/share-your-favorite-happy-otter-scripts-custom-command-line--116294/

Hi, is there something provided within that link that corrects the problem above? Most of what was being said went way above my head unfortunately.

 

Musicvid wrote on 11/8/2019, 11:52 PM

Is Sony XAVC a good alternative for 4k gameplay rendering? I might have to try that one out next if I can't find a fix for the above issue.

Certainly better than hardware encoding.

Benjamin wrote on 11/13/2019, 3:35 AM

Is Sony XAVC a good alternative for 4k gameplay rendering? I might have to try that one out next if I can't find a fix for the above issue.

Certainly better than hardware encoding.


Seems that Sony XAVC rendered it correctly at least :). File size was gb's larger than I anticipated but nothing my upload speed can't handle. If another render ever glitches out I know where to turn to. I have rendered 3 more videos since and not one of them had that odd glitch.

frmax wrote on 11/13/2019, 5:21 AM

Have you tried to set DRAM to zero before rendering ?

I14900K, RTX 4070 Super, 64GB RAM, 4TB M2, 4TB SSD, VEGAS Pro 14-23 (Post), Magix ProX, Davinci Resolve Studio, Powerdirector 365
AMD 5900, RTX 3090 TI, 64GB RAM, 1 TB M2 SSD, 4 TB HD, VP 21 Post, VP22

Monitor LG 32UN880; Camera Sony FDR-AX53; Photo Canon EOS, Samsung S22 Ultra

pierre-k wrote on 11/13/2019, 5:26 AM

This is a sample example of rendering errors.
The solution is to leave the DRAM at any number (eg 2000) and change only the number rendering threads to 1.

Method:
1. Permanently set number rendering threads to 1
2: DRAM for example 2000
3. Restar Vegas

4. Render your project

It works for me, without artifacts and errors in the video.
Do not use Magix AVC - it is of poor quality. Much better is the Sony AVC.

fr0sty wrote on 11/13/2019, 11:08 AM

Sometimes updating your GPU driver, especially changing to the studio drivers for nvidia cards if you haven't already, can help this.

The link you were given is to a Vegas extension called happy otter scripts. you can sign up for its beta, then download it for free (at least while it is still in beta testing). HOS has a sub-program called Render + that allows you to utilize ffmpeg encoding within Vegas, as well as other cool tools like noise reduction, free. The x264 encoders it uses are of the highest quality for the format, and they typically do not suffer from the repeat frame stutters the Vegas GPU encoders have.

 

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Musicvid wrote on 11/13/2019, 11:15 AM

I used the Nvencoder to begin with at 4k, 60fps, 100k bitrate but whenever I play it back post render there are two 5s or so glitches 

"100k bitrate" is obviously a typo. If that is actually 100Mbps, try cutting that in half and see if it makes a difference.

Benjamin wrote on 11/13/2019, 7:49 PM

Have you tried to set DRAM to zero before rendering ?

I didn't try that no.

 

This is a sample example of rendering errors.
The solution is to leave the DRAM at any number (eg 2000) and change only the number rendering threads to 1.

Method:
1. Permanently set number rendering threads to 1
2: DRAM for example 2000
3. Restar Vegas

4. Render your project

It works for me, without artifacts and errors in the video.
Do not use Magix AVC - it is of poor quality. Much better is the Sony AVC.


I just tried that but that particular video still glitches post render.

I will just change to a different render codec going forward. When you say Sony AVC did you mean the XAVC? Sony AVC doesn't seem to have a customizable profile for 4k just custom framerate with a locked maximum bitrate which is set pretty low in comparison with some of the others.

Sometimes updating your GPU driver, especially changing to the studio drivers for nvidia cards if you haven't already, can help this.

The link you were given is to a Vegas extension called happy otter scripts. you can sign up for its beta, then download it for free (at least while it is still in beta testing). HOS has a sub-program called Render + that allows you to utilize ffmpeg encoding within Vegas, as well as other cool tools like noise reduction, free. The x264 encoders it uses are of the highest quality for the format, and they typically do not suffer from the repeat frame stutters the Vegas GPU encoders have.

 


I might download that then thank you for the explanation :)

I used the Nvencoder to begin with at 4k, 60fps, 100k bitrate but whenever I play it back post render there are two 5s or so glitches 

"100k bitrate" is obviously a typo. If that is actually 100Mbps, try cutting that in half and see if it makes a difference.


That actually fixed it using the Magix AVC profile. What's odd though is in the recording the bitrate details display 128445kbps yet rendering it caused glitches with high bitrates. I will set this as the solution but I might go ahead and render using a different template going forward.

 

Musicvid wrote on 11/13/2019, 7:58 PM

128445 Kbps = 128Mbps = Way too high. Try cutting it in half.