Transcoding above certain quality fails

[pear235 4]

Hello,

 

I'm having a weird issue playing 4k hdr files - namely, when i select the quality to auto (or any other above, in this case, 1080 30mbit), the file starts playing, then after 5 - 10 seconds it flashes to black, then the playback is stopped with "No compatible streams are currently available. Please try again later or contact your system administrator for details."

 

This is on a local, wired, 1gbit connection so no network bottleneck. The same file plays completely fine on Plex and Jellyfin.

Emby's running on lxc in Proxmox.

Hardware - i5-14500  with 8GB ram and 6 cores, a310 used for transcoding. Same happens when using the igpu. Emby version 4.9.1.18 beta, but same happened with 4.8.10 an 4.8.11. 

I tried to test it using completely new installation, same behaviour. What i noticed is that when using Edge, this happens, whereas when using Firefox it doesn't - although then the tone mapping isn't working. Trying with Edge in safe mode, with all addons / plugins disabled doesn't help.

With tone mapping completely disabled, the issue still remains.

 

Any ideas? 

 

embyserver.txt ffmpeg-transcode-5a32a0ad-ab22-447a-bfc5-693c12b10f1b_1.txt ffmpeg-transcode-a102c447-9301-48ef-b7b5-77f12d1f586e_1.txt ffmpeg-transcode-ecd5ed8f-52e1-4c5a-8c02-d987e08bb33c_1.txt hardware_detection-63891271590.txt

Edited August 20, 2025 by pear235

[Luke 42077]

Hi, can you try resetting your diagnostics changes back to default? Thanks.

[pear235 4]

Hello @Luke, thanks for taking your time to look into this.

 

I disabled all enabled options in diagnostics plugin, then uninstalled the plugin for good measure and restarted emby service. Still the same behaviour unfortunately.

 

I noticed that for some reason, during one test play, three transcoding logs are generated, as it it was stopping completely and restarting. Similarily, when testing, i can see that the play progress resets: 00:07 -> 00:00, then jumps immediately back to 00:07 and so on.

 

hardware_detection-63891285116.txt embyserver.txt ffmpeg-transcode-c799e3a0-1689-4354-b66c-75bca8f60987_1.txt ffmpeg-transcode-01fe5aee-f179-4e46-b046-378722daa627_1.txt ffmpeg-transcode-13eeb4ed-74c0-4327-9a12-3d4d15013301_1.txt

Edited August 20, 2025 by pear235
additional info

[Happy2Play 9780]

No idea what parameter the other guys are using but Emby is taking that 26Mbps HEVC file and converting it into a almost 40Mbps H264.

Also don't know how this affects it also.

Quote

>>>>>  Non-Default Encoder Parameters
Warning EncoderParametersH264Qsv.Preset: Original:  Actual: slower
Warning EncoderParametersH264Qsv.LowPowerEncoding: Original: False Actual: True

 

[pear235 4]

1 hour ago, Happy2Play said:

No idea what parameter the other guys are using but Emby is taking that 26Mbps HEVC file and converting it into a almost 40Mbps H264.

Also don't know how this affects it also.

 

Yea i had it set in the H264 encoder settings :

 

Still, after setting it back to default just now, transcoding still isn't working

[pear235 4]

Update - after updating to 4.9.1.20, issue persists.

[pear235 4]

Hey @Luke, do you have any ideas? 

 

[Luke 42077]

On 8/22/2025 at 1:45 AM, pear235 said:

Hey @Luke, do you have any ideas? 

 

Hi, can you please provide a new log example from the latest build? Thanks.

[pear235 4]

Hello, of course: 

 

ffmpeg-transcode-cca01619-9d7d-4fdf-bd8e-9f20aae7f4e2_1.txt hardware_detection-63891700809.txt ffmpeg-transcode-32877d6d-4511-4903-9985-c5a5d417164c_1.txt ffmpeg-transcode-99179dde-4843-454d-81dd-2af54eb14439_1.txt ffmpeg-transcode-c26b7050-f6ee-4e99-afc1-63681a3488a1_1.txt ffmpeg-transcode-0d55faf3-2c0d-4dca-b80c-829a13e51f1b_1.txt embyserver.txt

[Luke 42077]

@pear235are you still having an issue with this on the latest build?