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

GPU/Hardware Encoding and Acceleration FAQ's

Coordinator
Jun 22, 2014 at 2:45 PM
Edited Jul 26, 2016 at 3:48 PM
This thread is a quick compilation of the FAQ's being asked around and answered related to GPU and Hardware encoding:

1. What platforms and devices are supported for GPU encoding

MCEBuddy supports QuickSync, OpenCL (currently through Handbrake) and NVENC (currently through FFMPEG). QuickSync and NVENC are used for encoding the video and OpenCL is used to accelerate the decoding and video processing (deinterlacing, resizing, cropping etc). It can support any driver (Intel, ATI, NVidia) that support QuickSync, NVENC and OpenCL.
To use Intel QuickSync, see FAQ 2 for driver details
For H.264 hardware encoders, Intel Sandy Bridge (1st Generation) or newer chipsets are required
For H.265 hardware encoders, Intel Broadwell (4th Generation) or newer chipsets are required

To use NVENC encoders, NVIDIA driver version 347.09 or newer are required
For H.264 hardware encoding requires CUDA hardware capability version 3.0 or later (Kepler or newer)
For H.265 hardware encoding required CUDA hardware capability version 5.2 or later (Maxwell GM2xx or newer)

2. What are the stable drivers for Intel QuickSync and NVIDIA NvEnc

The latest stable driver for QuickSync we have tested is 10.18.10.3958 (build 15.33.30.3958)
These drivers have been uploaded for your convenience here:
32bit - https://www.dropbox.com/s/uiip9fd562mfhyd/Intel_10.18.10.3958%20x86_15.33.30.3958.exe
64bit - https://www.dropbox.com/s/ushro6ovxg2ztqp/Intel_%2010.18.10.3958%20x64_15.33.30.3958.exe
.
The latest stable driver for NVIDIA tested is v353.90 (which is part of NVIDIA SDK v7.5 64bit)
Win 7/8.1 - http://developer.download.nvidia.com/compute/cuda/7.5/Prod/local_installers/cuda_7.5.18_windows.exe
win 10 - http://developer.download.nvidia.com/compute/cuda/7.5/Prod/local_installers/cuda_7.5.18_win10.exe
.
Other stable drivers are given below in the next post (see FAQ 10)

3. My conversion keeps hanging when I enable Hardware Encoding

If the conversion works when you disable Hardware Encoding (Conversion Task Settings -> Advanced Settings -> Expert Settings -> Enable Hardware Encoding) then most likely your driver is unstable (since the encoding is done via the graphics driver).
See above to get the most stable graphics driver.

4. How do I know if MCEBuddy is using hardware acceleration

This is a two step process, first find out if your system and driver support hardware acceleration and then check if the encoder is using it.

FOR INTEL QUICKSYNC:
Open the conversion log after the conversion is complete. To check if QuickSync is supported look for the following EXACT words:
QuickSync encoding supported available ->
A True or False will tell you whether hardware encoding is being used. Right now "pure" hardware encoding is supported with QuickSync.
If your Intel QuickSync encoder is being used for encoding, in your log you will find the line
encoder: H.264 (Intel Media SDK)
OR
encoder: H.265 (Intel Media SDK)
OR
started ("H.264/AVC encoder (Intel QSV)")
OR
started ("H.265/AVC encoder (Intel QSV)")
If this line is not there then the QuickSync hardware encoder is not being used even if your driver supports it.

FOR NVIDIA NVENC:
Open the conversion log after the conversion is complete. To check if NVENC is supported look for the following EXACT words:
NVidia H.264 Hardware Encoder Detected :
NVidia H.265 Hardware Encoder Detected :
A True or False will tell you whether hardware encoding is supported by your hardware/drivers.
If your NVIDIA NVENC encoder is being used for encoding, in your log look for the words
nvenc_hevc
OR
nvenc_h264
OR
nvenc_h265
If these words are not there then the NVENC hardware encoder is not being used even if your driver supports it.

FOR OPENCL:
To check if OpenCL is support by your driver look for the exact words in the log:
OpenCL version:
If OpenCL is supported, you will need to manually enable the options (see the thread below for details) that will accelerate some functions while encoding and decoding.

