Comments

j-v wrote on 12/22/2018, 3:54 PM

In the default settings that MC AVC codec is now a part of the Magix AVC and is self not listed in the rendersettings.

If you want that old one to see in the rendersettings you can switch it on by allowing it in the Preferences/Internal option and than you see this setting

and the codec appears in the rendersettings

Last changed by j-v on 12/22/2018, 3:56 PM, changed a total of 1 times.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

vkmast wrote on 12/22/2018, 3:59 PM

As j-v says, you can get it back. This is valid for Vegas Pro as well.

colin-anderson wrote on 12/23/2018, 9:58 AM

Thanks. It worked. MAGIX AVC, even the BD templates is still not DVD Architect compliant so have to use Mainconcept. Yep, I'm still using DVD Architect :)

rraud wrote on 12/23/2018, 10:55 AM

On the MAGIX AVC render template there are options for 'Mainconcept AVC', 'Intel QSV' and 'NV'. I do not know if that is an updated Mainconcept encoder or the legacy. I have no knowledge of the Intel QSV or NV either. Perhaps one of the VP video experts can enlighten us.

j-v wrote on 12/23/2018, 11:13 AM

I'm not an expert, but I did experience the switch from Mainconcept AVC to Magix AVC in the steps since the program comes from SonyCreative Software.
I think the base is and stays the old Mainconcept AVC codec and the development team build in more options, not to use the too low advantage of rendering with help of Cuda anymore, but switching to the new possibilities with the Intell Graphics GPU (QSV) and those of Nvidia (NVENC). That's why in the specs is written out that to use those options you have to use those GPU's starting with the newer series.
(That I'm no expert means also that I know nothing about AMD options I never used)

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

NickHope wrote on 12/23/2018, 11:51 AM

On the MAGIX AVC render template there are options for 'Mainconcept AVC', 'Intel QSV' and 'NV'. I do not know if that is an updated Mainconcept encoder or the legacy...

These are the version numbers of mc_enc_avc.dll that do the encoding work in VP16 build 352:

  • Legacy Mainconcept AVC encoder: 9.7.9.5738 (same version since VP12 or even older)
  • MAGIX AVC encoder: 10.0.14.2531

In practice I don't think much has changed between them but there might be some very slight improvement. I don't think there's a reason to stick with the legacy Mainconcept encoder unless you have an old GTX 400-500 series GPU that supports CUDA rendering or a Radeon HD 4000/5000/6000 series GPU that supports OpenCL rendering.

rraud wrote on 12/24/2018, 9:51 AM

Thanks, but I'm still not clear on this. The 'MainConcept', 'Intel QSV' and 'NV' are 'encode mode' options in the Magix AVC customize dialog..

The 'MainConcept legacy' AVC (if enabled) and the Sony AVC do not have the "encode mode" option.

NickHope wrote on 12/24/2018, 8:56 PM
The 'MainConcept legacy' AVC (if enabled) and the Sony AVC do not have the "encode mode" option.

@rraud Preferences > General > Allow legacy GPU rendering.

rraud wrote on 12/25/2018, 10:48 AM

Any advantages using the Magix AVC with the encode mode set to 'Intel QSV' or 'NV' over the MainConcept or the Lagacy MainConcept? I notice the Intel and NV do not have the 'Progressive download' or 'Reference frame' options. BTW, what does "NV" stand for?

Thanks and happy holidays, Rick

j-v wrote on 12/25/2018, 11:15 AM

Any advantages using the Magix AVC with the encode mode set to 'Intel QSV' or 'NV' over the MainConcept or the Lagacy MainConcept? I notice the Intel and NV do not have the 'Progressive download' or 'Reference frame' options. BTW, what does "NV" stand for?

Thanks and happy holidays, Rick

With me there is very much difference in rendertime with the Magix AVC Nvenc option and the QSV option.
Mostly 6-8 times faster than the legacy or Magix Mainconcept options.
I see no difference in quality exept with very low bitrates with the QSV option.
That one gives in that case sometimes black or distorted frames.
As I mentioned before with me the Nvenc option is never called "NV".

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

rraud wrote on 12/25/2018, 3:33 PM

'NV' is what it's listed as in the 'Encode mode' options in the Magix AVC on my Dell XPS, I did not know what it stood for.. now I do, Thanks. Nvida NVENC, duh says me.

colin-anderson wrote on 1/12/2019, 10:16 AM
 

In practice I don't think much has changed between them but there might be some very slight improvement. I don't think there's a reason to stick with the legacy Mainconcept encoder unless you have an old GTX 400-500 series GPU that supports CUDA rendering or a Radeon HD 4000/5000/6000 series GPU that supports OpenCL rendering.

Well, again for me, the MAGIX AVC doesn't output DVD Architect complient files so I have to continue to use the legacy Mainconcept encoder when authoring blu-ray discs. If ever that changes, I will switch to Magix AVC.

j-v wrote on 1/12/2019, 11:07 AM

If ever that changes

Don't count on that, Bluray and burning dics are from the past. Why should a company changes old stuff from ancient years?
Since more than a year now no discs are being produced anymore.

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

NickHope wrote on 1/12/2019, 11:57 PM
Well, again for me, the MAGIX AVC doesn't output DVD Architect complient files so I have to continue to use the legacy Mainconcept encoder when authoring blu-ray discs. If ever that changes, I will switch to Magix AVC.

@colin-anderson Do files rendered with a MAGIX AVC Blu-ray template always get recompressed by DVD Architect? I've read about that happening in NVENC mode (here & here), but I can't find clear discussion about that issue with regard to MainConcept AVC mode. Also, have you reported it and did you get an answer?