Is Magix AVC/AAC producing worse quality than Sony AVC/MVC?

Mats wrote on 11/25/2017, 4:42 PM

I found that Magix AVC/AAC render some videos with low light very bad in Vegas Pro 15. When I use Sony AVC/MVC in VP15 or Main Concept AVC/AAC in Movie studio 13 it´s not at all that bad. Look at the brown porch in left bottom corner.

Original file

Magix AVC/AAC

Sony AVC/MVC in VP15

Main Concept AVC/AAC in MS 13

Edit: All files actually look even a bit worse after uploading to this post.

Link to video files: https://www.dropbox.com/sh/j8hjzjxttnfn7uo/AACNLjU1HPVDvBsUiqxdOdJta?dl=0

Comments

john_dennis wrote on 11/25/2017, 8:49 PM

"All files actually look even a bit worse after uploading to this post."

I'm fairly certain that this Magix site re-encodes the video files that you upload. They probably do look a little worse than your files. The best way to do these kinds of comparisons is to upload the files to a cloud share site and post the download links here. It's too late in the day for me to peek at pixels. It appears that Vegas 15 has encoders for different use cases. At least you have options along with rendering to an uncompressed format and encoding outside of Vegas.

My main system:
Motherboard: ASUS ProArt Z790-CREATOR WIFI
CPU: Intel Core i9-13900K - Core i9 13th Gen Raptor Lake 24-Core (8P+16E) P-core Base Frequency: 3.0 GHz E-core Base Frequency: 2.2 GHz LGA 1700 125W Intel UHD Graphics 770 Desktop Processor - BX8071513900K
GPU: Currently intel on-die video adapter
RAM: CORSAIR Vengeance 64GB (2 x 32GB) 288-Pin PC RAM DDR5 5600 (PC5 44800) Desktop Memory Model CMK64GX5M2B5600C40
Disk O/S & Programs: WD Black SN850 NVMe SSD WDS100T1X0E - SSD - 1 TB - PCIe 4.0 x4 (NVMe)
Disk Active Projects: 1TB & 2TB WD BLACK SN750 NVMe Internal PCI Express 3.0 x4 Solid State Drives
Disk Other: WD Ultrastar/Hitachi Hard Drives: WDBBUR0080BNC-WRSN, HGST HUH728080ALE600, 724040ALE640, HDS3020BLA642
Case: LIAN LI PC-90 Black Aluminum ATX Full Tower Case
CPU cooling: CORSAIR - iCUE H115i RGB PRO XT 280mm Radiator CPU Liquid Cooling System
Power supply: SeaSonic SS-750KM3 750W 80 PLUS GOLD Certified Full Modular Active PFC Power Supply
Drive Bay: Kingwin KF-256-BK 2.5" and 3.5" Trayless Hot Swap Rack with USB 3
Sound card: Realtek S1220A on motherboard. Recording done on another system.
Primary Monitor: Asus ProArt PA248q (24" 1920 x 1200)
O/S: Windows 10 Pro 10.0.19045 Build 19045

Camera: Sony RX10 Model IV

https://www.youtube.com/user/thedennischannel

3POINT wrote on 11/26/2017, 6:26 AM

For me, the Sony AVC is still the favourite AVC codec, good quality also at low bitrates, with fast and single pass encoding.

i am erikd wrote on 11/26/2017, 9:13 AM

I have to agree with the points that 3point made. In the end Magix AVC is too slow and isn't as good as Sony AVC.

marcel-vossen wrote on 11/26/2017, 10:39 AM

I used to use Sony AVC, but at some point this output filter started acting weird and rendered every single MP4 file as Video.MP4.tmp instead of just Video.MP4, it does work however but I have to rename it first.... This started back in Vegas 14 but is also the case in Vegas 15. The Magix AVC filter doesn't do this, so I'm really wondering: does anybody have a clue how to re-install this filter in any way or what the hell could have changed in my configuration that caused this?

rstrong wrote on 11/26/2017, 7:32 PM

Hmmm...........I thought I was the only one who was getting those temp files........kinda frustrating to have to rename to view it. Anyone no why this is ? It only happens on the PC I have VP14 installed on.

Last changed by rstrong on 11/26/2017, 7:37 PM, changed a total of 2 times.

R. Strong

Custom remote refrigerated water cooled system for CPU & GPU. Intel i7- 6950X, 10 Core (4.3 Turbo) 64gb DDR4, Win7 64 Bit, SP1. Nvidia RTX 2080, Studio driver 431.36, Cameras: Sony HVR-Z5U, HVR-V1U, HVR-A1U, HDR-HC3. Canon 5K MK2, SX50HS. GoPro Hero2. Nikon CoolPix P510. YouTube: rstrongvideo

dream wrote on 11/27/2017, 1:38 AM

For me, the Sony AVC is still the favourite AVC codec, good quality also at low bitrates, with fast and single pass encoding.

how its faster and low bitrates than magix?

dream wrote on 11/27/2017, 1:41 AM

for me , magix - qsv intel is best -for quality/size=less time

3POINT wrote on 11/27/2017, 2:12 AM

For me, the Sony AVC is still the favourite AVC codec, good quality also at low bitrates, with fast and single pass encoding.

how its faster and low bitrates than magix?

It's faster than Magix without support of GPU. Magix is only faster when it can benefit from the graphics card. How much faster depends on the type of graphics card. On my workstation it's just 10-15% faster than rendering with SAVC. On my laptop MAVC is 25-30% slower than SAVC because it has no advantage at all from the graphics card.

Quality, at low bitrates I see with MAVC more and earlier blocking artifacts than with SAVC.

Last changed by 3POINT on 11/27/2017, 2:12 AM, changed a total of 1 times.

3POINT, Theo Houben, Vegasuser since version 5 and co-founder and moderator of the Dutch Vegasforum https://www.vegas-videoforum.nl/index.php

Recware: DJI Osmo Pocket/Mavic Mini, GoproHero7Black, PanasonicFZ300/HCX909.

Software: Vegaspro365+Vegasaur, PowerDirector365, Davinci Resolve 18

Hardware: i910900k, 32GB, GTX2080super, 2x1920x1200 display

Playware: Samsung Qled QE65Q6FN, Philips 55PFL7108

marcel-vossen wrote on 11/27/2017, 5:15 AM

Hmmm...........I thought I was the only one who was getting those temp files........kinda frustrating to have to rename to view it. Anyone no why this is ? It only happens on the PC I have VP14 installed on.

It is comforting to see I'm not the only one too...so this must be some kind of bug in Vegas or a combination of Vegas with other software? You wouldn't happen to have Cyberlink PowerDVD 17 installed? I think it started around the time I installed this on my PC.

Dexcon wrote on 11/27/2017, 5:35 AM

As a test, I've just rendered a 4K mp4 video event (from a Sony FDR-AX100) using the Sony AVC 1920x1080 25fps render template. The resulting render was .avc. Source video on the D drive and rendered to the E drive. Cyberlink PowerDVD17 is installed on the C drive.

Cameras: Sony FDR-AX100E; GoPro Hero 11 Black Creator Edition

Installed: Vegas Pro 16 Edit, Vegas Pro 17 Edit, Vegas Pro 18, Vegas Pro 19 Edit, Vegas Pro 20 Edit, HitFilm Pro 2021.3, BCC 2023, Mocha Pro 2022.5.1, Ignite Pro, NBFX TotalFX 7, Neat NR, DVD Architect 6.0, MAGIX Travel Maps, Sound Forge Pro 16, SpectraLayers Pro 9, iZotope RX10 Advanced and many other iZ plugins, Vegasaur 4.0

Windows 11

Dell Alienware Aurora 11

10th Gen Intel i9 10900KF - 10 cores (20 threads) - 3.7 to 5.3 GHz

NVIDIA GeForce RTX 2080 SUPER 8GB GDDR6 - liquid cooled

64GB RAM - Dual Channel HyperX FURY DDR4 XMP at 3200MHz

C drive: 1TB M.2 PCIe NVMe SSD

D drive: 6TB WD 7200 rpm Black HDD 3.5"

E & F drives: 2 x 2TB Barracuda HDDs 2.5"

 

marcel-vossen wrote on 11/27/2017, 6:24 AM

I'm using MP4 as output format for the Magix and Sony AVC filters, so maybe it will work better with AVC formats...

What's also very weird is that the Magix AVC/AAC filter disappears and re-appears all the time when I re-start Vegas. As you can see in the screenshots below, I have selected the Magix output filter as a favourite and it's often just MISSING, and when I just close Vegas and open it again, it is back, it seems this is just a giant bug in Vegas and it's driving me pretty mad...when I want to use Sony AVC I have to rename every single rendered file, and when i want to use Magix AVC I have to be lucky enough to find it in the output formats or else restart the whole program every time...it doesn't make any sense.

WTF Magix, can't you make an output filter that I'm not actually using disappear all the time if you want to play Houdini jokes on your customers? :D

Marcel

 

 

Musicvid wrote on 11/27/2017, 6:41 AM

Comparing either quality or speed between two encoders, one using hardware and one not, is too many moving targets for a sensible discussion.

Two encoders can each only be "best" on a level playing field.

Mats wrote on 11/27/2017, 6:41 AM

I have a slight feeling that this thread has been seized by some nearby other questions ;-)

