Client didnt request transcode for unsupported codec in integrated exo player

Tetrax-10 commented 9 months ago

Describe the bug

I played a video of codec V_MPEGH/ISO/HEVC 10 bits which is unsupported in my android device (Moto g51 5G) it should have requested transcode and played it in supported codec in integrated exo player, instead it tried to play raw data without transcoding and got error in my Jellyfin android app (integrated exo player). But the web player requests transcode and plays the video in supported codec.

WhatsApp Image 2023-11-27 at 00 55 55_2df2d513

WhatsApp Image 2023-11-27 at 00 54 16_fe7bd20f

Logs

No response

Application version

2.5.3

Where did you install the app from?

Google Play

Device information

Moto G51 5G

Android version

Android 11

Jellyfin server version

10.8.12

Which video player implementations does this bug apply to?

[ ] Web player (default)
[X] Integrated player (ExoPlayer)
[ ] External player (VLC, mpv, MX Player)

broetchenrackete36 commented 9 months ago

I have the same problem with 10Bit Codecs on my Redmi Pad SE. I don't completely understand the DeviceProfileBuilder.kt but it seems it only checks the mimeType and not the supported Profile? I could be completely wrong...

broetchenrackete36 commented 9 months ago

Possibly same as #1174

jellyfin-bot commented 4 months ago

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.

If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.

Tetrax-10 commented 4 months ago

Yes this issue still exists

jellyfin-bot commented 4 weeks ago

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.

If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.

Tetrax-10 commented 3 weeks ago

Just tested again, this issue still exists.

jellyfin / jellyfin-android