View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000740 | madVR | bug | public | 2025-06-14 16:52 | 2025-06-15 16:38 |
Reporter | mitzsch | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | new | Resolution | open | ||
Summary | 0000740: Frame dropping/ glitching with 4K HDR10 files with changing metadata | ||||
Description | I noticed a problem with HDR10 files with changing metadata. Those files are typically found on UHD Blu-rays where there is a theatrical and director's cut on the same disc... Those small movie pieces on the disc of the movie, created into the full movie by seamless branching, may have different metadata values. An example of such a movie would be the German disc of Jurassic World Dominion... I checked with my UHD Blu-ray player... It does not care about the changing metadata, the first metadata it reads from the disc/file is passed through until the end of the movie... madVR (0.92.17/208) in passthrough mode, however, adapts and sends the changed metadata whenever such a spot in the file is hit, to the display. This leads to frame dropping/glitching. This is especially noticeable when framerate/mode matching is on. Other software is also affected... I also use mpv and it shows the same problem... => https://github.com/mpv-player/mpv/issues/11538 | ||||
Steps To Reproduce | Open a mkv 4K HDR file with changing metadata and turn on framerate/mode matching when in fullscreen. When hitting the spot where metadata changes, you will encounter frame dropping or glitching. | ||||
Tags | No tags attached. | ||||
madVR Version | 0.92.17 / build 208 | ||||
Media Player (with version info) | mpc-hc 2.4.3 from clsid2 github | ||||
Splitter (with version info) | LAV 0.79.2-29-gadffe | ||||
Decoder (with version info) | LAV 0.79.2-29-gadffe | ||||
Decoding | DXVA2 Native | ||||
Deinterlacing | none (progressive) | ||||
DXVA2 Scaling Active | no | ||||
Aero / Desktop Composition | On | ||||
Problem occurs with mode | fullscreen exclusive mode | ||||
GPU Manufacturer | NVidia | ||||
GPU Model | RTX 4060 | ||||
GPU Driver Version | 576.52 (Studio) - Windows 10 | ||||
|
If it also affects other renderers like mpv, then it's likely the Nvidia driver (or the OS itself) causing an issue when you update the metadata. Which is, of course, very annoying, but probably not much we can do about it. You could try different drivers to see if that makes a difference. You can also try enabling or disabling the OS built-in HDR mode. |
|
you could not send meta data in general. as an option obviously. could help many user where the display can not handle meta data correctly. there are also many that inject meta data theses days for reason i do not know. |
|
Thanks for the reply and input. I will try my old AMD GPU (RX 580) - I'm kind of curious how it behaves. In the end, it may simply be Windows... Yeah, not sending metadata at all is also possible... Well lets see |
|
i just forget you can already do that. give it a try. |