My original question at the top of the page was: if anyone else have seen difference in quality between rendered files from Magix AVC/AAC vs Sony AVC/MVC. Especially in low light.

I believe I have about the same render settings in all examples. Or have I overlooked something?

rstrong wrote on 11/27/2017, 8:00 PM

It is comforting to see I'm not the only one too...so this must be some kind of bug in Vegas or a combination of Vegas with other software? You wouldn't happen to have Cyberlink PowerDVD 17 installed? I think it started around the time I installed this on my PC.

Marcell....

No, PowerDVD not installed on that PC. Wish I knew what was causing it.

robert

R. Strong

Custom remote refrigerated water cooled system for CPU & GPU. Intel i7- 6950X, 10 Core (4.3 Turbo) 64gb DDR4, Win7 64 Bit, SP1. Nvidia RTX 2080, Studio driver 431.36, Cameras: Sony HVR-Z5U, HVR-V1U, HVR-A1U, HDR-HC3. Canon 5K MK2, SX50HS. GoPro Hero2. Nikon CoolPix P510. YouTube: rstrongvideo

Former user wrote on 11/27/2017, 8:09 PM

My original question at the top of the page was: if anyone else have seen difference in quality between rendered files from Magix AVC/AAC vs Sony AVC/MVC. Especially in low light.

