search

jellyfin / jellyfin-media-player

Jellyfin Desktop Client
GNU General Public License v2.0
2.87k stars 297 forks source link

Forced transcoding on new update 1.11.0 - no direct play #687

Open deanrobin333 opened 3 weeks ago

deanrobin333 commented 3 weeks ago

I have been using media-player just fine and it has been playing media files directly without transcoding, up to version 1.10.1. But after upgrading to version 1.11.0, CPU usage went through the roof and then I noticed, every video is now being transcoded, while before it did not.

Why is this happening now in the new version 1.11.0? I downgraded back to version 1.10.1 and media is now playing direct without transcoding.

am using jellyfin on ubuntu 24.04 Noble.

vincejv commented 3 weeks ago

what's the transcode reason? can't reproduce on Ubuntu 22

Echtze1t commented 3 weeks ago

My issue is similar, so I'm posting my log file here (Windows 10). Before the latest two updates, h.265 content was played via direct play. Now it's not playing at all (I have disabled transcoding, because it was never necessary before and I prefer to keep it that way).

Log.bib.txt

Edit: This shit is getting on my nerves. The last two updates have been horrible. I'm reverting back to 1.10.1 (AGAIN).

MagicTeePee commented 3 weeks ago

Same issue for me, as soon as I updated I disabled transcoding server-side and nothing at all can be played on my client anymore, wether h265 or h264: "This client isn't compatible with the media and the server isn't sending a compatible media format." Jellyfin Media Player 1.11.1 on Windows 11 23H2

Here are the server logs jellyfin_forced_transcode.txt

I did not force transcode in the client settings

No issues when reverting to 1.10.1

MrOscarvs commented 3 weeks ago

I got this problem too after updating. I think it's fixed if you disable "Force Transcode Dolby Vision" in Client Settings. I also have every "Force Transcode..." option disabled. Please confirm if this solves it for you.

MagicTeePee commented 2 weeks ago

I got this problem too after updating. I think it's fixed if you disable "Force Transcode Dolby Vision" in Client Settings. I also have every "Force Transcode..." option disabled. Please confirm if this solves it for you.

I reinstalled 1.11.1, the "Force Transcode Dolby Vision" client option was indeed enabled by default but disabling it did not solve the issue, I still get the playback error.

This was the only enabled transcode option.

athfrith commented 2 weeks ago

Verified. Even with server 10.9.6 this bugs out for me and force transcodes all X265 (HEVC) media even though my desktop machine can locally HW accelerate x265 media.

Using Ubuntu Desktop 24.04.

Downgrading Jellyfin Media Client from 1.11.1 to 1.10.1 fixes the issue. No more transcoding.

larkwiot commented 2 weeks ago

Think I'm having this issue too

deanrobin333 commented 2 weeks ago

I got this problem too after updating. I think it's fixed if you disable "Force Transcode Dolby Vision" in Client Settings. I also have every "Force Transcode..." option disabled. Please confirm if this solves it for you.

@MrOscarvs even if you do that, it doesn't solve it. I went on a rampage of changing several settings, but the new update is forcing transcoding. So if you disable transcode for a particular user it will not play the media.

I wonder why this is happening, and yet it was working perfectly before.

What I did notice though is before, if you played media from the web browser directly, it would force transcoding. Hence why I loved using the jellyfin media player app. However now with this update they mentioned something about integrating it with the web so that updates are immediate, however this has also made it acquire the quirks of forced transcoding that happened when you played via the media browser.

For now using version 1.10 works; I will probably stick to this until this issue is addressed.

MagicTeePee commented 4 days ago

Same issue for me, as soon as I updated I disabled transcoding server-side and nothing at all can be played on my client anymore, wether h265 or h264: "This client isn't compatible with the media and the server isn't sending a compatible media format." Jellyfin Media Player 1.11.1 on Windows 11 23H2

Here are the server logs jellyfin_forced_transcode.txt

I did not force transcode in the client settings

No issues when reverting to 1.10.1

I replicated the issue on a second computer also running windows 11 23h2 with JellyFin Media Player 1.11.1

I also started a fresh 10.9.7 jellyfin windows server on that computer, disabled transcoding for the newly created account, and I get the exact same error.

JellyLog.txt JellyLog2.txt

MysteriousLounger commented 1 day ago

hi, I am also experiencing forced transcoding after upgrading to 10.9.6. My server is running bare-metal on Debian 12. In my case the target device is a chromecast. All video is transcoded, including those already in h264. changing client settings had no effect. Like others have reported, I have also tried disabling transcoding server-side for the user in question, and indeed, video fails to play [although audio works, and the content 'plays' with a black screen]. My logs look very similar to those already posted here, but if they would be useful, please let me know and I can sanitize and post them. hope this can be fixed soon, although I unfortunately don't have the time or skills to see to it myself...

marvin8 commented 1 day ago

Have you all tried setting Home network quality in the Playback settings to something close to your network speed or to just anything other than Auto.

Doing so seems to have improved this for me.

jjames55 commented 1 day ago

Same here.

Infuse on iPhones and Apple TVs plays everything without problems!

I have transcoding disabled on the server, as my server is a sinology with no hardware acceleration for media stuff. Also all clients can easily decode even 4K without breaking a sweat.

The new client fails on most files, as does the built-in web player. Using Edge seems to be marginally better, it is able to play a few more files than chrome.