5. Suddenly my encoding time is taking very long or for some video it takes a long time

Very likely your Intel driver is buggy and is causing issues. Use the recommended version in FAQ 2 and it should resolve your issues. Latest drivers are not always the most stable or faster drivers.

If you have a bugger driver, the symptoms may vary, from slow encoding to hanging the system, crashing the system or error messages in the logs. An example of a buggy driver or if you're running heavy graphics apps/games while using hardware encoding can take the wind out of the Intel driver and causing it to run out of resources, you might see things like this in the log:
2014-04-15T20:43:36 MCEBuddy.AppWrapper.Handbrake --> Encoding: task 1 of 1, 0.02 %[20:43:36] qsv_enc_init: using 'hardware (1)' implementation, API: 1.3
2014-04-15T20:43:36 MCEBuddy.AppWrapper.Handbrake --> Error code -1, av_qsv_wait_on_sync 642
2014-04-15T20:43:36 MCEBuddy.AppWrapper.Handbrake --> Error code -1, av_qsv_wait_on_sync 642
2014-04-15T20:43:36 MCEBuddy.AppWrapper.Handbrake --> Encoding: tasError code -1, av_qsv_wait_on_sync 642
2014-04-15T20:43:36 MCEBuddy.AppWrapper.Handbrake --> Encoding: task 1 of 1, 0.06 %not enough to have 10 sync point(s) allocated
2014-04-15T20:43:36 MCEBuddy.AppWrapper.Handbrake --> ERROR: qsv: Not enough resources allocated for QSV encode

6. My system crashes or my system hangs or I see many errors in my log file when I try to convert a video

See FAQ 4 above, if you driver is buggy it can cause unknown issues with your system, because the encoding is done in the video driver and the video driver runs in the kernel space it can use the system to become unstable or even crash. The best way to determine if the video driver is causing the issue is to TURN OFF hardware encoding on the Conversion Options -> Expert Settings and then see if the symptoms go away. If do they try to update to a stable driver.

7. Is OpenCL and QuickSync hardware encoding auto enabled OR I've enabled quicksync/Intel GPU in the bios but it still says QuickSync is not present?

