madshi bug tracker - madVR
View Issue Details
0000631madVRbugpublic2019-12-31 15:442020-01-26 16:13
totalz 
 
highmajoralways
newopen 
Windows101709
v0.92.17
KMPlayer 64X_2019.11.18.03
LAV 0.70.2
LAV 0.74.1
DXVA2 Copyback
auto mode
no
Off
fullscreen exclusive mode
AMD
RX570
2020 12 02 WHQL
0000631: Disabled(unchecked) automatic full screen exclusive mode, but still entered exclusive mode while full screen.
If seems that I cannot totally disable full screen exclusive mode.
Once enabled, cannot fully disable, not even system restart
No tags attached.
Issue History
2019-12-31 15:44totalzNew Issue
2019-12-31 21:24madshiNote Added: 0002607
2020-01-02 04:02totalzNote Added: 0002608
2020-01-02 04:05totalzNote Edited: 0002608bug_revision_view_page.php?bugnote_id=2608#r598
2020-01-02 04:06totalzNote Edited: 0002608bug_revision_view_page.php?bugnote_id=2608#r599
2020-01-02 07:29totalzNote Edited: 0002608bug_revision_view_page.php?bugnote_id=2608#r600
2020-01-03 09:29madshiNote Added: 0002609
2020-01-03 09:53totalzNote Added: 0002610
2020-01-03 09:56madshiNote Added: 0002611
2020-01-16 12:17domNote Added: 0002615
2020-01-20 11:06pittyhNote Added: 0002617
2020-01-20 11:11madshiNote Added: 0002618
2020-01-20 13:07pittyhNote Added: 0002619
2020-01-20 13:11pittyhNote Edited: 0002619bug_revision_view_page.php?bugnote_id=2619#r602
2020-01-20 13:19pittyhNote Edited: 0002619bug_revision_view_page.php?bugnote_id=2619#r603
2020-01-20 13:22pittyhNote Edited: 0002619bug_revision_view_page.php?bugnote_id=2619#r604
2020-01-20 13:24pittyhNote Edited: 0002619bug_revision_view_page.php?bugnote_id=2619#r605
2020-01-20 13:49pittyhNote Added: 0002620
2020-01-21 23:43madshiNote Added: 0002621
2020-01-26 16:09domNote Added: 0002626
2020-01-26 16:13madshiNote Added: 0002627

Notes
(0002607)
madshi   
2019-12-31 21:24   
Some media players override the madVR settings. Maybe that's what's happening here? I'm not very familiar with KmPlayer. Maybe there's a setting for that in the KmPlayer options?
(0002608)
totalz   
2020-01-02 04:02   
(edited on: 2020-01-02 07:29)
Actually, I think KMPlayer is now closely and kind of identical to MPC-HP. And I don't think there's any HDR setting in KMPlayer.

After more testing, I found that the issue happens when Windows HDR is off. But then I only enabled the fullscreen exclusive mode while Windows HDR was off. I'm not dare to test the mode while Windows HDR is on. I did try clean install display card driver, but that didn't fix the problem.

Device HDR setting in madvr set to "passthrough HDR to display", and checked "send HDR metadata to the display". Is the HDR metadata for HDR10+ & Dolby Vision?

I'm wondering if madvr has to enter "fullscreen exclusive" in order to passthrough HDR to display. Cause whenever I need to access KMPlayer's menu, the screen goes black, wait 3 sec if that option is checked in exclusive mode. And there are times that I couldn't get the menu, video picture shown, then back to black screen for 3 sec... And color can be all wrong when playback resumes, 50% of times it goes to Black&White. Windows 10 itself could be the issue here when Windows HDR is off.

(0002609)
madshi   
2020-01-03 09:29   
madVR should never go fullscreen exclusive unless you either have it enabled in the settings, or if the media player overwrites your settings.

The HDR metadata is simple HDR10. Dolby Vision and HDR10+ are not supported at the moment.

For best HDR quality I'd recommend using the latest test build from AVSForum and letting madVR do the tone mapping. That requires a good GPU, though.
(0002610)
totalz   
2020-01-03 09:53   
The effect of switching to fullscreen exclusive mode is very obvious, and I never see that in KMPlayer unless I use madVR as the Video Renderer and enabled fullscreen exclusive mode. Except in this case I couldn't disable it...
(0002611)
madshi   
2020-01-03 09:56   
What does the madVR OSD say (Ctrl+J)? Does it say fullscreen exclusive mode?
(0002615)
dom   
2020-01-16 12:17   
I'm encountering the same issue with MPC-HC.
The display goes black for a moment and then comes back - exact behavior of my display when mode/resolution/whatever is changed.
- Only occurs with MadVR
- Switch to exclusive happens a few seconds after going to full-screen in MPC
- No matter what options are set in MadVR - it always occurs
- All mode-switching and exclusive options in MPC are disabled as well

