![]() |
SOLVED: Successful transcodes in browser, but not on other devices - 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: Successful transcodes in browser, but not on other devices (/t-solved-successful-transcodes-in-browser-but-not-on-other-devices) |
Successful transcodes in browser, but not on other devices - abaxi - 2024-01-31 I'm running into an issue where Jellyfin does not kick off a transcode job for AV1 files when streamed to certain clients like my Chromecast and jellyfin-web-player desktop applications. I have verified that hardware transcoding is enabled and working for the AV1 codec when streaming from a Firefox browser. But when I try to stream the same video file to a Chromecast or desktop jellyfin-media-player app, no transcode takes place. I know this because no transcode log appears in the log dashboard after terminating playback. I have svt-av1 installed in the container and av1 codec libraries present on the proxmox host. Here's a log of the playback events when streaming from the Chromecast: Code: [2024-01-30 17:31:16.442 -06:00] [INF] User policy for "User". EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True I'm not exactly sure why it would transcode when streaming to the browser but not elsewhere, as the Chromecast 4K and my desktop clients do not support AV1. Server Setup:
Chromecast 4K Client:
RE: Successful transcodes in browser, but not on other devices - TheDreadPirate - 2024-01-31 Can you share the full media info for this video as shown by the Jellyfin UI? RE: Successful transcodes in browser, but not on other devices - tmsrxzar - 2024-01-31 (2024-01-31, 12:08 AM)abaxi Wrote: I'm not exactly sure why it would transcode when streaming to the browser but not elsewhere, as the Chromecast 4K and my desktop clients do not support AV1. because the source video is already compatible with the client, PlayMethod=DirectPlay and because the android-tv app does not have force transcoding settings that means the client does not request a transcode transcoding settings on the server only tell the server what it is capable of doing IF THE CLIENT REQUESTS IT the server cannot force clients to take a transcoded version RE: Successful transcodes in browser, but not on other devices - abaxi - 2024-01-31 (2024-01-31, 12:13 AM)TheDreadPirate Wrote: Can you share the full media info for this video as shown by the Jellyfin UI? The video stream has info: Code: Video The audio stream has info: Code: Audio (2024-01-31, 12:15 AM)tmsrxzar Wrote:(2024-01-31, 12:08 AM)abaxi Wrote: I'm not exactly sure why it would transcode when streaming to the browser but not elsewhere, as the Chromecast 4K and my desktop clients do not support AV1. What does "compatible" mean here? Why would the client request a direct stream for a codec that it's not able to decode? RE: Successful transcodes in browser, but not on other devices - TheDreadPirate - 2024-01-31 My CCwGTV 4K requests transcodes for my AV1 content. But I explicitly use exoplayer (manually selected). I see in the first log you posted that libVLC wanted to direct play. I manually selected libVLC on mine and it ATTEMPTED to direct play (it did not go well). What happens when you manually select exo as your preferred player? RE: Successful transcodes in browser, but not on other devices - tmsrxzar - 2024-01-31 disregard* take it TDP, all yours RE: Successful transcodes in browser, but not on other devices - abaxi - 2024-01-31 (2024-01-31, 03:45 AM)TheDreadPirate Wrote: My CCwGTV 4K requests transcodes for my AV1 content. But I explicitly use exoplayer (manually selected). I see in the first log you posted that libVLC wanted to direct play. I manually selected libVLC on mine and it ATTEMPTED to direct play (it did not go well). Ah, I had LibVLC selected for troubleshooting this issue with Auto set before (also attempted direct play). Selecting ExoPlayer explicitly seemed to have resolved the issue, thank you! |