MCEBuddy will auto detect if you have an Intel QuickSync enabled chipset and enabled QuickSync encoding.
  1. If you have an Intel chipset and another graphics card and MCEBuddy is not detecting the QuickSync, use the FakeMonitor trick (http://mirillis.com/en/products/tutorials/action-tutorial-intel-quick-sync-setup_for_desktops.html#top) to enable the Intel graphics chipset and get MCEBuddy to recognize it.
If you have OpenCL support in your driver, you will need to manually enable support for it since it's performance varies from system to system and there is no way for MCEBuddy to tell it will make the system faster or slower.
  1. If you have an older CPU like a Pentium/Core/Core 2 and good graphics card from Nvidia or ATI, then you may want to add -U the end of the handbrake-video line in the profile. This will enable hardware decoding. This ONLY works if the GPU is more powerful than the CPU, it will reduce the performance on new CPU's which are much more powerful at decoding compared to graphics cards.
  2. If you have a newer graphics card (very powerful) which supports OpenCL 1.1 then add -P to the end of the handbrake-video line in the profile. This works if you're using cropping reducing the video size (or the profile is using lookahead). Again, this will help only with a powerful graphics card with OpenCL drivers. If used on a weak graphics card it can reduce performance.
MCEBuddy cannot auto OpenCL since it is graphics card vs CPU dependent. MCEBuddy can only auto enable QuickSync if detected.

See this thread for more details: https://mcebuddy2x.codeplex.com/discussions/530808
Marked as answer by rboy1 on 6/22/2014 at 7:48 AM
Coordinator
May 11, 2015 at 5:04 PM
Edited Jul 26, 2016 at 2:03 AM

8. I have an Intel chipset, does it support QuickSync and which Chipset provides the fastest performance

So far only Intel Sandy Bridge, Ivy and Haswell chipsets support QuickSync encoding. Of the three our research has shown that Ivy Chipset is the fastest of the three.
You can find more details here:
http://www.tetrachromesoftware.com/q264Test1Analysis/q264test_4.html

Intel chipset encoding performance comparison

9. My encoding is taking a long time even with hardware acceleration enabled or my FPS appears to be slow/low

Encoding performance depends upon many factors which can impact the FPS or time taken to encode. These include:
  1. Profile being used (High Quality take more time)
  2. Profile bitrate, higher bitrates take more time
  3. Input and output resolution, HD and high resolutions take significantly longer times
  4. Your GPU and CPU are being used by other processes or you have multiple simultaneous conversions. Check your GPU and CPU utilization using the CPUZ and GPUZ tools while encoding
  5. Check your hardware chipsets being used, some chipsets are faster than others (see FAQ 7 above)
  6. Check your video driver, buggy or slow video drivers are the primary cause of slow encoding. See FAQ 2 and FAQ 4 above
  7. Sometimes OpenCL settings are incompatible and may cause a slow down in the performance if manually enabled (see FAQ 6 above)
Depending upon the above factor GPU frame rates (FPS) can vary from 25FPS to 1200 FPS which typically represent a 5x to 50x increase in comparison to non-hardware acceleration performance.

Here is a comparison of a performance comparison between hardware and non hardware encoded versions:
Image

10. What are the other stable drivers for Intel QuickSync

The other stable drivers for QuickSync we have tested are
10.18.14.4414 (this is reportedly also the faster performing driver)
These drivers have been uploaded for your convenience here:
32bit - https://www.dropbox.com/s/f9k06nxys1txbq8/win32_153631.4414.exe
64bit - https://www.dropbox.com/s/ssqejwvbt5su1kq/win64_153631.4414.exe

Install them using the Setup
.
10.18.10.3621
These drivers have been uploaded for your convenience here:
32bit - https://www.dropbox.com/s/1d8qduebpcd9p7u/Intel_Win7_8_8.1_32_10.18.10.3621.zip
64bit - https://www.dropbox.com/s/q3126ibz41j1mn3/Intel_Win7_8_8.1_64_10.18.10.3621.zip

Extract the ZIP files and install them using the Setup or manually follow the procedure given below
.
10.18.10.3379
These drivers have been uploaded for your convenience here:
32bit - https://www.dropbox.com/s/6k7rvno4705226k/Intel_10.18.10.3379_x86.zip
64bit - https://www.dropbox.com/s/8foxcvvhaganz1z/Intel_10.18.10.3379_x64.zip

These are ZIP files (taken from Windows Update CAB) and you will need to extract the files and then manually install them through the device manager.
  1. Extract the ZIP file contents into a folder (x86 or x64 depending upon your system)
  2. Open Device Manager (from Control Panel)
  3. Look for Display Adapters
  4. Expand it, (note the NAME of your graphics card you will need this in Step 12)
  5. Right click on your Intel graphics device and select "Update Driver Software"
  6. Select "Browse my computer for driver software"
  7. Select "Let me pick from a list of device drivers from my computer"
  8. Click on Have Disk
  9. Click Browse and select the folder where you extracted the file driver files in Step 1
  10. Select the setup information file "igdlh" and Click "Open"
  11. Click "OK"
  12. Select your Graphics card (see the name you noted in Step 4), name SURE you select the correct name here or it won't work
  13. Click "Next". If it gives a Update Driver Warning about "Device driver is not recommended ..." go back and select the right Device Name. Do NOT proceed with the wrong device name as it may crash your system.
  14. It'll give a warning about "Windows can't verify the publisher...", Click "Install this driver anyway"
  15. It'll install the driver, you may need to reboot
.

See these thread of more details:
https://mcebuddy2x.codeplex.com/discussions/530808
https://mcebuddy2x.codeplex.com/discussions/546041
https://mcebuddy2x.codeplex.com/discussions/548361
https://mcebuddy2x.codeplex.com/discussions/549317
https://mcebuddy2x.codeplex.com/discussions/543814
https://mcebuddy2x.codeplex.com/discussions/645486
Marked as answer by rboy1 on 5/11/2015 at 10:04 AM
Coordinator
Nov 22, 2015 at 5:41 PM
Edited Dec 5, 2015 at 7:10 AM
Thanks!
Marked as answer by rboy1 on 11/22/2015 at 10:43 AM
Feb 22, 2016 at 11:38 PM
Thanks for the detailed information - it's been quite helpful.

Any updates on the most recent stable driver for Intel QuickSync, i.e., have any later versions than 10.18.10.3958 been tested? I'm using 10.18.10.4252 and it seems to be working fine, but I wanted to check.
May 26, 2016 at 1:49 PM
Edited Jun 20, 2016 at 7:07 AM
jswartz wrote:
Thanks for the detailed information - it's been quite helpful.

Any updates on the most recent stable driver for Intel QuickSync, i.e., have any later versions than 10.18.10.3958 been tested? I'm using 10.18.10.4252 and it seems to be working fine, but I wanted to check.
I am using Windows 7 64-bit with a Intel i5-4690K CPU Overclocked @ 4.5 ghz with 16gb of ram. I have tried the three drivers in this thread (10.18.10.3958, 10.18.10.3379, 10.18.10.3621) and actually get the best performance when using the Intel 10.18.14.4414 driver: win64_153631.4414.exe (build 15.36.31.4414)

Using the MKV Normal Quality profile for my conversions with ComSkip donator, I finally got over 120fps conversions using QSV! Without QSV, I get about 20-30fps with Handbrake for either GPU or CPU encoding with the same profile.

2016-05-26T04:20:17 MCEBuddy.AppWrapper.Handbrake --> Encoding: task 1 of 1, 6.98 % (124.96 fps, avg 106.92 fps, ETA 00h07m43s)
2016-05-26T04:20:17 MCEBuddy.AppWrapper.Handbrake --> Encoding: task 1 of 1, 7.04 % (124.96 fps, avg 106.92 fps, ETA 00h07m43s)
2016-05-26T04:20:18 MCEBuddy.AppWrapper.Handbrake --> Encoding: task 1 of 1, 7.07 % (124.96 fps, avg 106.92 fps, ETA 00h07m43s)
2016-05-26T04:20:18 MCEBuddy.AppWrapper.Handbrake --> Encoding: task 1 of 1, 7.13 % (124.96 fps, avg 106.92 fps, ETA 00h07m43s)
2016-05-26T04:20:18 MCEBuddy.AppWrapper.Handbrake --> Encoding: task 1 of 1, 7.16 % (124.96 fps, avg 106.92 fps, ETA 00h07m43s)
2016-05-26T04:20:18 MCEBuddy.AppWrapper.Handbrake --> Encoding: task 1 of 1, 7.22 % (130.33 fps, avg 107.47 fps, ETA 00h07m40s)
2016-05-26T04:20:18 MCEBuddy.AppWrapper.Handbrake --> Encoding: task 1 of 1, 7.28 % (130.33 fps, avg 107.47 fps, ETA 00h07m40s)
2016-05-26T04:20:19 MCEBuddy.AppWrapper.Handbrake --> Encoding: task 1 of 1, 7.31 % (130.33 fps, avg 107.47 fps, ETA 00h07m40s)
2016-05-26T04:20:19 MCEBuddy.AppWrapper.Handbrake --> Encoding: task 1 of 1, 7.37 % (130.33 fps, avg 107.47 fps, ETA 00h07m40s)
2016-05-26T04:20:19 MCEBuddy.AppWrapper.Handbrake --> Encoding: task 1 of 1, 7.40 % (130.33 fps, avg 107.47 fps, ETA 00h07m40s)
2016-05-26T04:20:19 MCEBuddy.AppWrapper.Handbrake --> Encoding: task 1 of 1, 7.46 % (125.87 fps, avg 107.88 fps, ETA 00h07m37s)
2016-05-26T04:20:19 MCEBuddy.AppWrapper.Handbrake --> Encoding: task 1 of 1, 7.49 % (125.87 fps, avg 107.88 fps, ETA 00h07m37s)
2016-05-26T04:20:20 MCEBuddy.AppWrapper.Handbrake --> Encoding: task 1 of 1, 7.52 % (125.87 fps, avg 107.88 fps, ETA 00h07m37s)
I also am trying the Intel Graphics and SDK driver that is installed with Intel Media Server Studio 2016 – Community Edition. This package installs a similar driver to the log file above: 10.18.14.4371 I will let you know my results compared with the above test.

------ UPDATE ------

Both drivers work well (100+ fps conversions with QSV), but I find the 10.18.14.4371 version provided by the Intel Media Server Studio 2016 – Community Edition is most stable and does not require the fake monitor hack.

------ Second UPDATE ------

The conversions do work more reliably if you have a HDMI or EDID Emulator (aka headless device) in your Intel HDMI port. I use this device from amazon: fit-Headless 4K
Oct 17, 2016 at 1:36 PM
Edited Oct 21, 2016 at 1:16 PM
Another issue I found with Intel QuickSync is if you RDP (Remote Desktop) into the machine, QuickSync is disabled. In order to resolve this, you need to run the following command to disconnect the RDP connection and re-enable the local console login. Remember to replace HTPC in the first command below to your default user account name:
@powershell -NoProfile -ExecutionPolicy unrestricted -Command "$sessionid=((quser HTPC | select -Skip 1) -split '\s+')[2]; tscon $sessionid /dest:console" 2> UnlockErrors.log
exit
I was then able to save that command to a bat file named UnlockScreen.bat in my C:\Tasks\ folder. I lastly added the command to my profiles.conf:
PreCustomCommandPath=C:\Tasks\ForceConsole.bat
PreCustomCommandParameters=
PreCustomCommandHangPeriod=60
PreCustomCommandCritical=false
PreCustomCommandUISession=true
PreCustomCommandShowWindow=false
PreCustomCommandExitCodeCheck=false
Nov 5, 2016 at 2:55 PM
I have a new Dell Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz, running MCEBuddy v2.4 beta 6. This has a passmark score close to 10000. When MCEBuddy 2.4 beta 6 (Windows 10 Pro) is processing using Comskip Donator, the computer runs real hot and the fan sounds like a freight train. MCEBuddy logs say I have hardware acceleration but the Handbrake portion of the logs report errors that indicate it may not be using hardware acceleration because of admin login privileges not right:

2016-11-05T01:07:45 MCEBuddy.AppWrapper.Handbrake --> Starting process as a UISession process with Admin privileges. This requires at least 1 user to be logged into the system (remote desktop or locally)
ERROR> 2016-11-05T01:07:45 --> StartAppWithAdminPrivilegesFromNonUISession WTSQueryUserToken failed (No logged on users) with error 1008. An attempt was made to reference a token that does not exist.

WARNING> 2016-11-05T01:07:45 MCEBuddy.AppWrapper.Handbrake --> Unable to create UI Session process with Admin Privileges from NonUI Session. Is any user logged on?
WARNING> 2016-11-05T01:07:45 MCEBuddy.AppWrapper.Handbrake --> Retrying process creation as a NonUI Session process with Admin privileges
WARNING> 2016-11-05T01:07:45 MCEBuddy.AppWrapper.Handbrake --> Some functions like hardware encoding may not work in this mode

Some other details:

2016-11-05T01:07:46 MCEBuddy.AppWrapper.Handbrake --> [01:07:46] CPU: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
2016-11-05T01:07:46 MCEBuddy.AppWrapper.Handbrake --> [01:07:46] - Intel microarchitecture Skylake
2016-11-05T01:07:46 MCEBuddy.AppWrapper.Handbrake --> [01:07:46] - logical processor count: 8
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] OpenCL device #1: Intel(R) Corporation Intel(R) HD Graphics 530
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - OpenCL version: 2.0
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - driver version: 10.18.15.4279
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - device type: GPU
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - supported: YES
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] Intel Quick Sync Video support: yes
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - Intel Media SDK hardware: API 1.16 (minimum: 1.3)
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - H.264 encoder: yes
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - preferred implementation: hardware (any)
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - capabilities (hardware): breftype icq+la+i+downs vsinfo opt1 opt2+mbbrc+extbrc+trellis+ib_adapt+nmpslice
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - H.265 encoder: yes

