Help getting started with QuickSync

[Michael K. 24]

I've enabled Intel QuickSync hardware acceleration. When Emby transcodes it appears to be using the CPU and not the Intel HD Graphics 630. I'm judging this by watching the Performance tab in Windows Task Manager.

 

The CPU is Intel Core i7-7700

 

The log files are attached.

 

Am I missing something to get QuickSync enabled? Please advise, thanks!

server_Log.txt

transcode_Log.txt

[Guest asrequested]

There are improvements to how this works, in the next sever release. I'd suggest waiting until that arrives, or try the latest beta. You could also try disabling decoding.

Stream mapping:
  Stream #0:0 -> #0:0 (hevc (hevc_qsv) -> h264 (h264_qsv))
  Stream #0:1 -> #0:1 (truehd (native) -> ac3 (native))

[Luke 42080]

Does your hardware support hevc decoding?

[Michael K. 24]

Does your hardware support hevc decoding?

 

I believe so. The playback device is an Apple TV 4K which according to the specs supports the following:

 

1. H.264/HEVC SDR video up to 2160p, 60 fps, Main/Main 10 profile

2. HEVC Dolby Vision (Profile 5)/HDR10 (Main 10 profile) up to 2160p

 

The Emby server has Intel HD Graphics 630, on which I've enable decoding and encoding, so I would think the Apple TV should be receiving a compatible stream from the Emby server.

 

Is there another piece of hardware that I need to check for HEVC support?

Edited October 9, 2018 by Michael K.

[Happy2Play 9781]

Looking at you log decoding failed that it fell back and didn't use qsv at all.  I would test only enabling encoding. to see if it work.

 

Error while decoding stream #0:0: Function not implemented
Conversion failed!

 

Stream mapping:
  Stream #0:0 -> #0:0 (hevc (native) -> h264 (libx264))
  Stream #0:1 -> #0:1 (truehd (native) -> ac3 (native))

 

Are your drivers up to date?

Edited October 9, 2018 by Happy2Play

[Michael K. 24]

Are your drivers up to date?

 

Yes, I checked and updated to the latest drivers just before starting this thread.

Version 25.20.100.6323

Date 2018-09-20

 

 

 I would test only enabling encoding. to see if it work.

 

I just tested with only encoding enabled, but I got the same result - I saw activity only on the CPU, not the GPU. Log files attached.

server_Log.txt

transcode_Log.txt

Edited October 9, 2018 by Michael K.

[Guest asrequested]

Looks like your flavor of HEVC isn't supported.

Stream mapping:
  Stream #0:0 -> #0:0 (hevc (native) -> h264 (h264_qsv))
  Stream #0:1 -> #0:1 (truehd (native) -> ac3 (native))
Press [q] to stop, [?] for help
[h264_qsv @ 000001d9587e0a00] Current pixel format is unsupported
[h264_qsv @ 000001d9587e0a00] some encoding parameters are not supported by the QSV runtime. Please double check the input parameters.
Error initializing output stream 0:0 -- Error while opening encoder for output stream #0:0 - maybe incorrect parameters such as bit_rate, rate, width or height
Conversion failed!

[Michael K. 24]

Looks like your flavor of HEVC isn't supported.

 

Interesting, I think the bitrate is too high or the combination of bitrate and resolution is too much. I will run some tests with various content.

 

I also have a new Core-i7 8700 and it's labeled with Intel UHD Graphics 630 - most of the specs look the same, but perhaps it can handle UHD better. We'll see.

 

I was looking at the log as well, but I'm not too good at interpreting it... appreciate you looking into it and providing the snippets. Very helpful!

[Michael K. 24]

Looks like your flavor of HEVC isn't supported.

 

Can you tell me, is that not supported by ffmpeg or QuickSync?

[Guest asrequested]

Can you tell me, is that not supported by ffmpeg or QuickSync?

 

Well, ffmpeg has to correctly tell your GPU what's required, the GPU takes it from there. I have that same processor, and I think in this case, it might just be the ffmpeg params need tweaking. Unfortunately, my i7 7700 is in my HTPC, so I can't test what you're trying. I thought this had all been hashed out, a while back. What chipset are you using?

 

Luke, the adjustments in the beta with the dxva2, might they correct this? I know the decoding should work better, but any adjustments with QS params? 

[Luke 42080]

The beta will just do a better job of not failing when something isn't supported.

[Guest asrequested]

The beta will just do a better job of not failing when something isn't supported.

 

Meaning it'll fall back on CPU, or try a different decoder/encoder?

Edited October 9, 2018 by Doofus

[Luke 42080]

fallback.

[Michael K. 24]

What chipset are you using?

 

The chipset is Intel Z270 (ASRock Z270 Taichi motherboard)

[Guest asrequested]

That's fine. It's a curious one. It may just be a new format that it doesn't support.