"MPEG-4 export moduel: Export was canceled due to an unknown error.".

turdsurfer wrote on 5/9/2017, 9:28 AM

I just bought and installed the Main Concept codec and configured MEP2017 to use hardware encoding, but as soon as I export to MPEG-4, this error (including typo) occurs:
"MPEG-4 export moduel: Export was canceled due to an unknown error.".

These are the details:

Move Edit Pro Plus version 16.0.3.66 (UDP3)
with MPEG-4-Codec (MainConcept)
GPU: NVIDIA GeForce GTX 1060 6GB
CPU: Intel i7 920
File -> Program -> Settings -> Import/Export: both hardware acceleration options checked, and preferred code set to "Main concept".
In export dialog: Calculate video effects on GPU unchecked (checking it doesn't help)
In export dialog -> Advanced: video codec is set to MPEG4 H.264 and "Streamable format" is checked (unchecking doesn't help).

This is the "Format description":
MPEG4 Export (MP4) CUDA:
Video: 1920x1080p; 60.00 Frames/s; H.264 3000 kbit/s
Audio: 48000 Hz; Stereo; AAC
Size estimate: 44239 kByte

Exporting using software encoding works, but that's obviously slow.
Exporting using the codec "MPEG-4 Simple" works when checked in export dialog -> Advanced.

Comments

emmrecs wrote on 5/9/2017, 10:45 AM

Hi, welcome to the Magix forums.

You cannot use the Main Concept codec with Hardware Acceleration. If you turn HWA off or deselect the MC codec, (which should revert to using the default Intel codec) I think the export should proceed without problem.

Jeff

turdsurfer wrote on 5/9/2017, 10:51 AM

Thanks. Hardware Acceleration didn't work with the default codec, it kept defaulting to software encoding. I was under the impression that the MainConcept codec was needed to use hardware acceleration.
Anyway, if the MainConcept code doesn't support hardware acceleration, then Magix can simply show an error dialog explaining that instead of "unknown error".

emmrecs wrote on 5/9/2017, 12:14 PM

I apologise for my misinformation. I hadn't realised your processor is not one which includes graphics processing.

I think you are also correct that only software encoding is available to you.

Jeff

johnebaker wrote on 5/9/2017, 1:36 PM

. . . . if the MainConcept code doesn't support hardware acceleration . . . .

It does, however, for me, the MainConcept codec in conjunction with HWA completes, and the resulting file has zero bytes ie contains nothing.

This is a known issue with the MainConcept codec and MainConcept are not developing it any more.

Also there are other issues - see this answer it may also apply.

HTH

John EB

Scenestealer wrote on 5/9/2017, 8:28 PM

Hi Jeff and John

FYI - The reason the errors occur when you have HWA selected and are using the MC encoder / codec, is because the default setting for the AVC Encoder in the "Advanced Settings > Advanced Video Settings" is "Auto" and this defaults to CUDA for the encode. The encoder cannot connect with CUDA , for reasons we have discussed many times, and fails. Change this setting to "Intel QSV" in the dropdown and it will use QuickSync to accelerate the encode using the Main Concept encoder.

Peter

johnebaker wrote on 5/10/2017, 3:38 AM

Hi Peter

. . . . Change this setting to "Intel QSV" in the dropdown and it will use QuickSync to accelerate the encode using the Main Concept encoder. . . . .

However it still produces 0 byte files, I reported this to Magix about 2 years ago and they confirmed it is a known issue with the MC codec.

John EB

Scenestealer wrote on 5/10/2017, 6:50 AM

Hi John

Works like a champ here in MEP2017! It also works for French and German members.

Once you select it and OK at the bottom, go back to the previous encoder screen and click Driver Information and the Quick Sync driver version should appear in the box at the bottom. The export template should then show QuickSync in the details instead of CUDA or GPU.

Peter

johnebaker wrote on 5/10/2017, 10:40 AM

Hi Peter

Everything was as you indicated above, Intel driver used, Quick Sync used and indicated at top of dialog, however always a 0 byte file.

Turn of HWA - renders correctly but takes about 50% longer.

My Quick Sync driver version is 20.19.0015.4531 how does this compare to yours? Previous versions of the driver, the 15.xx.xxxx.xxxx series also had the same issue.

Intel HD codec is also a lot faster compared to the MC codec when both are using HWA, on the same project takes approx 72 % of the time to render than the MC takes, also do not get the unusual 15 sec wait before the progress dialog appears - this appears to be set in the MC Muxer settings bottom item.

John EB

Scenestealer wrote on 5/10/2017, 7:42 PM

Hi John

My Quick Sync driver version is 20.19.0015.4531

I think this is your display driver version? Mine is 21.20.16.4590 from Jan 17.

My QuickSync driver that displays in the encoder driver information is 21.21.0013.7653.

I guess the efficiency of the respective encoder may come down to the material and type of effects and not least the hardware setup.I just did a couple of encodes in VPX with about 2 mins of 1080 50P clips with quite a few effects - PinP Multiple overlaid Alphas, couple of Fades, slomo, and and the MC and Intel encode times were almost identical at about 30 secs faster than real time. Selecting the Calculate effects on GPU option took 15secs longer than Realtime in both cases and interestingly it pushed of a lot of the load onto the Nvidia 1060 card. A little more so with the MC encode.

Peter