full log: ftp://mcebuddy@files.mcebuddy2x.com/upload/permission-problem/The Tonight Show Starring Jimmy Fallon (2014) - S04E30 - Dana Carvey; Alicia Keys; Young M.A.ts-Convert to MKV Normal Quality-2016-11-05T00-56-03.7107595-06-00.log

I have not tried JoshDi fix above -- I do RDP to this machine, but was not connected to it last night when I heard this fan noise and started to investigate.

When I look at the MCEBuddy service logon properties, logon as "Local System Account" is selected, but I have the choice to logon with a specific user account... should I be doing that instead, being sure it is an admin account?

Any help appreciated.
Nov 5, 2016 at 7:13 PM
I have an i5-2500 using the Intel HD Graphics 2000 (I think this is referred to as 2nd generation). I tried a couple days ago to update the existing graphics driver 9.17.10.4229 to something more recent as suggested in a sticky or another FAQ. This seems to be the highest driver version available for my hardware. I downloaded the suggested driver from intel and it installed the same version. I tried another one from intel and the one linked to in point 2 above and they both gave errors saying "This system doesn't meet the minimum requirements....".
Nov 7, 2016 at 10:48 PM
eskimoquin wrote:
I have an i5-2500 using the Intel HD Graphics 2000 (I think this is referred to as 2nd generation). I tried a couple days ago to update the existing graphics driver 9.17.10.4229 to something more recent as suggested in a sticky or another FAQ. This seems to be the highest driver version available for my hardware. I downloaded the suggested driver from intel and it installed the same version. I tried another one from intel and the one linked to in point 2 above and they both gave errors saying "This system doesn't meet the minimum requirements....".
yes, that is true. In your case, I would use the latest driver available for your processor.
Nov 7, 2016 at 10:58 PM
kschroll wrote:
I have a new Dell Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz, running MCEBuddy v2.4 beta 6. This has a passmark score close to 10000. When MCEBuddy 2.4 beta 6 (Windows 10 Pro) is processing using Comskip Donator, the computer runs real hot and the fan sounds like a freight train. MCEBuddy logs say I have hardware acceleration but the Handbrake portion of the logs report errors that indicate it may not be using hardware acceleration because of admin login privileges not right:

