Jellyfin-android: ExoPlayer profiles don't always work as expected - unnecessary transcoding, broken transcodes

Created on 20 Aug 2020  路  5Comments  路  Source: jellyfin/jellyfin-android

The currently shipped ExoPlayer profile doesn't properly advertise the device capabilities in some cases, e.g. HEVC seems to be transcoded sometimes although it shouldn't need to. Since I'm not very knowledgeable into the internals of Jellyfin transcoding and profiles, I'd request others to help me with getting to profile to work properly with as many devices as possible.

bug exoplayer needs discussion

Most helpful comment

Working on the new apiclient, branch implementing it already exists in this repository. Hopefully beta release in 1 to 3 weeks.

All 5 comments

This is planned to be resolved with a new apiclient that's already integrated with ExoPlayer and handles media playback itself.

This is planned to be resolved with a new apiclient that's already integrated with ExoPlayer and handles media playback itself.

Is there an ETA when this new apiclient will be integrated, because the problem presits in v2.1?

New apiclient will be released after the 10.7 server version (since it is not compatible with 10.6). But it will not contain playback related code from the start.

@nielsvanvelzen Just wondering if there is any news on this now that Jellyfin 10.7 has finally reached stable.

Working on the new apiclient, branch implementing it already exists in this repository. Hopefully beta release in 1 to 3 weeks.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

willymilkytron picture willymilkytron  路  5Comments

Orybon picture Orybon  路  4Comments

sopidos picture sopidos  路  3Comments

nielsvanvelzen picture nielsvanvelzen  路  5Comments

vegedb picture vegedb  路  6Comments