This is made worse by the fact that I'm also experiencing something sort of similar to issue 0000596 (http://bugs.madshi.net/view.php?id=596 [^]).
However, in my case, the image is significantly darker only after the switch has occurred -> dark in FSE and better-looking in FSW - i.e. the other way around.
If I watch the video in normal windowed mode (no full-screen whatsoever) then it looks fine.
-> This is what leads me to believe that the display switch that occurs after a few seconds is to full-screen exclusive
(0002617)
pittyh   
2020-01-20 11:06   
Created a account here, just confirm i am having the same issue.

Windows 10 1909
9900K
2080ti
Nvidia driver version 441.12
Potplayer 1.7.20977

 Disabled(unchecked) automatic full screen exclusive mode, but still entered exclusive mode while full screen.

I just cannot get fullscreen windowed without it going exclusive.
Changing to EVR renderer in potplayer allows fullscreen windowed no problem.
(0002618)
madshi   
2020-01-20 11:11   
Again guys, I've asked but you didn't answer:

What does the madVR OSD say (Ctrl+J)? Does it say fullscreen exclusive mode?
(0002619)
pittyh   
2020-01-20 13:07   
(edited on: 2020-01-20 13:24)
Hi madshi,

Nope it says D3d11 fullscreen windowed (10Bit) but it's acting like it's fullscreen exclusive, because if i mouse over the seek bar or adjust volume, screen flashes black

Also lists "1 frame drop every 1.00 seconds" appears when in windowed mode, and disappears in fullscreen

Link to madvr settings image - windowed mode
https://imgur.com/DFGDyX0 [^]


Fullscreen mode
https://imgur.com/a/C1ROtoQ [^]

(0002620)
pittyh   
2020-01-20 13:49   
Think i fixed it by totally uninstalling madvr and reinstalling.
(0002621)
madshi   
2020-01-21 23:43   
FWIW, Windows 10 has a special mode called "direct scanout", which is automatically activated by the OS and GPU driver in fullscreen windowed mode. The OS and GPU driver do this directly, practically behind the back of madVR. Which is normally fine, because this mode improves performance to near FSE levels. Plus it allows 10bit output in fullscreen windowed mode.

My best guess is that this "direct scanout" mode is somehow causing these issues for you. There's not much I can do about that, unfortunately.

Not sure why uninstalling and reinstalling madVR would fix that, though. That seems weird.
(0002626)
dom   
2020-01-26 16:09   
uninstall/reboot/reinstall/reboot does seem to help on my end.

It says D3D11 fullscreen windowed - the same BOTH immediately after going fullscreen in MPC-HC - and after the delay of a few seconds elapses and the screen switches and the HDR display becomes much darker.

After the "switch" it definitely behaves like fullscreen exclusive, even if MadVR debug OSD doesn't say so.
E.g.: Just mouse right-click to bring up the MPC context menu causes another switch (to what really is FSW, I think) - with the display becoming more light again... after dismissing the context-emu, there is again A 2SWITCH>" (back to FSE) with display becoming much darker again.

As I mentioned before, the FSE dark display is too dark - it is unusable for watching movies.
Grey value 72 is just barely visible an non-black on my (admittedly weak) HDR display.
If in windowed mode, it is 66.
It's not just the low end - the curve seems differentr, e.g. dark/FSE 100 looks equal to light/FSW 80

I'm the above I'm using this: "01. black-level-v1.mp4" from "Mehanik HDR10 test patterns" (https://www.avsforum.com/forum/139-display-calibration/2943380-hdr10-test-patterns-set.html [^])
(0002627)
madshi   
2020-01-26 16:13   
As I said, it's a "feature" of Windows 10. There's nothing I can do about it. Maybe you can work around it by choosing appropriate GPU driver settings. E.g. make sure you're using "RGB Full" in the GPU control panel etc.

It's also possible that it only occurs when using D3D11 presentation or when using 10bit output. You could try disabling D3D11 presentation or force 8bit output instead.