I would like to request official support for **HDR Vivid** and **Audio Vivid** in mpv.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 37k
- Forks
- 3.5k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 22
Description
Feature Request
I would like to request official support for HDR Vivid (CUVA 005.1-2021 dynamic HDR standard) and Audio Vivid (3D audio standard) in mpv.
Background and Current Status
1. HDR Vivid
- FFmpeg Support: FFmpeg has provided complete dynamic metadata support for the CUVA 005.1-2021 standard since 2022 through the
AVDynamicHDRVividstruct (related APIs:av_dynamic_hdr_vivid_alloc(),av_dynamic_hdr_vivid_create_side_data()). - mpv Status: mpv has not yet integrated these APIs and cannot properly handle or pass through HDR Vivid dynamic metadata.
2. Audio Vivid
- FFmpeg and mpv Status: Neither mainline has merged Audio Vivid decoder support yet.
- Third-party Implementation Proves Feasibility: The community integration package
mpv-Yaozhihas already implemented decoding and PCM output for Audio Vivid (AV3A) through independent integration of the decoding pipeline (supportingnativechannel-preserving output andbinauralrendering). This demonstrates that adding Audio Vivid support in the mpv ecosystem is technically feasible. - Reference Project: https://github.com/Yaozhil/mpv-Yaozhi (its README explicitly lists AV3A / Audio Vivid as a core capability)
Specific Requests
1. For HDR Vivid
FFmpeg already provides a complete dynamic metadata API through the AVDynamicHDRVivid struct, but mpv has not yet integrated it. I would like to ask the developers whether it would be possible to add parsing and passing support for this metadata in the gpu-next renderer backend? Implementing dynamic tone mapping or display passthrough would be very helpful for users in China who play HDR Vivid content.
2. For Audio Vivid
Neither FFmpeg nor mpv mainline currently supports this format, but community integration packages (such as mpv-Yaozhi) have already implemented Audio Vivid decoding and PCM output through independent AV3A integration, proving technical feasibility. I would like to ask whether the developers have any plans to consider adding support for this format in FFmpeg or mpv mainline in the future? If testing or additional information is needed, I am willing to assist.
Thank you for taking the time to consider this request!
Expected Behavior
I carefully read all instruction and confirm that I did the following:
- I tested and confirmed that the issue exists with the latest release version or newer.
- I provided all required information including system and mpv version.
- I produced the log file with the exact same set of files, parameters, and conditions used in "Reproduction Steps", with the addition of
--log-file=output.txt. - I produced the log file while the behaviors described in "Actual Behavior" were actively observed.
- I attached the full, untruncated log file.
- I attached the backtrace in the case of a crash.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by reviewing mpv’s gpu-next renderer context and the FFmpeg HDR Vivid APIs named in the issue. Compare the referenced mpv-Yaozhi Audio Vivid implementation, then determine whether either request has an upstreamable implementation path; completion would require an agreed scope for metadata passthrough and Audio Vivid support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100