2016-11-05T01:07:45 MCEBuddy.AppWrapper.Handbrake --> Starting process as a UISession process with Admin privileges. This requires at least 1 user to be logged into the system (remote desktop or locally)
ERROR> 2016-11-05T01:07:45 --> StartAppWithAdminPrivilegesFromNonUISession WTSQueryUserToken failed (No logged on users) with error 1008. An attempt was made to reference a token that does not exist.

WARNING> 2016-11-05T01:07:45 MCEBuddy.AppWrapper.Handbrake --> Unable to create UI Session process with Admin Privileges from NonUI Session. Is any user logged on?
WARNING> 2016-11-05T01:07:45 MCEBuddy.AppWrapper.Handbrake --> Retrying process creation as a NonUI Session process with Admin privileges
WARNING> 2016-11-05T01:07:45 MCEBuddy.AppWrapper.Handbrake --> Some functions like hardware encoding may not work in this mode

Some other details:

2016-11-05T01:07:46 MCEBuddy.AppWrapper.Handbrake --> [01:07:46] CPU: Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
2016-11-05T01:07:46 MCEBuddy.AppWrapper.Handbrake --> [01:07:46] - Intel microarchitecture Skylake
2016-11-05T01:07:46 MCEBuddy.AppWrapper.Handbrake --> [01:07:46] - logical processor count: 8
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] OpenCL device #1: Intel(R) Corporation Intel(R) HD Graphics 530
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - OpenCL version: 2.0
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - driver version: 10.18.15.4279
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - device type: GPU
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - supported: YES
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] Intel Quick Sync Video support: yes
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - Intel Media SDK hardware: API 1.16 (minimum: 1.3)
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - H.264 encoder: yes
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - preferred implementation: hardware (any)
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - capabilities (hardware): breftype icq+la+i+downs vsinfo opt1 opt2+mbbrc+extbrc+trellis+ib_adapt+nmpslice
2016-11-05T01:07:47 MCEBuddy.AppWrapper.Handbrake --> [01:07:47] - H.265 encoder: yes

