home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Area 51 - Testing Area
madVR support in MP1
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="el Filou" data-source="post: 1282455" data-attributes="member: 78516"><p>It seems like the problem is specific to NVIDIA and has two causes:</p><p></p><p>1. Some time ago (can't remember the exact version, but can probably be found when searching this thread: <a href="https://forum.doom9.org/showthread.php?t=176013" target="_blank">AMD, Intel and Nvidia driver issues and last recommended version - Doom9's Forum</a>) NVIDIA changed the way their private HDR API works and now says the developers who were using the API the old way should change their code (source: madshi, from link in previous post).</p><p></p><p>2. As a workaround of point 1 for apps that were using the private API "the old way" (like madVR), NVIDIA implemented a 'trick' in the driver that detects when those apps display HDR content, and makes it transparently switch to HDR (source: <a href="https://nvidia.custhelp.com/app/answers/detail/a_id/5072" target="_blank">Considerations for Playing Games with HDR Enabled | NVIDIA</a>). What seems to be happening, is that the driver is detecting when apps that use madVR start a HDR video and it switches to HDR mode, but it not always detects when HDR content is not displayed anymore. For example, with MPC-HC people have said that when they display any GUI element like seek bar or menu, the driver temporarily switches to SDR and then to HDR again when the GUI element goes away. The test by [USER=68365]@HomeY[/USER] where opening Task Manager over MP temporarily switched back to SDR would have the same explanation.</p><p>This is just my intuition on what may be happening, but I think as MediaPortal uses a 3D GUI and not 2D Windows GUI elements like MPC, the NVIDIA driver doesn't correctly detect when the app is not showing HDR content anymore, and that's why it's stuck in HDR mode after madVR is used once to display HDR content (i.e. the driver probably thinks MediaPortal is acting more like a game where everything is in HDR, than a media player that switches back and forth depending on content).</p><p></p><p>The definitive solution if you follow what NVIDIA recommends (source: madshi) would be for madVR to change its code to use the "new way" to switch to HDR, but madshi isn't sure it won't impact quality as he thinks this involves the OS HDR API and it might not be lossless.</p><p>As long as there is no change to madVR, there may be no other solution with MediaPortal except using old NVIDIA drivers (so no compatibility with newest cards), except if MP devs find some way to make the NVIDIA driver 'guess' that HDR content is not displayed anymore and it should switch back to SDR.</p></blockquote><p></p>
[QUOTE="el Filou, post: 1282455, member: 78516"] It seems like the problem is specific to NVIDIA and has two causes: 1. Some time ago (can't remember the exact version, but can probably be found when searching this thread: [URL="https://forum.doom9.org/showthread.php?t=176013"]AMD, Intel and Nvidia driver issues and last recommended version - Doom9's Forum[/URL]) NVIDIA changed the way their private HDR API works and now says the developers who were using the API the old way should change their code (source: madshi, from link in previous post). 2. As a workaround of point 1 for apps that were using the private API "the old way" (like madVR), NVIDIA implemented a 'trick' in the driver that detects when those apps display HDR content, and makes it transparently switch to HDR (source: [URL="https://nvidia.custhelp.com/app/answers/detail/a_id/5072"]Considerations for Playing Games with HDR Enabled | NVIDIA[/URL]). What seems to be happening, is that the driver is detecting when apps that use madVR start a HDR video and it switches to HDR mode, but it not always detects when HDR content is not displayed anymore. For example, with MPC-HC people have said that when they display any GUI element like seek bar or menu, the driver temporarily switches to SDR and then to HDR again when the GUI element goes away. The test by [USER=68365]@HomeY[/USER] where opening Task Manager over MP temporarily switched back to SDR would have the same explanation. This is just my intuition on what may be happening, but I think as MediaPortal uses a 3D GUI and not 2D Windows GUI elements like MPC, the NVIDIA driver doesn't correctly detect when the app is not showing HDR content anymore, and that's why it's stuck in HDR mode after madVR is used once to display HDR content (i.e. the driver probably thinks MediaPortal is acting more like a game where everything is in HDR, than a media player that switches back and forth depending on content). The definitive solution if you follow what NVIDIA recommends (source: madshi) would be for madVR to change its code to use the "new way" to switch to HDR, but madshi isn't sure it won't impact quality as he thinks this involves the OS HDR API and it might not be lossless. As long as there is no change to madVR, there may be no other solution with MediaPortal except using old NVIDIA drivers (so no compatibility with newest cards), except if MP devs find some way to make the NVIDIA driver 'guess' that HDR content is not displayed anymore and it should switch back to SDR. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Area 51 - Testing Area
madVR support in MP1
Contact us
RSS
Top
Bottom