This project has moved. For the latest updates, please go here.

Hardware Acceleration

Sep 23, 2014 at 1:13 PM
Edited Sep 23, 2014 at 1:23 PM
Hi team,

I'm very interested in getting hardware acceleration to work so I donated and downloaded 2.4.1 today. I don't notice any improvement in speed over 2.3 (was not using it long before upgrading to 2.4 so not really scientific) and suspect this is being fully handled in software as ffmpeg is running hot in task manager.

I have installed the Intel driver linked from the FAQ (10.18.10.3379), and ensured Hardware is ticked in the conversion settings. The logs mentioned in the FAQ ("QuickSync encoding supported availble") do not appear at all in any of the conversion logs.

I am running a Intel NUC d54250wyk (Haswell i5-4250U with HD5000 GPU).

Any ideas?

BTW, feature request #1 - allow configuration change without having to cancel the conversion job!

feature request #2 - have a simple indicator to show if hardware acceleration is being used - the log method is very difficult to use in practice, as you apparently have to wait for the process to finish to check and that could take hours

Cheers
Daniel
Coordinator
Sep 23, 2014 at 1:42 PM
What profile are you using? Upload your conversion log.

Sep 24, 2014 at 12:49 AM
Hi rboy1,

I'm using the "iPad" profile. Here's the log

Thanks
Daniel
Coordinator
Sep 24, 2014 at 2:38 AM
That explains it currently the iPad profile uses ffmpeg and not handbrake to encode hence the hardware accell is not availbale. Use the M4V or MP4 profiles and it should work. We'll see how to include hardware acelleration on the iPad profile in the next build.

Sep 25, 2014 at 2:47 AM
Thanks for the quick response. I have tried both options, and get that QuickSync is not available.

MCEBuddy.AppWrapper.Handbrake --> QuickSync encoding supported availble -> False

log

Can't see any obvious reason. The hardware should support it. There is a HDMI and Mini DVI port on the NUC, allowing for two monitors. I set it in BIOS to only allow the HDMI port, still the same issue. I haven't tried the dummy driver yet. For what I want to use this all for, I think software encoding is suitable for now. Would have been good this all working out of the box, but I don't particularly want to go breaking too many things by changing the system - it's the household htpc, and if it stops working I get into a lot of trouble ;-) Already the change in the video driver for this has resulted in Media Centre intermittently reporting an error about video RAM available to it, an issue which has been resolved in more recent driver builds. I'm going to roll back to the latest driver now.

I'll have an opp to look at this again in a few weeks, any tips appreciated.

Thanks
Daniel
Coordinator
Sep 25, 2014 at 6:07 AM
Your driver looks okay. Try connecting a monitor to your HDMI port that's connected to your Intel graphics card. That helps to "activate" the driver sometimes.
Alternatively you can try manually changing the profile codec to qsv_h264 as the codec. This will force handbrake to use quicksync if available, see is that works.

Sep 26, 2014 at 12:32 AM
I had the same problem with beta 2.4.1 from 9-21. It looks like there is a bug in the version of Handbrakecli that is included (svn6418). I upgraded to the latest nightly (svn6419) and my problems went away. I put both versions of HandbrakeCLI in the same spot and ran the QSV check (svn6418 does not report QSV):



C:\Program Files\MCEBuddy2x\handbrake>handbrakecli -i null -o null
Output format can't be guessed from file name (null), using default.
[16:20:20] hb_init: starting libhb thread
HandBrake svn6419 (2014092201) - MinGW x86_64 - http://handbrake.fr
8 CPUs detected
Opening null...
[16:20:20] CPU: Intel(R) Core(TM) i7-2600S CPU @ 2.80GHz
[16:20:20] - Intel microarchitecture Sandy Bridge
[16:20:20] - logical processor count: 8
[16:20:20] Intel Quick Sync Video support: yes
[16:20:20] - Intel Media SDK hardware: API 1.4 (minimum: 1.3)
[16:20:20] - H.264 encoder: yes
[16:20:20] - preferred implementation: hardware (any)
[16:20:20] - H.265 encoder: no
[16:20:20] hb_scan: path=null, title_index=1
libbluray/bdnav/index_parse.c:162: indx_parse(): error opening null/BDMV/index.b
dmv
libbluray/bdnav/index_parse.c:162: indx_parse(): error opening null/BDMV/BACKUP/
index.bdmv
libbluray/bluray.c:2182: nav_get_title_list(null) failed
[16:20:20] bd: not a bd - trying as a stream/file instead
libdvdnav: Using dvdnav version 5.0.1
libdvdread: Encrypted DVD support unavailable.
libdvdread: Can't stat null
No such file or directory
libdvdread: Could not open null
libdvdnav: vm: failed to open/read the DVD
[16:20:20] dvd: not a dvd - trying as a stream/file instead
[16:20:20] hb_stream_open: open null failed
[16:20:20] scan: unrecognized file type
[16:20:21] libhb: scan thread found 0 valid title(s)
No title found.

HandBrake has exited.

C:\Program Files\MCEBuddy2x\handbrake>handbrakecli-org -i null -o null
Output format can't be guessed from file name (null), using default.
[16:20:28] hb_init: starting libhb thread
HandBrake svn6418 (2014091901) - MinGW x86_64 - http://handbrake.fr
8 CPUs detected
Opening null...
[16:20:28] CPU: Intel(R) Core(TM) i7-2600S CPU @ 2.80GHz
[16:20:28] - Intel microarchitecture Sandy Bridge
[16:20:28] - logical processor count: 8
[16:20:28] hb_scan: path=null, title_index=1
libbluray/bdnav/index_parse.c:162: indx_parse(): error opening null/BDMV/index.b
dmv
libbluray/bdnav/index_parse.c:162: indx_parse(): error opening null/BDMV/BACKUP/
index.bdmv
libbluray/bluray.c:2182: nav_get_title_list(null) failed
[16:20:28] bd: not a bd - trying as a stream/file instead
libdvdnav: Using dvdnav version 5.0.1
libdvdread: Encrypted DVD support unavailable.
libdvdread: Can't stat null
No such file or directory
libdvdread: Could not open null
libdvdnav: vm: failed to open/read the DVD
[16:20:28] dvd: not a dvd - trying as a stream/file instead
[16:20:28] hb_stream_open: open null failed
[16:20:28] scan: unrecognized file type
[16:20:28] libhb: scan thread found 0 valid title(s)
No title found.

HandBrake has exited.
Coordinator
Sep 30, 2014 at 4:35 PM
Thanks for reporting this, we are doing a custom build of handbrake now since they no longer provide 32bit builds. This will be fixed in the next release today.
Marked as answer by rboy1 on 9/30/2014 at 8:35 AM