full log: ftp://mcebuddy@files.mcebuddy2x.com/upload/permission-problem/The Tonight Show Starring Jimmy Fallon (2014) - S04E30 - Dana Carvey; Alicia Keys; Young M.A.ts-Convert to MKV Normal Quality-2016-11-05T00-56-03.7107595-06-00.log

I have not tried JoshDi fix above -- I do RDP to this machine, but was not connected to it last night when I heard this fan noise and started to investigate.

When I look at the MCEBuddy service logon properties, logon as "Local System Account" is selected, but I have the choice to logon with a specific user account... should I be doing that instead, being sure it is an admin account?

Any help appreciated.
QSV will not work if the last console session was an RDP session, even if you are not currently RDP'ed into the machine. QSV will start working the second a local user logs into the machine. The script I posted above disconnects the RDP session and restores the console (its the same as logging in from the lock screen). Obviously, you need to have AutoLogin enabled.

I looked at your Jimmy Fallen log... you were getting 129.19 fps avg and the entire conversion only took 23:23 minutes. I can confirm that QSV is working on your machine and was working for this conversion log you posted.

Depending on the individual show's quality and format, will depend on how fast QSV can convert the video. I typically get over 100fps for all conversions and even close to 200fps for lower quality WTV files. Rarely handbrake does not like certain WTV files, which causes QSV to not work and the video only converts at 20-40 fps - even more rarely, handbrake totally fails and MCEBuddy falls back to FFMPEG

