More > JRiver Media Center 32 for Windows
JRVR issues with HDR Passthrough [All these fixed with build 55]
Manni:
--- Quote from: SamuriHL on June 01, 2024, 01:36:54 pm ---546.65 like you (I just reverted a couple days ago based on the doom9 thread). Windows 11 which just updated itself to 24h2 but I doubt anything's changed with that.
--- End quote ---
Thanks, that's what I thought, I just wanted to check there was no difference there.
@Hendrik, I checked the new feature in the last build that is supposed to output SDR content as BT2020 / PQ if the OS HDR is enabled, as it could be a workaround if it allowed me to play all content with the OS HDR enabled. Unfortunately, it doesn't seem to be working properly, gamma with SDR content is all washed out. Are you using a fixed 2.2 or something like that? Also I gue it wouldn't work with my SDR 3D LUT, but gamma is wrong with the LUT enabled or disabled.
Manni:
--- Quote from: SamuriHL on June 01, 2024, 01:36:54 pm ---546.65 like you (I just reverted a couple days ago based on the doom9 thread). Windows 11 which just updated itself to 24h2 but I doubt anything's changed with that.
--- End quote ---
Quick question: When you change the refresh rate delay in the settings, does it do anything visibly (apart from solving the metadata issue)? Here there is no difference at all whether the delay is 0.5s or 15s. Is that normal?
@Hendrik: One more thing I noticed, if you enable OS HDR manually before playback, the HDR metadat is always correct, but if you enable HDR to HDR tonemapping back and forth, instead of switching between the original metadata (passthrough) and the HDR to HDR metadata (peak target) you get empty metadata again. Can you reproduce this? If so, this might help you to locate the part of the code that sends empty metadata, because that should never be the case.
SamuriHL:
--- Quote from: Manni on June 01, 2024, 03:53:04 pm ---Quick question: When you change the refresh rate delay in the settings, does it do anything visibly (apart from solving the metadata issue)? Here there is no difference at all whether the delay is 0.5s or 15s. Is that normal?
--- End quote ---
Yes there's a very visible difference for me. When I initially went from 0.5 to 2, it basically blanks the screen for 2 seconds before activating HDR mode. At least on my G2 that's what it does. 2 is far too long for my taste so I'm happy it works at 1. It does not, however, work at 0.5 for me.
Manni:
--- Quote from: SamuriHL on June 01, 2024, 04:22:18 pm ---Yes there's a very visible difference for me. When I initially went from 0.5 to 2, it basically blanks the screen for 2 seconds before activating HDR mode. At least on my G2 that's what it does. 2 is far too long for my taste so I'm happy it works at 1. It does not, however, work at 0.5 for me.
--- End quote ---
Thanks, so that’s the first thing I have to resolve, and probably why it doesn’t help in my case. Changing the delay doesn’t make any difference here (no blanking at all, even with 5 or 15 secs). Have you tried with a 119p or 120p default refresh rate, going to 119p or 120p? Maybe you can reproduce what I experience if you mirror this.
Otherwise please tell me what your options are and I’ll try to see what’s different.
SamuriHL:
My desktop is 120 10 bit rgb in the nVidia cp
JRiver:
Display Settings automatic change mode: Custom
Wait after change (use if display changes slowly): 1 second
FILM (23.976): 3840x2160 - 32 bit @ 119 Hz
FILM( 24): 3840x2160 - 32 bit @ 120 Hz
The rest are set to Desktop Settings
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version