Have a Homatics 4k plus box but I guess this is an Android TV/Plex question.
If I set box to DV in android config the TV switch to Dolby Vision mode.
If I then start a HDR or SDR movie in Plex, TV do not switch mode but stays in DV.
So what mode is actually being played? Is some kind of conversion happening or is DV backwards compatible with SDR/HDR and if then how can I see what mode is actually being used?
When you enable DV on your box via the config does the switching happen straight away or only when you start playback of a title on Plex?
Had some progress.
If I enable HDR and AUTO-HDR, then gui will be SDR and if I start a HDR movie TV switch to display.
If I enable Dolby vision box asks to restart and TV changes to Dolby Vision all the time.
Seems amlogic(5.x kernel) boxes do not support DV profile 7 FEL, so need to convert profile 7 to profile 8. I assume Plex do not have any support for this. There exists a PR for kodi 21 to enable profile 7 on the fly conversion.
xbmc:master ← quietvoid:libdovi
opened 07:24PM - 21 Jan 23 UTC
## Description
The changes bring support for the Rust toolchain with the goal o… f being able to integrate C compatible dependencies through [cargo-c](https://github.com/lu-zero/cargo-c).
This PR also adds the optional [libdovi](https://github.com/quietvoid/dovi_tool/tree/main/dolby_vision) dependency for Android builds.
## Motivation and context
The main motivation for this is to be able to convert Dolby Vision on-the-fly, so that Android devices have less issues.
This requires `libdovi` (which is a Rust/C compatible library).
There are also other usecases for Rust such as binary addons, which seem to have been previously proposed GSoC projects.
## How has this been tested?
Tested successful build for all Android target platforms.
Runtime tested on FireTV Stick 4K (2018) and 4K Max (2021), so `armv7`.
## What is the effect on users?
None by default, as the added dependencies are built optionally with a configure flag.
Only the build process is affected, it's still unknown to me how the new dependencies behave on all supported platforms.
As the dependencies are limited to Android only, I don't think it can have a negative effect.
Testing thread for Android: https://forum.kodi.tv/showthread.php?tid=371557
## Types of change
- [ ] **Bug fix** (non-breaking change which fixes an issue)
- [ ] **Clean up** (non-breaking change which removes non-working, unmaintained functionality)
- [ ] **Improvement** (non-breaking change which improves existing functionality)
- [x] **New feature** (non-breaking change which adds functionality)
- [ ] **Breaking change** (fix or feature that will cause existing functionality to change)
- [ ] **Cosmetic change** (non-breaking change that doesn't touch code)
- [ ] **None of the above** (please explain below)
## Checklist:
- [x] My code follows the **[Code Guidelines](https://github.com/xbmc/xbmc/blob/master/docs/CODE_GUIDELINES.md)** of this project
- [ ] My change requires a change to the documentation, either Doxygen or wiki
- [ ] I have updated the documentation accordingly
- [x] I have read the **[Contributing](https://github.com/xbmc/xbmc/blob/master/docs/CONTRIBUTING.md)** document
- [ ] I have added tests to cover my change
- [ ] All new and existing tests passed
system
Closed
October 31, 2023, 11:54am
4
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.