clams4shoes
clams4shoes
This might be related to an issue some users have reported with Dolby Vision Profile 8.1 content that use non-standard aspect ratios (i.e., not 16:9) on certain Fire TV devices....
I've detailed the Dolby Vision Profile 7 detection and client behavior in 0.19 [here](https://github.com/jellyfin/jellyfin-androidtv/issues/5073#issuecomment-3471370467). Ideally, it would be great if the server could transform the RPU and remux the base...
@rmiller14 I don't think there's much we can do here, other than waiting for the PR to be reviewed. If you'd like, you could try reaching out to Niels to...
Could you provide a Media Capabilities Report? Follow these steps: ``` 1. Open the Jellyfin for Android TV app 2. Connect to a server that you have admin access to...
It seems that the Dolby Vision stream is malformed or invalid. According to the specification, Dolby Vision Profile 8 cannot have a cross-compatibility ID of 6 (Blu-ray): [Dolby Vision Profile...
@njanke96, This appears to be a entirely seperate issue. It looks like all HDR formats are being transcoded because your display is reported as only supporting SDR content. There’s an...
Your Device Profile correctly reports that your Android TV doesn't support Dolby Vision Profile 7 (`DOVIWithEL`) and is requesting that the Jellyfin server start a remux/transcode. Previously, the Jellyfin Android...
In version 0.18.11 of the app, it only checked whether the display supported Dolby Vision. If the display did not, the device profile instructed the server to exclude the `DOVI`...
@EvanAllan, I agree -- it would be nice to have an option to override Dolby Vision Profile 7 detection and force Direct Play. This would also bring the client in...
@Kranzes @EvanAllan Even though [PR #5116](https://github.com/jellyfin/jellyfin-androidtv/pull/5116) is meant to allow users to override Profile 7 device compatibility checks and Direct Play, I wanted to note that when the **only** barrier...