I believe I have about the same render settings in all examples. Or have I overlooked something?

Yes I see the extra noise. it gets worse when you turn on the Nvidia hardware encoding. It's the same sort of noise just amplified more. So it's a fake mainconcept codec then? The noise it produces is so similar to hardware produced noise it's almost like it's a software version of the the NVENC asic.

 

Would also make sense as to why Vegas15 mainconcept is slower than previous versions. It's because it's not really mainconcept encoder.

NickHope wrote on 11/28/2017, 2:45 AM

The MainConcept AVC CPU-only encoder used in the MainConcept AVC/AAC renderer in VP12-14 is still in VP15 at C:\Program Files\VEGAS\VEGAS Pro 15.0\FileIO Plug-Ins\mcmp4plug2\mc_cpu\mc_enc_avc.dll. It is version 9.7.9.5738 (found by right-clicking on the file in Windows Explorer then choosing Properties > Details).

The MainConcept AVC CPU-only encoder used in the Magix AVC/AAC renderer in VP15 is at C:\Program Files\VEGAS\VEGAS Pro 15.0\FileIO Plug-Ins\mxavcaacplug\mc_cpu\mc_enc_avc.dll. It is version 10.0.14.2531.

I very much doubt it's a "fake" as it's "Copyright 2015 MainConcept GmbH" and the version numbering appears logical. Maybe they messed it up, or maybe it's not implemented optimally in Vegas somehow, or maybe it's better in some ways and worse in others.

You can enable the older MainConcept AVC/AAC renderer in the internal preferences (accessed by holding SHIFT while clicking "Preferences"):

If you really wanted, you could replace the latter dll file with the former dll file, so you have the older quality within the Magix renderer, but rename the latter first so you can change back.

Mats wrote on 11/28/2017, 3:16 PM
You can enable the older MainConcept AVC/AAC renderer in the internal preferences (accessed by holding SHIFT while clicking "Preferences"):

Thank you Nick!