View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000739 | madVR | bug | public | 2025-05-25 12:25 | 2025-05-26 20:41 |
| Reporter | Lugi | Assigned To | |||
| Priority | normal | Severity | major | Reproducibility | random |
| Status | new | Resolution | open | ||
| Platform | Desktop | OS | Windows | OS Version | 10 Home |
| Summary | 0000739: madVR looses ability to enter exclusive mode after playing and exiting videos a few times | ||||
| Description | If I watch a few videos in fullscreen exclusive mode (each time entering and exiting, sometimes closing player in between), then after a few times madVR looses it's ability to enter exclusive mode. I tried killing the process of madVR and the player (tested both MPC-HC and MPC-BE), tried deactivating and activating the monitor, but only restarting the PC fixes it; until it happens again. I need exclusive mode because 10 bits doesn't work correctly (depending on video format) without it, as I can see with the attached test patterns. | ||||
| Steps To Reproduce | I don't know, but I've made a log in case that's needed. I don't know what information are in there though so I don't want to post that publicly. | ||||
| Additional Information | I use four monitors, only two of which are 10 bits, only one of which is HDR. I don't know what DXVA2 "Native" or "Copyback" means. I think it doesn't matter if DXVA2 scaling is active or not. I don't know what "Aero / Desktop Composition" means. I think something called Windows Aero is activated though. | ||||
| Tags | No tags attached. | ||||
| madVR Version | v0.92.17 | ||||
| Media Player (with version info) | MPC-BE 1.8.4 | ||||
| Splitter (with version info) | (Where do I find this information?) | ||||
| Decoder (with version info) | MPC Video Decoder 1.8.4 | ||||
| Decoding | DXVA2 Native | ||||
| Deinterlacing | none (progressive) | ||||
| DXVA2 Scaling Active | no | ||||
| Aero / Desktop Composition | On | ||||
| Problem occurs with mode | fullscreen exclusive mode | ||||
| GPU Manufacturer | NVidia | ||||
| GPU Model | RTX 4060 | ||||
| GPU Driver Version | 32.0.15.7628 | ||||
|
|
I've now tested if different things happen if I activate or deactivate HDR for that monitor in Windows. If I deactivate HDR in Windows, then MadVR enters exclusive mode (as I saw through Ctrl+J), but HDR doesn't work; which it normally does with exclusive mode. (I at first thought exclusive mode doesn't work because HDR doesn't work.) If I activate HDR in Windows, then MadVR doesn't enter exclusive mode on that monitor. During all of that, exclusive mode on my other 10-bit-SDR-monitor still works. |
|
|
You mentioned a log but there's none attached. Why do you want to activate HDR, either in the OS or in the madVR output settings? Usually, you'll get the best quality by letting madVR do the tone mapping, and then sending a Gamma curve to the display. This may be different, though, if you're using an OLED TV. You can also try the latest build from AVSForum, see my recent posts in this thread: https://www.avsforum.com/threads/improving-madvr-hdr-to-sdr-mapping-for-projector.2954506 |
|
|
I want to activate HDR because it's about my HDR-Monitor. On my non-HDR-monitor (which is 10 bit too) everything works with exclusive mode, 10 bit and tone mapping. The problem is with my HDR-Monitor where after some time the HDR or exclusive mode with 10 bits (depending on Windows HDR-setting) stops working. I would like if it doesn't stop working though so that I can watch HDR + 10 bit without needing to restart my PC all the time. I'll send the logs later as soon as I'm on my PC again. I was worried at first that the logs appear public if I attach them, because I don't know what information might be in the logs. Sorry for the confusion. |
|
|
Have you compared HDR vs tone mapping on your HDR monitor? Just because it's an "HDR" monitor doesn't mean that it will look any better if you send it an HDR signal. It might just as well look worse. It depends, though. E.g. if your HDR monitor switches into a high luminance mode when receiving HDR content and can display most content without even needing to do any tone mapping, while it uses a lower luminance mode when receiving Gamma signals, then it could make sense to send it an HDR signal. But otherwise, you're likely better off letting madVR tone map and sending the HDR monitor a non-HDR gamma signal. |
|
|
I have the Samsung Odyssey G85SD, which is able to display a wider color range and (with the correct settings) 1000 nits. That's why I would like my monitor to always receive the full HDR + 10 bit signal. I've now attached the logs where I tested it once with Windows HDR on, and once with Windows HDR off, which results in different problems, as explained. In these logs I've tested it with this video: https://4kmedia.org/lg-cymatic-jazz-hdr10-uhd-4k-demo |
|
|
Oh, attachments ARE public? It would be nice if you switch that post to private then I guess. Regarding 10 bit not working without exclusive mode I'm not quite sure anymore btw. It could be the case that this just depends on the file type, because it doesn't work with one of the test pattern files (I'd attached to the opening post), but it seems to work with a different video (I've copied from an UHD-Blu-Ray in which there are a few color gradients). I've now restarted my PC so that everything works normal for now, and madVR still doesn't want to enter exclusive mode with these test patterns for some reason. With one of them 10 bit seems to work without exclusive mode though, so I'm a bit confused. |
|
|
I've downloaded and deleted the logs. But no worries, the logs don't contain any of your private info or your PC's info, anyway. They strictly just contain information about madVR's internal processing progress. Looking at the "exclusive mode not working" log, it says this for the first couple of seconds, but then this message disappears, so I'm not sure if this is the key reason why it fails: 00005443.424 Render covered by DisplayFusion.exe window [DFTitleBarWindow:01970a01-f2c2-7487-9b43-80225380633c] {2798,-1439,2831,-1410} What is DisplayFusion.exe? You could try temporarily disabling it, maybe that resolves this issue? About HDR passthrough not working, have you tried the latest build from AVSForum? See my recent posts in this thread for a download link: https://www.avsforum.com/threads/improving-madvr-hdr-to-sdr-mapping-for-projector.2954506 |
|
|
Next time the problem appears I will test if the DisplayFusion.exe process has something to do with the issue. I think that it doesn't, because if I remember correctly, I've already had this issue before I've installed DisplayFusion. (It's a software to get more possibilities with setting up multiple monitors, like with different taskbars and stuff.) I can't find a post of yours with a link in that thread. On which page is it? |
|
|
If the problem of not being able to enter exclusive mode persists, then please create a new log with the debug OSD (Ctrl+J) enabled, because that will add a few more important info lines to the log. Please search for my posts in that thread and sort them by date, showing newest first, should be easy to find. |
|
|
I've now used the new version from here: https://avsforum.com/threads/improving-madvr-hdr-to-sdr-mapping-for-projector-no-support-questions.2954506/page-963?post_id=63824868#post-63824868 Using the files standalone results in an error message, so I copied them on top of the old version. Then in worked. I think you sometimes forget that there are people who don't know how such things work. Fortunately I know it at least a little bit. It's the same with that I had to search for your post in that forum. No, that's not easy for many people. Later, madVR's ability to pass through HDR stopped again with specific videos downloaded from YouTube with yt-dlp. It doesn't even work with Window's HDR enabled. I'll send a section of it, cut out with LosslessCut. It still worked with Windows HDR enabled with the video linked earlier. Sadly, I don't have log-creating .ax-file-versions of that new madVR version. So I switched back to the previous version (with the log-creating .ax-files in place) to see what happens. It was able to do the HDR passthrough of the earlier video (log 1), but it made all the colors oversaturated with the new video (log 2). With Window's HDR mode enabled and VLC that new video looks correctly btw. After a bit of trying and switching around the old version stopped doing the oversaturation of the new video, but instead now also failed to display HDR (log 3). Sorry, that's all very complicated and annoying to me. So it's difficult for me to explain all of that in a good way. I don't understand why it's complicated and bugged like that. |
|
|
That video file is HLG, not HDR. Ok, HLG is a type of HDR, but it's *VERY* different to normal HDR content. Sending an HLG file "untouched" to the TV with the HDR flag on is incorrect. You should send the file either without the HDR flag, or with the HLG flag, but sending out the HLG flag is not supported by Windows or Nvidia. One thing you could do (and which the latest madVR build should support) is decoding HLG and tone mapping it, but then it's not HDR, anymore. madVR is freeware, so take it or leave it... :) Yes, things can be complicated. Part of the reason is that the HDR support in both the OS and in the Nvidia drivers is very messy. If you're happier with VLC, then I don't mind you using that instead. |
|
|
should be the same issue http://bugs.madshi.net/view.php?id=736 exclusive is also not possible. |
|
|
For me HDR stops working too though, as soon as it happens. But now I have to see what comes, to maybe describing in a better way what exactly is happening next time. This time I was a bit overwhelmed and confused. For now I've just restarted my PC. It would be good to have a log-creating version of the new madVR version so I can create logs if it happens again. VLC is sadly no option because of its worse controls and scaling algorithms. |
|
|
Unfortunately, HDR Flag issues are almost impossible to figure out just by looking at logs. So I fear it will either work or not work, and there's not much we can do about it. It can vary with the PC, it can vary with the GPU driver, it can vary depending on the constellation of the planets. The only way for me to fix such bugs would be if I were able to reproduce them myself. But it just seems to work fine for me. Logs can be super useful for all kinds of things, but not for the HDR flag issue, unfortunately. |
|
|
An alternative may be if you make 10 bit work in all cases, including without exclusive mode. You can use the two test patterns I've added in my opening post to test if 10 bit actually works in different configurations. Then I could just use Window's HDR mode without madVR's exclusive mode which seems to break at least less often. Here, in case you want to have the source for the test patterns: https://github.com/jursonovicst/gradient |
|
|
10bit can work in fullscreen windowed mode. The Nvidia driver internally switches into a direct 10bit mode, in certain situations. It's outside of my control when the driver does that. In theory it's supposed to do that in the moment when the rendering window goes fullscreen, and there are no other windows covering the screen. Nvidia calls this "direct scanout". But practically, it doesn't always seem to work 100% reliably. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-05-25 12:25 | Lugi | New Issue | |
| 2025-05-25 12:46 | Lugi | Note Added: 0003229 | |
| 2025-05-25 15:25 | madshi | Note Added: 0003230 | |
| 2025-05-25 16:11 | Lugi | Note Added: 0003231 | |
| 2025-05-25 17:05 | madshi | Note Added: 0003232 | |
| 2025-05-26 03:14 | Lugi | Note Added: 0003233 | |
| 2025-05-26 03:14 | Lugi | File Added: madVR log.zip | |
| 2025-05-26 03:29 | Lugi | Note Added: 0003234 | |
| 2025-05-26 08:39 | madshi | File Deleted: madVR log.zip | |
| 2025-05-26 09:21 | madshi | Note Added: 0003235 | |
| 2025-05-26 09:39 | Lugi | Note Added: 0003236 | |
| 2025-05-26 10:04 | madshi | Note Added: 0003237 | |
| 2025-05-26 18:31 | Lugi | Note Added: 0003238 | |
| 2025-05-26 18:44 | madshi | Note Added: 0003240 | |
| 2025-05-26 18:45 | madshi | Note Edited: 0003240 | |
| 2025-05-26 19:28 | huhn | Note Added: 0003241 | |
| 2025-05-26 20:16 | Lugi | Note Added: 0003242 | |
| 2025-05-26 20:20 | madshi | Note Added: 0003243 | |
| 2025-05-26 20:20 | madshi | Note Edited: 0003243 | |
| 2025-05-26 20:38 | Lugi | Note Added: 0003244 | |
| 2025-05-26 20:41 | madshi | Note Added: 0003245 |
