Quicksync Apollo Lake Windows 10 not working, CPU fallback

[fightforlife 1]

Maybe you should give the user a check box to activate or deactivate this option for encoding and decoding. (seperately?)

Not every GPU is able to user the HW plugin. Or you check the generation of the cpu and automotically assign the correct command.

[Luke 40079]

Well i guess the question would be why even support the software version?

[fightforlife 1]

If you want i can try a preview version?

[Luke 40079]

Yes the changes are in the beta server. Thanks.

[fightforlife 1]

I updated my server. The test file is working fine.  Speeds around 3x-7x transcoding.

 

Some other files are not working and transcoding still falls back to cpu.

I will post some log files, in the next days

 

Thanks!

[Luke 40079]

The beta server has some nice improvements for NVENC transcoding, for those interested:

 

https://emby.media/community/index.php?/topic/56088-slow-hardware-decode-with-hevc-and-nvidia-p4000/?p=548844

 

Thanks.

[fightforlife 1]

Could it be, that this change got reversed?

 

I just tried emby beta on windows again, and it isnt working anymore?

 

It should say:

Stream mapping:
Stream #0:0 -> #0:0 (hevc (hevc_qsv) -> h264 (h264_qsv))

but it does say:

Stream mapping:
Stream #0:0 -> #0:0 (hevc (native) -> h264 (h264_qsv))
Stream #0:1 -> #0:1 (copy)

/ffmpeg -y -c:v hevc_qsv -load_plugin hevc_hw -i video-h265.mkv -an -c:v h264_qsv out.mp4

 

The load plugin parameter is also missing in the transcode log.

 

Thanks in advance!

 

 

 

 

edit:

 

I found this thread where the same problem is mentioned on the last page.

There you decide to use DXVA2 insted of the QSV decode for HEVC.

https://emby.media/community/index.php?/topic/58388-hevc-x265-quicksync-hardware-transcoding-not-working/page-5

 

Is it somehow possible to modify the fmpg parameters on my installation to use hevc_hw plugin isntead?

The qsv performce is much better. with the current dxva2 option my cpu is going straight to 100% while the GPU stays at 20%.

Edited October 23, 2018 by fightforlife

[Luke 40079]

At some point along the way we removed that param due to it causing problems.

[fightforlife 1]

my edit from above (didnt see your response):

 

I found this thread where the same problem is mentioned on the last page.

There you decide to use DXVA2 insted of the QSV decode for HEVC.

https://emby.media/c...-working/page-5

 

Is it somehow possible to modify the ffmpg parameters on my installation to use hevc_hw plugin isntead?

The qsv performce is multiple times better. With the current dxva2 option my cpu is going straight to 100% while the GPU stays at 20%.

[Luke 40079]

It's not possible, no. We can look at using QSV once we're able to get it working for all machines. Thanks.

[fightforlife 1]

This is sad. Emby is not usable with hevc on apollo lake (J3455, windows).

 

Is there no way to implement a switch "Force QSV (experimanteal)" under Transcoding->Advanced only in Beta Channel?

(As you can see in the other thread I am not the only one affected)

[Carlo 4552]

Either Emby needs to interrogate the GPU and build up a list of options to use based on the GPU and the command lines used or we should have some options that can be set.

 

If using QSV and HEVC "-load_plugin hevc_hw" can make a world of difference for those who can use it.  This is a perfect "advanced option" to have available.

[Luke 40079]

We will improve this in the future. Thanks.

[Carlo 4552]

Sounds great Luke!

[Bigjohns97 4]

Is there anyway to set this outside of the Emby settings?

 

I have a 9700k so i have the power to handle this but i would rather use Hardware encoding if possible.

[Luke 40079]

To set what exactly outside of emby settings?