der richter
der richter
with the removal of [this](https://github.com/mpv-player/mpv/pull/13643/commits/5337cab13cb1e36827aed8d2a503ca5e59a5960f), i don't think this is possible to do in the vulkan platform context itself, since we can't just change the swapchain functions or add new...
> Vulkan has no extension to check for the current displays bit depth. So no way to automate this step. As such it is up to the user to manually...
> I think the best is to have platform specific check and/or logic to infer target depth agreed > Too little dithering is worse than too much dithering. i didn't...
i am wondering how to proceed here? to sum it up: - macOS seems to always operate at at least 10 bit internally (compositor), whether the display is 8bit or...
opened a PR for this #15125.
probably related to #15622 / https://github.com/mpv-player/mpv/commit/06fe665b789ffca7c6716cd4ca2fec7e2d0f54be any idea @ruihe774? the crucial part in the log. ``` ... [ 0.076][v][af] [in] 88200Hz stereo 2ch s32 [ 0.076][v][af] [userspeed] 88200Hz stereo 2ch...
@ruihe774 mentioning you, in the case you didn't see this issue.
does it happen without `--hwdec=yes` and `--input-commands='script-message display-stats-toggle'`? does it happen with `vo=gpu-next`? on a side note, i would expect dropped frames in the case of audio and video desynchonising...
i am not quite sure why you expect this, though you might need to play with `target-peak` and `hdr-compute-peak` options. the latter is most likely activated in your case and...
just to make things clear. the maximum PX(Y) is the max brightness of the video, not the display. mpv knows the peak brightness of the display if the colour profile...