Hardware encoding virkede i 2.4.7 men stoppede i 2.4.8 og 2.4.9 beta

General Support / Questions Hardware-kodning
1

I uploaded my log and video files for the issue. What I see is FFMPEG gets set to the primary conversion method, and then is replaced with MENCODER which attempts to verify QuickSync and fails after multiple attempts and finally uses setting for software conversion.

I see lines where the GT730 NVIDIA card is recognized and the Intel 630 as well, but hardware encoding never seems to kick in. Any suggestions?

2

Can you attach your conversion log

3

Sorry, followed the instructions of the FTP site and didn’t add a link:
ftp://upload.mcebuddy2x.com/jpyatt/TheGoodDoctor.log

4

So a couple of things you need to be aware of:

  1. The order of your encoders:

order=handbrake,ffmpeg,mencoder

This means it’ll use handbrake first (QuickSync) and then ffmpeg
(NvEnc/CUDA) for hardware encoding.

You have BOTH, QuickSync and CUDA available. In the earlier version due to
a bug in MCEBuddy if both were found it would use ffmpeg first (cuda) and
then handbrake (quicksync).
With 2.4.9 of both hardware encoders are found it’ll use the user specified
encoder first (in your case handbrake, ie. quicksync).

So when it starts QuickSync encoding, the Intel graphics driver fails.

2018-03-15T13:28:46 MCEBuddy.AppWrapper.Handbrake → Handbrake
failed, non 0 return code

This is likely due to a bad graphics driver, try installing one of the
recommended drivers version to get your QuickSync encoder working.

Because the hardware encoder fails, MCEBuddy tries to use the software
version of the same encoder (i.e. handbrake) and this works and this is
what you’re seeing.

MCEBuddy does not try the second available hardware encoder before falling
back to software encoder, this is a known issue and it’s slated to be fixed
in the next version.

Basically you’re facing this issue because your system supports BOTH Cuda
and QuickSync.

The simplest solution is to:

  1. Fix your Intel graphics driver to that QuickSync works
  2. Change the order in your profile to

order=ffmpeg,handbrake,mencoder

This make MCEBuddy use CUDA/NvEnc first and hopefully that driver is more
stable then you Intel driver and hardware encoding will be successful.

The dual hardware encoder issue will be addressed in the next release

5

Thanks for the help. I updated the Intel driver from the Hardware encoding FAQ and eventually everything worked. A one hour show from Windows Media Center converts with commercials removed in 14 minutes. Awesome.

6

Jeg har et Sandy Bridge i7 2600 CPU og nu et Nvidia Quadro P2000, og jeg vil gerne få hardware-kodning til at virke, men jeg prøvede at installere den anbefalede driver: Intel 2010.18.10.3958 x64_15.33.30.3958 som anbefalet ovenfor, men den siger, at mit hardware ikke opfylder minimumskravene og ville ikke installere.

Er der en anden anbefalet driver? Eller skal jeg bare springe QuickSync-supporten over og blot ændre rækkefølgen af kodere som du foreslog ovenfor?

Tak.

7

Afhænger af, hvad du vil bruge; hvis du bruger nvidia-hardwarekodning, behøver du ikke Intel-driverne – bare brug omrokering af encoderen, eller hvis du kører den nyeste version 2.4.9, vælger den ffmpeg-profilen automatisk, da det er den eneste tilgængelige hardware-koder.

PS – der er flere anbefalede drivermuligheder, du kan prøve, inklusive nogle nyere til Windows 10.

8

Jeg tror, jeg må mangle noget, for jeg installerede 2.4.9, og det fungerer fint til software-kodning. Men jeg kan ikke finde nogen

  nvenc nogen steder i hverken mcebuddy.log eller i de individuelle videofil-logs. Jeg sørgede for at installere CUDA-developer-kit'et

  og satte flueben ved "hardware-acceleration" i mcebuddy. Jeg ændrede også rækkefølgen af encoderne, så ffmpeg er først, stadig

  ingen succes.

  Hvad kunne jeg mangle? Er der noget andet, der kræves for at få det til at bruge mit hardware?

Tak.

9

Vedhæft din konverteringslog.