Jellyfin Forum
SOLVED: High cpu usage with hw accelaration qsv - Printable Version

+- Jellyfin Forum (https://forum.jellyfin.org)
+-- Forum: Support (https://forum.jellyfin.org/f-support)
+--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting)
+--- Thread: SOLVED: High cpu usage with hw accelaration qsv (/t-solved-high-cpu-usage-with-hw-accelaration-qsv)

Pages: 1 2


High cpu usage with hw accelaration qsv - Gtu785696 - 2024-08-31

Hey there im getting almost 100% CPU usage with hardware transcoding a single 4k hdr file to sdr 1080p.

I have enabled QSV & and its working verified with intel_gpu_top & as well as logs, cleaned up the file to remove the subtitles, changed hdr tonemapping algorithm to mobius but nothing seems to be working.

I have hp prodesk 600 g4 with i3 8100t. Should be transcoding multiple files at the same time as per my research.

Have attached logs & screenshots. Any help would be much appreciated

Also why is it even transcoding hevc to h264 when my client (Galaxy s23) can handle it well ?


RE: High cpu usage with hw accelaration qsv - nyanmisaka - 2024-08-31

The QSV hardware decoder is not enabled.


RE: High cpu usage with hw accelaration qsv - Gtu785696 - 2024-08-31

(2024-08-31, 07:37 AM)nyanmisaka Wrote: The QSV hardware decoder is not enabled.

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

This from ffmpeg log means its transcoding right ?


RE: High cpu usage with hw accelaration qsv - Fate - 2024-08-31

(2024-08-31, 07:39 AM)Gtu785696 Wrote:
(2024-08-31, 07:37 AM)nyanmisaka Wrote: The QSV hardware decoder is not enabled.

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

This from ffmpeg log means its transcoding right ?
Well, yes it means the encoding to h264 is using the iGPU

But that is not the only CPU intensive task. To be able to encode it needs to decode the existing file.
By the log you posted it is  HEVC 10bit HDR content. 
So do you have hardware decoding enabled for HEVC 10bit in jellyfin?

Even if you have it enable the file is HDR so it needs to have the Tonemapping done via software since hardware tonemapping is not supporting in Coffeelake CPU.


RE: High cpu usage with hw accelaration qsv - nyanmisaka - 2024-08-31

(2024-08-31, 10:42 AM)Fate Wrote:
(2024-08-31, 07:39 AM)Gtu785696 Wrote:
(2024-08-31, 07:37 AM)nyanmisaka Wrote: The QSV hardware decoder is not enabled.

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

This from ffmpeg log means its transcoding right ?
Well, yes it means the encoding to h264 is using the iGPU

But that is not the only CPU intensive task. To be able to encode it needs to decode the existing file.
By the log you posted it is  HEVC 10bit HDR content. 
So do you have hardware decoding enabled for HEVC 10bit in jellyfin?

Even if you have it enable the file is HDR so it needs to have the Tonemapping done via software since hardware tonemapping is not supporting in Coffeelake CPU.

We support OpenCL-based tone mapping for KabyLake and newer iGPUs. Coffeelake is no exception.


RE: High cpu usage with hw accelaration qsv - Fate - 2024-08-31

(2024-08-31, 10:55 AM)nyanmisaka Wrote: We support OpenCL-based tone mapping for KabyLake and newer iGPUs. Coffeelake is no exception.

Totally forgot about the OpenCL fallback ^^


RE: High cpu usage with hw accelaration qsv - nyanmisaka - 2024-08-31

(2024-08-31, 11:02 AM)Fate Wrote:
(2024-08-31, 10:55 AM)nyanmisaka Wrote: We support OpenCL-based tone mapping for KabyLake and newer iGPUs. Coffeelake is no exception.

Totally forgot about the OpenCL fallback ^^

VPP tonemap is also supported on KabyLake+. The only exceptions are Jasper Lake and some Gemini Lake processors.


RE: High cpu usage with hw accelaration qsv - Gtu785696 - 2024-08-31

Hey guys

When i enabled decoding for hevc it seems to be working (hevc 10bit was already enabled). Now the cpu usage sits around 30%.

But why is it encoding to h264 when my client can handle h265 is it the issue with the android app ? Tried exoplayer also.


RE: High cpu usage with hw accelaration qsv - TheDreadPirate - 2024-08-31

Did you enable HEVC encoding?

"Allow encoding in HEVC format".

   


RE: High cpu usage with hw accelaration qsv - Gtu785696 - 2024-08-31

(2024-08-31, 03:12 PM)TheDreadPirate Wrote: Did you enable HEVC encoding?

"Allow encoding in HEVC format".

Yes its enabled.