More > JRiver Media Center 32 for Windows
JRVR issues with HDR Passthrough [All these fixed with build 55]
Hendrik:
--- Quote from: Manni on May 31, 2024, 09:58:40 am ---One thing I forgot to mention in the first post that might help explain the difference some of us experience between manually enabling OS HDR before playback and leaving it disabled, and possibly the dropped frames issue in HDR passthrough:
- When OS HDR is disabled before playback, if you look at the vSync info in the JRVR OSD it jumps all over the place. I don't think it reflects the actual vsync rate, as there is no more or less frames dropped or repeated, but it moves up and down like crazy. This never happens with madVR.
- When OS HDR is enabled before playback, the vSync info in the OSD is rock steady, as it should be: 119.880hz when playing 23p content at 119p.
Can you reproduce this behaviour, and does it help to understand what might be wrong for some users and not others? Could it be different depending on the processing/rendering path/hardware acceleration options etc?
--- End quote ---
I have actually been observing this no matter how I start playback or if I even play HDR at all. But it hasn't been causing any apparent playback issues as far as I can tell. It used to be perfectly stable, I wonder if something in the driver or Windows changed.
I'm working on a new presentation mode that may impact this, we will see.
Manni:
--- Quote from: Hendrik on May 31, 2024, 10:22:51 am ---I have actually been observing this no matter how I start playback or if I even play HDR at all. But it hasn't been causing any apparent playback issues as far as I can tell. It used to be perfectly stable, I wonder if something in the driver or Windows changed.
I'm working on a new presentation mode that may impact this, we will see.
--- End quote ---
Thanks, it's must have been a coincidence then. I agree that I haven't seen any detrimental impact of this weird fluctuation on playback, as reported earlier.
One suggestion, it would be great if you could provide in the JRVR OSD the peak target when doing HDR to HDR tonemapping, so that we can see the difference with HDR passthrough, as currently I don't think there is any. The original peak is reported for the input as HDR 10 peak, but there is no information reported the tonemapped peak. Maybe report "HDR to HDR (peak)" instead of "HDR Passthrough" when HDR to HDR tonemapping is enabled? Because technically, it's not passthrough if you tonemapped HDR to HDR, that's one of the reasons (along with the empty HDR metadata) why I thought HDR to HDR wasn't working.
I can't see any difference in the OSD at the moment that would help clarify the active mode (HDR passthrough vs HDR to HDR) at a glance.
Reporting the 3D LUT on the OSD (if active) as already discussed would also be helpful, but I'm aware that you don't have much room available in the OSD in SDR.
SamuriHL:
Ok, interesting. I think Manni you're on to something here about the refresh rate change causing the issue. If I set my display to 120 and turn OFF custom refresh rate options in MC, I do indeed get metadata passed without having to enable the OS nonsense first. IF, however, I have the refresh rate option in MC set to on, I lose all metadata unless I enable OS HDR before playback. So I don't know if that can be improved but that's what's happening there.
Hendrick, while we're on the topic of DV and profile 7. Any chance you could eventually include an option to convert it to profile 8 on the fly. Kodi now has that option built in and it's useful for some people. I think for the purposes of using the DV data here it MIGHT be useful? But I'm with Manni, please don't just shut it off for profile 7. I definitely see improvement in MEL titles for sure. An option would be nice.
danbez:
" I definitely see improvement in MEL titles for sure. An option would be nice."
Interesting - are you sure this is not placebo effect? I can't claim I know all details on how JRVR/Libplacebo handles DV, but MEL titles have an empty 2nd layer, leaving only the RPU data to be consumed as an improvement to the base HDR. However, Hendrik confirmed that scene-based DV metadata is not consumed yet. What is left for P7? Only peak brightness info? (For Profile 5, we know that it can properly consume ICtCp which is better than YcBrCr).
I actually like what Hendrik suggested - detect the presence of a 2nd layer and turn off DV. Is this available in the latest build? I have been using "vf=format:dolbyvision=no" with MPV to ignore DV on anything but Profile 5 ATM.
Also excited to hear you have plans to support DV scene based tonemapping. This would be interesting. But what would be really cool is if you could pull "a trick out of the hat" and add FEL support as well... I don't care about FEL titles that fixes brightness (because JRVR can do the same with its own tonemapping), but I care about titles with poorly authored Base layer and huge FEL layer to fix the problems. Paramount, Kino Lorber, some titles from Studio Canal seem to be the main offenders here.
Hendrik:
--- Quote from: SamuriHL on May 31, 2024, 11:22:13 am ---I definitely see improvement in MEL titles for sure.
--- End quote ---
I made it so that it's only turned off for FEL titles, since on MEL the enhancement layer is all zeros anyway.
If there is any noticeable improvement is arguable, but the image reshaping instructions are used regardless, which can change on a per-scene basis, we only don't use any of the tone mapping instructions in the further DV levels.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version