[WiP] madVR support in MP1 (34 Viewers)
- Thread starter Sebastiii
- Start date
- Moderator
- #5,672
The problem to compar mpchc with kodi or mediaportal, is the fact than mpchc is only videoplayer, nothing else.
The best way, would to use mpchc as renderer for MP as API interface, but mpchc is more young than mp, i think.
Envoyé de mon LG-H870S en utilisant Tapatalk
The best way, would to use mpchc as renderer for MP as API interface, but mpchc is more young than mp, i think.
Envoyé de mon LG-H870S en utilisant Tapatalk
I would have to disagree with that, since MPC-HC + madVR with the latest Nvidia drivers (from 7/1/2021) is a perfectly working combination.
I have not tested last drivers yet. But since 446.14 was ok for me and after that was not, i came to the conclusion that nvidia changed something in the drivers.
- August 9, 2012
- 2,714
- 2,077
- Home Country
-
Germany
Have you tried setting up MPC-HC to use external filters only and selecting LAV as the only external filter? That way you will be using the same setup as MP. Just in case it is something in LAV/settings.
Screenshots below are for MPC-BE but should be the same for -HC
I also recall that version as being a very good version. The problem is that there are many variables naming MediaPortal, Nvidia and not to forget the windows updates. I always use MPC-HC as comparising and that has been working really well. Lately i was so fed up with the issues that i even used MPC-HC for playback....
Yes, I have MPC-HC setup with LAV as external filters and madVR as DShow Video output
You can read more about my testing from yesterday and my findings about the (most likely) root cause of this issue in this post.
I stand corrected.... I had to test it again, and indeed, 446.14 is working for me also from a few tests.
Need to see if it holds, but i recall it was having issues sticking to 12bit for 23.976 and i often had to correct that in Nvidia Configuration.
But so far, so good!
Now i'm still baffled why the latest drivers work fine in windowed mode and why MPC-HC, lav filters and madVR combo is working without issues...
But TNX for the driver hint
I stand corrected.... I had to test it again, and indeed, 446.14 is working for me also from a few tests.
Need to see if it holds, but i recall it was having issues sticking to 12bit for 23.976 and i often had to correct that in Nvidia Configuration.
But so far, so good!
Now i'm still baffled why the latest drivers work fine in windowed mode and why MPC-HC, lav filters and madVR combo is working without issues...
But TNX for the driver hint
More info here and madshi's reply.
- July 2, 2008
- 144
- 116
- Home Country
-
Belgium
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: AMD, Intel and Nvidia driver issues and last recommended version - Doom9's Forum) 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: Considerations for Playing Games with HDR Enabled | NVIDIA). 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 @HomeY 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.
1. Some time ago (can't remember the exact version, but can probably be found when searching this thread: AMD, Intel and Nvidia driver issues and last recommended version - Doom9's Forum) 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: Considerations for Playing Games with HDR Enabled | NVIDIA). 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 @HomeY 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.
Hello, i'm french and a user of madvr with my pc and a sony projector 590ES...really happy but please help me , i have something i don't understand and no one seems to know here in France.
I 've just reinstalled everything on my computer (big bug with windows) and since that, the settings in MADVR's shortcuts concerning SOURCE CONTRAST and SOURCE SATURATON and SOURCE BRIGHTNESS don't not work anymore in HDR 4K, but they do work well on 1080P sources. I am really sure that before the reinstallation they worked , i used them really often to ajust the color and brighness on HDR movies.
Who would have an idea of the cause please? Maybe it comes from something else, from the version or settings of NVIDIA?
Thanks in advance.
Below is the shortcut page in madvr
I 've just reinstalled everything on my computer (big bug with windows) and since that, the settings in MADVR's shortcuts concerning SOURCE CONTRAST and SOURCE SATURATON and SOURCE BRIGHTNESS don't not work anymore in HDR 4K, but they do work well on 1080P sources. I am really sure that before the reinstallation they worked , i used them really often to ajust the color and brighness on HDR movies.
Who would have an idea of the cause please? Maybe it comes from something else, from the version or settings of NVIDIA?
Thanks in advance.
Below is the shortcut page in madvr