-
-
Notifications
You must be signed in to change notification settings - Fork 495
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.17.x fire TV 1st gen HEVC support claimed but unsupported? #3842
Comments
Edit: My mistake... that 0.17.0 doesn't include that rewrite, |
I've also noticed the timestamp skips (despite the audio being perfect) incase that's a useful clue... It reliably goes 00:00, 00:02, 00:05, 00:08, 00:11 ... |
I just found some other media which direct plays but skips... 1 frame every few seconds... I believe this media worked correctly on the previous fire tv 0.16 release: Video |
Going back to the original video... unchecking "Allow encoding in HEVC format" & "Allow encoding in AV1 format" on the server (and so defaulting to h264?) slightly changes the result: The audio still works fine, but after ~5 seconds I see a single image frame which then skips to a new frame each few seconds... |
Direct play media have the same issue, ffmpg just quits ([q] command received. Exiting.). Works fine from other clients. Updated to latest server version just to make sure, still same behaviour. |
Updated to 0.17.1 and see the same issues. |
Seems something to do with HEVC. The following media shows the same black screen symptoms while being transcoded
... Until I deselect "Allow encoding in HEVC format" on the server after which the playback performs flawlessly. (The media from my original post plays back with ~3s between frames with this configuration) |
https://developer.amazon.com/docs/fire-tv/device-specifications-comparison-table.html then points out that my fire TV 1st gen doesn't support HEVC/h265... which starts to explain the issue! I'm guessing jellyfin is claiming HEVC support and the server obliges, leading to the failure scenarios above. |
Curiouser and curiouser... I was playing around with my own build and forced I swapped back to the fire tv store build and noticed that Commenting out this line sees everything work correctly, with only h264 requested:
|
@nielsvanvelzen I'm struggling to follow the code at this point. I think this is a pretty solid lead though from my latest comment - that jellyfin-androidtv is correctly seeing the lack of HEVC support and logging as such. And yet a HEVC transcode is still requested of the server? Please is there any chance you could give me a pointer to support debugging this further? |
So now looking at |
https://github.com/jellyfin/jellyfin-androidtv/compare/release-0.17.z...PriceChild:jellyfin-androidtv:fire-tv-1-disable-hevc?expand=1 implements a naughty disabling of hevc transcoding specifically for the 1st Gen Fire TV which isn't ideal... Weirdly, although video is now transcoded perfectly with "downmix to stereo" checked, when asking for direct pass through of eac3, the audio is perfect 5.1 but video stutters.
On the contrary, AAC files are always being downmixed to stereo:
Given that this at least provides a path on 0.17.x to working picture+audio (Even if it's not the right way to fix it, and doesn't fix 5.1) I'll open a MR... |
Describe the bug
After updating to 0.17.0 I initially found the player refusing to start.
I noticed that my server was still configured to VAAPI and updated it to QSV. After that change, the 5.1 audio is passed through perfectly to my AVR but the screen is simply black with the usual playback controls. Modifying the Mbit/s makes no difference.
Transcoding works perfectly for my other clients.
Logs
NA
FFmpeg logs
Media info of the file
Application version
0.17.0
Device information
1st-Gen Fire TV (CL1130)
Android version
Fire OS 5.2.7.4 (656639420)
Jellyfin server version
10.9.8
The text was updated successfully, but these errors were encountered: