Default 'color-standard' different between Quest 2 and Quest 3 when no metadata in video
@rohitjoins is already working on this.
Since Oct 14, 2024.
- Dominant language
- Java
- Stars
- 3k
- Forks
- 955
- Avg merge
- 12d 14h
- Merged PRs (30d)
- 2
Description
Question regarding colour space.
We are seeing a difference between Meta Quest 2 (and all other devices tested) and the Quest 3 in terms of 'default colour space' (color-standard).
If a video does not explicitly contain the metadata to signify BT709 (color-standard = 1), then it appears to use BT2020 (color-standard = 6) on the Quest3, whilst other devices use BT709. media3/ExoPlayer seems to set Format.NO_VALUE (-1) due to the atom being missing from the video.
If we use the MediaPlayer API instead of media3/ExoPlayer, then we get BT709 (color-standard = 1) on all devices (including Quest 3) for the same video.
Seeing this in the media3 'demo' app (tested v1.1.0 and 1.4.0) as well as our product (AVProVideo).
Naturally the solution is to make sure the information is in the video (!) but we are curious as to why we are seeing this, and also have a client that does not really want to fix their entire video catalog.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.