I find that MCEBuddy with QSV enabled can convert a 40 minute (60 minute show without commercials) 1080i wtv show to the MKV Normal Quality format with a 20% QSV quality boost in less than 25 minutes.
Nov 8, 2016 at 2:01 AM
Thanks Josh. I appreciate your taking a look at my logs. This computer, keyboard and mouse are in a semi-public space where someone could interact with it. Does your script mean that someone can turn the monitor on and start using the computer without logging in as your script leaves the user logged in? Can the screen saver lock while leaving the local user logged in so QSV will work If not, I suppose that I could unplug the monitor to prevent access (the computer is in a locked cabinet).
Nov 8, 2016 at 4:29 AM
kschroll wrote:
Thanks Josh. I appreciate your taking a look at my logs. This computer, keyboard and mouse are in a semi-public space where someone could interact with it. Does your script mean that someone can turn the monitor on and start using the computer without logging in as your script leaves the user logged in? Can the screen saver lock while leaving the local user logged in so QSV will work If not, I suppose that I could unplug the monitor to prevent access (the computer is in a locked cabinet).
If the Screensaver activates the lock screen, then QSV will not work.

The script just unlocks the console if there is no password or auto login is enabled.

QSV will only work as well if the computer thinks there is a monitor installed via the Intel graphics card. For my machines I have an EDID emulator to fake my TV to the machine so that it always thinks the monitor is on, even though it is only on when someone is watching TV.
Nov 10, 2016 at 11:17 PM
Thanks. I got an EDID emulator today and will give that a shot.
Nov 14, 2016 at 1:48 AM
kschroll wrote:
Thanks. I got an EDID emulator today and will give that a shot.
sounds good. let me know how it works out.
Nov 30, 2016 at 8:08 PM
Sorry for the n00b question - but I just want to better understand what i have to do to set this up.

I have an nVidia 1060 graphics card, and I believe it should support this. I have the latest driver installed, but it seems I need to install the CUDA toolkit for this to work.

Once I install the CUDA toolkit, will this just automatically run? Otherwise what other steps do I need to do?

Thanks -
Coordinator
Dec 1, 2016 at 1:58 PM
That's it, nothing else to do make sure you're using a ffmpeg based profile and it'll automatically pick it up