View Full Version : madVR - high quality video renderer (GPU assisted)
madshi
24th January 2016, 11:14
@IceB, which OS? Crossfire is problematic, especially on Windows 10. Try disabling it, to see if it makes a difference. You say "Since I have updated madvr". Which version did you use before? And that version definitely didn't have this issue? Are you sure the only thing you changed is the madVR version? You didn't change OS or GPU drivers at the same time, too? If so, it would be great if you could try to isolate the exact madVR build which introduced the problem for you. You can download old madVR builds from the link in the first post of this thread.
IceB
24th January 2016, 11:20
@IceB, which OS? Crossfire is problematic, especially on Windows 10. Try disabling it, to see if it makes a difference. You say "Since I have updated madvr". Which version did you use before? And that version definitely didn't have this issue? Are you sure the only thing you changed is the madVR version? You didn't change OS or GPU drivers at the same time, too? If so, it would be great if you could try to isolate the exact madVR build which introduced the problem for you. You can download old madVR builds from the link in the first post of this thread.
I am on Win OS 8.1 64 bit. Using mpc-hc, lav codecs and madvr all 32 bit. The only change I made is installing the latest madvr. I do not remember what 8x of madvr I had previosly installed but I have my previous madvr folder backed up. I will restore it and recheck again.
As for the crossfire, the second card is inactive according to the monitoring app. I do not enable the CF for the apps that have no profile for it. Moreover, previous madvr version worked well with the same CF configuration..
Sent from my GT-I9500 using Tapatalk
madshi
24th January 2016, 11:42
Well, in that case, as I said, please try to isolate the exact madVR build which introduced the problem for you. That's the best way to approach the problem, because if I know which exact madVR build introduced the problem I can look at the source code changes in that exact version to find which change might be responsible for the problem. Practically that means you'd have to download different older madVR builds, until you find two consecutive builds where build X works and build X+1 shows the problem.
IceB
24th January 2016, 11:55
Well... download different older madVR builds, until you find two consecutive builds where build X works and build X+1 shows the problem.
Will try and report.
Sent from my GT-I9500 using Tapatalk
bbsc
24th January 2016, 12:09
Well, if you create a debug log, I can check if I can see something.
Sample video is here (http://www.mediafire.com/download/zwssy8gzdxbbg9n/Sample-001.mkv).
Logs are here (http://www.mediafire.com/download/n45b7y4amlnbpee/madVR_-_log.zip).
Thank you.
madshi
24th January 2016, 12:16
Sample video is here (http://www.mediafire.com/download/zwssy8gzdxbbg9n/Sample-001.mkv).
Logs are here (http://www.mediafire.com/download/n45b7y4amlnbpee/madVR_-_log.zip).
Thank you.
Does this one help?
http://madshi.net/madVRbbsc.rar
FDisk80
24th January 2016, 12:26
Where is the madVR's profile saved? Wasn't it the settings.bin file?
I can't find it anywhere. But somehow settings are still being saved.
madshi
24th January 2016, 12:40
The "settings.bin" file is created if (and only if) madVR has write access to its own folder. In addition madVR always saves the settings to the registry (HKCU\Software\madshi\madVR\Settings).
FDisk80
24th January 2016, 12:41
The "settings.bin" file is created if (and only if) madVR has write access to its own folder. In addition madVR always saves the settings to the registry (HKCU\Software\madshi\madVR\Settings).
Thank you.
XTrojan
24th January 2016, 14:49
What's the current issue with external subtitles in 3D or 3D subs at the moment? When I tried SBS external subs they were 3D but it felt weird. Does MadVR have the same issue StereoScopic player has; they have no depth and cause wierdness?
There's no player at the moment that can handle 3D subtitles well for some reason :/
Afaik 3D Bluray subs has dynamic "depth" or something similar located in the VUI or SEI, tsmuxer could remux this data into a .m2ts, although it's sad that it's development stopped. Maybe it's worth digging there?
madshi
24th January 2016, 15:19
What's the current issue with external subtitles in 3D or 3D subs at the moment? When I tried SBS external subs they were 3D but it felt weird. Does MadVR have the same issue StereoScopic player has; they have no depth and cause wierdness?
There's no player at the moment that can handle 3D subtitles well for some reason :/
Afaik 3D Bluray subs has dynamic "depth" or something similar located in the VUI or SEI, tsmuxer could remux this data into a .m2ts, although it's sad that it's development stopped. Maybe it's worth digging there?
Why don't you look 2 pages back in this thread, there are all your answers.
bbsc
24th January 2016, 15:26
Does this one help?
http://madshi.net/madVRbbsc.rar
Sorry, but it doesn't.
Installed 0.90.3.
The original works as expected.
Replaced .ax
With Broadcom video decoder:
Test sample crashes madVR as before.
New logs are here (http://www.mediafire.com/download/pv4wahngt74t4b7/2015.01.24.16.14.madVR_-_log.zip).
"Normal" videos play as if there is no horizontal scanning sync (a lot of horisontal lines)
With LAV:
Test samle produces "Creating Direct3D device failed (80070005)" message and player pauses. Playing normal if resumed from this state.
"Normal" videos play normally.
madshi
24th January 2016, 16:12
Sorry, but it doesn't.
Installed 0.90.3.
The original works as expected.
Replaced .ax
With Broadcom video decoder:
Test sample crashes madVR as before.
New logs are here (http://www.mediafire.com/download/pv4wahngt74t4b7/2015.01.24.16.14.madVR_-_log.zip).
"Normal" videos play as if there is no horizontal scanning sync (a lot of horisontal lines)
With LAV:
Test samle produces "Creating Direct3D device failed (80070005)" message and player pauses. Playing normal if resumed from this state.
"Normal" videos play normally.
Sounds like a *really* crappy decoder. Ok, I'll try again. FWIW, with other renderers where you don't get the crash, are the bottom couple of video lines blacked out, or are they properly filled?
bbsc
24th January 2016, 16:35
Sounds like a *really* crappy decoder. Ok, I'll try again. FWIW, with other renderers where you don't get the crash, are the bottom couple of video lines blacked out, or are they properly filled?
Others don't crash and properly filled.
But madVR is the single one which can do smooth playback and excellent sync.
EVR is working more or less but there's a problem with video framerate when it's encoded with VC1.
Ok, thank you for the effort, it's really a problem but not a huge one.
There're not so many videos with height not dividable by 4.
"Real" BD's and remuxes go just fine.
evil-doer
24th January 2016, 17:03
Oh. I just noticed we tested in the wrong order. As I wrote in my original post:
> If the problem does not occur with build 5, then it will
> also not occur with builds 6-10. In that case try build 2 or 3.
You said you had no problem with build 5, so your next test should have been build 2 or 3, and not build 6+. Sorry, didn't notice that before...
I dont have a problem with 3, 2, or 1 either.
The original problem was on potplayer 64 bit and I installed potplayer 32 bit for this testing, so maybe that has something to do with it?
nevcairiel
24th January 2016, 17:04
The original problem was on potplayer 64 bit and I installed potplayer 32 bit for this testing, so maybe that has something to do with it?
Easy enough to find out and use the version that did show the problem before? :)
evil-doer
24th January 2016, 17:43
Easy enough to find out and use the version that did show the problem before? :)
Thats not up to me, madshi only gave me the 32 bit files to test.
Uoppi
24th January 2016, 17:46
That's most probably the low latency mode, which the media player activates when drawing any kind of OSD that needs quick reaction times (madVR's Ctrl+J OSD does *not* activate it, though). It also gets activated when the madVR exclusive mode seekbar is visible.
I remember in the past the present queue seemed to switch back to normal from 2 frames immediately as the seekbar disappeared (I'm using Kodi DSPlayer). Now there's some occasional switching back and forth, according to the madVR OSD stats.
But right now it's not getting "permanently" stuck at 2 frames anymore, so performance-wise the little hiccuping doesn't do any harm at all. I'm not sure what was happening when it was stuck at 2 frames, even without the seekbar visible (maybe my settings were maxing out and that's what caused it?). I've also had some crashes with a couple of Youtube videos, which hasn't happened before. It might have something to do with the latest Nvidia drivers.
nevcairiel
24th January 2016, 17:59
Thats not up to me, madshi only gave me the 32 bit files to test.
You misunderstand, use PotPlayer 32-bit with whichever madVR version you are having issues with, ie. 0.90.3, and see if the issues exist there as well. If not, thats a clue as well.
evil-doer
24th January 2016, 18:23
You misunderstand, use PotPlayer 32-bit with whichever madVR version you are having issues with, ie. 0.90.3, and see if the issues exist there as well. If not, thats a clue as well.
Um.. Not only is it working in 32 bit, its now working in 64 bit too. Unless Im somehow missing the magical feature that makes it crash. This is a real mystery now. Ill keep messing with settings and see if I can find what does it.
AngelGraves13
24th January 2016, 21:48
Any ideas why present queue shows 2 as the max value, regardless of what is set in madVR's settings? Previously everything has worked fine. Sometimes the OSD shows the correct present queue number at first but quickly changes to 2 and is then stuck there.
Fullscreen or windowed? If fullscreen, you may have limited the pre-rendered frames to 3 or less in the GPU control panel.
IceB
24th January 2016, 22:02
Well... download different older madVR builds, until you find two consecutive builds where build X works and build X+1 shows the problem.
Thank you @madshi, the issue is solved for me.
I have checked the previous build of madVR I had installed prior to the update - it was 0.80.20. So I have placed it back and rechecked. The issue still exists - queue drops to 0 after a couple minutes of playback.
In fact, as you have mentioned, I have updated my GPU AMD drivers about a month ago and probably have not noticed that the issue exists since the CRIMSON driver update. So I have disabled the crossfire and restarted the PC and rechecked the playback - no queue drops - everything is smooth. I have enabled the crossfire back - the queue drops again.
So I have uninstalled the crimson driver and cleaned the system from the AMD leftovers with the DDU. Then I have installed the latest crimson 16.1 hotfix drivers without the mew settings panel and the installed the CCC from the latest pre CRIMSON 15.1.1 AMD drivers. The disabled all the advanced video stuff in CCC as I did prior the CRIMSON update and rechecked the palyback with the Crossfire enabled. No queue drops - the render times are about 35 with Chroma Upscaling NNEDI3 128 with no glitches. The rendr back to normal.
So my conclusion is that the new AMD CRIMSON edition settings panel, which is lack of the advanced video settings is the source of the issue. It definitely related to the way it handles the crossfire.
This info might hopefully be helpful to anyone with the similar issues.
Cheers
madshi
25th January 2016, 00:34
Others don't crash and properly filled.
But madVR is the single one which can do smooth playback and excellent sync.
EVR is working more or less but there's a problem with video framerate when it's encoded with VC1.
Ok, thank you for the effort, it's really a problem but not a huge one.
There're not so many videos with height not dividable by 4.
"Real" BD's and remuxes go just fine.
Ok, here's the next try:
http://madshi.net/madVR93b.rar
Um.. Not only is it working in 32 bit, its now working in 64 bit too. Unless Im somehow missing the magical feature that makes it crash. This is a real mystery now. Ill keep messing with settings and see if I can find what does it.
Maybe you had 3D enabled, when using an NVidia GPU? That sometimes produces crashes, when using D3D11 presentation.
Manni
25th January 2016, 00:38
Thank you @madshi, the issue is solved for me.
I have checked the previous build of madVR I had installed prior to the update - it was 0.80.20. So I have placed it back and rechecked. The issue still exists - queue drops to 0 after a couple minutes of playback.
In fact, as you have mentioned, I have updated my GPU AMD drivers about a month ago and probably have not noticed that the issue exists since the CRIMSON driver update. So I have disabled the crossfire and restarted the PC and rechecked the playback - no queue drops - everything is smooth. I have enabled the crossfire back - the queue drops again.
So I have uninstalled the crimson driver and cleaned the system from the AMD leftovers with the DDU. Then I have installed the latest crimson 16.1 hotfix drivers without the mew settings panel and the installed the CCC from the latest pre CRIMSON 15.1.1 AMD drivers. The disabled all the advanced video stuff in CCC as I did prior the CRIMSON update and rechecked the palyback with the Crossfire enabled. No queue drops - the render times are about 35 with Chroma Upscaling NNEDI3 128 with no glitches. The rendr back to normal.
So my conclusion is that the new AMD CRIMSON edition settings panel, which is lack of the advanced video settings is the source of the issue. It definitely related to the way it handles the crossfire.
This info might hopefully be helpful to anyone with the similar issues.
Cheers
Thanks, that gave me the idea to try the same thing to see if it could resolve the issues I have with Crimson, unfortunately it doesn't.
I installed the latest Crimson 16.1 and the latest pre-crimson catalyst CCC (which is 15.7, not 15.1.1 by the way).
1) The dynamic range option in the old CCC has no effect on Crimson (similar to RadeonMod), so it's still not possible to select RGB Full for MadVR and 16-235 for PDVD or other apps using the Windows renderer.
2) Crimson still crushes white in 3D above 230 with PDVD, so until LAV+MadVR are able to support 3D BDMV/SSIF I have to keep PDVD for 3D Blurays.
For anyone not using non-MadVR software it's a good way to get more control and the latest drivers.
Back to 14.12 as far as I'm concerned.
evil-doer
25th January 2016, 00:52
Maybe you had 3D enabled, when using an NVidia GPU? That sometimes produces crashes, when using D3D11 presentation.
Ive never enabled 3D, and have an AMD 290x
SamuriHL
25th January 2016, 01:46
Definitely an interesting build. My observation is that it's better for MC21 but I have to do some weird stuff to get it to fully work.
With all the options checked in the 3D settings page for madvr....
Play a 3D MKV in MC21....plays in 2D but the OSD says it's D3D11 3D
Pause playback, minimize the player
Open up the OS display properties and head to advanced
You'll see 3D is enabled. Change NOTHING....just close it
Go back to MC21 and unpause....I now have 3D that works with or without the MC UI. Crazy!!
EDIT:
Ok, I did some different stuff and it seems I was wrong. Just pausing, taking it out of fullscreen, and bringing it back to fullscreen and unpausing is all that's needed. Sweet!
bbsc
25th January 2016, 07:52
Ok, here's the next try:
http://madshi.net/madVR93b.rar
This one is much more interesting.
It doesn't crash at all.
"Normal" videos play excellent.
"Problematic" videos play too. Video starts, stops, resizes without problems.
The only remaining problem is that there are two groups of greened-out lines:
- bottom group. It's constant and wouldn't be a problem if they were black, not green.
- a group on the video image. This group of lines is not constant, it appears on random position and at random time.
Have a look at the screenshot. Ignore the size, it's taken via RDP session, image on the TV is just the same.
http://s10.postimg.org/rdkzacctx/mad_VR_2016_01_25_07_58.jpg (http://s10.postimg.org/9njapaz93/mad_VR_2016_01_25_07_58.png)
Thank you.
MSL_DK
25th January 2016, 08:49
Can you double check whether this is a new problem with v0.90.x or whether this also occurs with v0.89.19?
I have enabled debug with version madVR93b
link: madVR93b_Debug (https://www.dropbox.com/s/2bqj9jpgbzt2xsk/madVR%20-%20log.txt?dl=0)
Do I still have to test with <v0.90.x
x7007
25th January 2016, 09:35
Whoever has windows 8.1 and windows 10 , do like that, it boosted my performance in Skyrim from 28 to 60+ . windows 8.1 and windows 10 are bugged with full of bad settings that worked in windows 7 just fine. In windows 7 I got 100+ fps in skyrim. even with LOW everything the FPS stayed 28 , no way it is possible with 970 GTX and 3770K 4.3 Ghz I will get this kind of fps. This setting from here http://www.ibtimes.co.uk/windows-10-how-fix-sluggish-performance-boost-overall-system-speed-1516413 Fixed the issue. I will do it on my laptop 8.1 too and see how it improved things. it might fix stupid bugs in the media player that we use, because we use Exclusive mode and it's like gaming, should work the same. And don't forget to disable the Xbox DVR . from Start > Xbox DVR > Log in your account without password (you can skip the password) > Settings > Xbox DVR Recording .. > disable .
Should fix a lot of input lag and other things too.
4h4h270
25th January 2016, 10:41
I'm not sure I understand: Does this frame drop problem only occur with 3D playback, or also with 2D playback?
The frame drop only occur with 3D playback, especially frame packed 3D.
madshi
25th January 2016, 17:39
This one is much more interesting.
It doesn't crash at all.
"Normal" videos play excellent.
"Problematic" videos play too. Video starts, stops, resizes without problems.
The only remaining problem is that there are two groups of greened-out lines:
- bottom group. It's constant and wouldn't be a problem if they were black, not green.
- a group on the video image. This group of lines is not constant, it appears on random position and at random time.
Have a look at the screenshot. Ignore the size, it's taken via RDP session, image on the TV is just the same.
http://s10.postimg.org/rdkzacctx/mad_VR_2016_01_25_07_58.jpg (http://s10.postimg.org/9njapaz93/mad_VR_2016_01_25_07_58.png)
Thank you.
Turns out it was my fault, after all. The decoder is quite buggy, but in this specific case it was a bug in madVR which only occurred if the decoder sent data in YUY2 format (4:2:2) with an unusual video height and when having DXVA processing (scaling, deinterlacing) active. Should be fixed in this build:
http://madshi.net/madVRbbsc2.rar
Do I still have to test with <v0.90.x
Yes, please. It's important to know if it's a new problem and which exact build introduced it.
The frame drop only occur with 3D playback, especially frame packed 3D.
Well, unfortunately I don't have any idea about that one. Nobody else has reported this specific problem yet. I would ask for a debug log, but if it only occurs after an hour of playback, by that time the debug log will probably have filled the rest of your harddisk free space, no matter how large it is... :o
MSL_DK
25th January 2016, 18:05
Yes, please. It's important to know if it's a new problem and which exact build introduced it.
I do it later tonight. DispcalGUI must be finished before I can do anything else.
bbsc
25th January 2016, 19:14
Should be fixed in this build:
http://madshi.net/madVRbbsc2.rar
Excellent.
Now everything is working as it should to. Playback, resizing, everything...
You're the best :)
Thank you very much.
Now my old HTPC has a chance to live a couple of years longer.
scollaco
26th January 2016, 01:33
I'm having issues getting 3D to work. I'm a noob so maybe I missed something.
1) I have windows 10 and the latest 6th generation NUC with Intel Iris Pro 540 Graphics. (NUC6i5syk).
2) I installed madVR v.0.90.3 and the latest LAV filters fromt he nightly builds (0.67.0-65).
This is what I did:
1) I set the display control panel to have 3D "on".
2) In madVR I turned off "exclusive mode". I enabled "use Direct3D11 for presentation (is this correct?) and also check marked "present a frame for every VSync" (Is this a needed step too?)
3) I didn't touch any settings in madVr's stereo 3D area besides the default that si checked "enable stereo 3d playback"
When playing a 3d mkv made using makemkv, I see that LAV filters is using the "msdk mvc" decoder.
on playing a movie, the projector correctly switches resolution to 1920x2205 for framepacked 3D. However the image that shows up is frozen and the movie doesn't play any further. At that point I cannot exit out of my MPC-BE player and need to kill it using the task manager. I'm stuck because it looks like it all correctly switches to 3d and I have a proper 3d image on screen, but it is frozen and refuses to play the movie.
I also tried setting my scaling algorithms to the most basic but still same issue. Any advice what I'm doing wrong or what step I'm missing?
Tarzan
26th January 2016, 09:52
Hi!
I'm trying to run a automatic CIH setup by cropping the bottom and top part om my ~2,37:1 screen, using only an active screen area of 1920x810, but I cant get it to work. By work I mean always setting the height of the active area of the image to 810 pixels, unless the AR is wider than 2,37:1 of course.
What i've done is:
Screen config:
Define visible screen are by cropping masked borders: 135 bottom and 135 top.
Zoom control:
[x] automatically detect hard coded black bars
[x] zoom small black bars away
[x] crop black bars
In mpc-hc the video frame is set to touch window from inside.
For now the only option that seem to do anything is "if there are big black bars ... zoom the bars away completely", but this option also crops bottom and top content from 16:9 content and doesn't respond to changes in AR in a movie at all. Am I missing something?
Other than not having to manually set the zoom for cinescope content within a 16:9 video I would be happy to be able to watch grand budapest hotel showing a minimum of black bars throughout the movie.
I'm using Windows 10, MPC-HC, Madvr v0.90.3 and a Sony vpl-hw20 (which doesn't have a lens memory function).
Clammerz
26th January 2016, 10:45
and doesn't respond to changes in AR in a movie at all.
Make sure you don't have the MPC option View->Video Frame->"Keep Aspect Ratio" enabled.
madshi
26th January 2016, 11:03
I'm having issues getting 3D to work. I'm a noob so maybe I missed something.
1) I have windows 10 and the latest 6th generation NUC with Intel Iris Pro 540 Graphics. (NUC6i5syk).
2) I installed madVR v.0.90.3 and the latest LAV filters fromt he nightly builds (0.67.0-65).
This is what I did:
1) I set the display control panel to have 3D "on".
2) In madVR I turned off "exclusive mode". I enabled "use Direct3D11 for presentation (is this correct?) and also check marked "present a frame for every VSync" (Is this a needed step too?)
3) I didn't touch any settings in madVr's stereo 3D area besides the default that si checked "enable stereo 3d playback"
When playing a 3d mkv made using makemkv, I see that LAV filters is using the "msdk mvc" decoder.
on playing a movie, the projector correctly switches resolution to 1920x2205 for framepacked 3D. However the image that shows up is frozen and the movie doesn't play any further. At that point I cannot exit out of my MPC-BE player and need to kill it using the task manager. I'm stuck because it looks like it all correctly switches to 3d and I have a proper 3d image on screen, but it is frozen and refuses to play the movie.
I also tried setting my scaling algorithms to the most basic but still same issue. Any advice what I'm doing wrong or what step I'm missing?
Are you using x86 or x64 version of MPC-BE? If you're using x64, try x86 instead, just to double check.
I'm trying to run a automatic CIH setup by cropping the bottom and top part om my ~2,37:1 screen, using only an active screen area of 1920x810, but I cant get it to work. By work I mean always setting the height of the active area of the image to 810 pixels, unless the AR is wider than 2,37:1 of course.
What i've done is:
Screen config:
Define visible screen are by cropping masked borders: 135 bottom and 135 top.
Zoom control:
[x] automatically detect hard coded black bars
[x] zoom small black bars away
[x] crop black bars
In mpc-hc the video frame is set to touch window from inside.
For now the only option that seem to do anything is "if there are big black bars ... zoom the bars away completely", but this option also crops bottom and top content from 16:9 content and doesn't respond to changes in AR in a movie at all. Am I missing something?
Other than not having to manually set the zoom for cinescope content within a 16:9 video I would be happy to be able to watch grand budapest hotel showing a minimum of black bars throughout the movie.
I'm using Windows 10, MPC-HC, Madvr v0.90.3 and a Sony vpl-hw20 (which doesn't have a lens memory function).
Ok, let's analyse what's going on: Please create an empty file named "ShowBlackBars" in the madVR folder. If you do that, madVR will draw a green rectangle around the detected "active video area". Does this rectangle show the correct video area? If so, at least the black bar detection works correctly. If not, black bar detection itself fails for some reason. Are you using native DXVA decoding, maybe? Currently black bar detection doesn't work for native DXVA decoding. Any other mode should work, though.
One more thing to test would be to run natively encoded cinemascope, 16:9 and 4:3 movies (without any black bars inside of the encoded video area), just to check whether the video is zoomed correctly in your setup then?
FWIW, with Budapest Hotal don't always expect instant detection of new black bar configurations. Depending on the situation detection *can* be instant, but it can sometimes also take 10-15 seconds. Once one specific black bar configuration was detected, though, switching back to it again should be instant then.
Make sure you don't have the MPC option View->Video Frame->"Keep Aspect Ratio" enabled.
Hmmm... Doesn't that only affect AR and not the whole zoom? Not sure, though.
chros
26th January 2016, 12:12
Whoever has windows 8.1 and windows 10 , do like that, it boosted my performance in Skyrim from 28 to 60+ . windows 8.1 and windows 10 are bugged with full of bad settings that worked in windows 7 just fine. In windows 7 I got 100+ fps in skyrim. even with LOW everything the FPS stayed 28 , no way it is possible with 970 GTX and 3770K 4.3 Ghz I will get this kind of fps. This setting from here http://www.ibtimes.co.uk/windows-10-how-fix-sluggish-performance-boost-overall-system-speed-1516413 Fixed the issue. I will do it on my laptop 8.1 too and see how it improved things. it might fix stupid bugs in the media player that we use, because we use Exclusive mode and it's like gaming, should work the same.
I'll be curious whether win8.1 will be also fixed by this. It's an old trick (from WinXP age). Do you have SSD in both or just HDD?
I'm not sure whether I've applied this on my laptop that has SSD (win8.1) but I'll check it this evening and if not I'd definitely set this! Thanks for mentioning!
MSL_DK
26th January 2016, 12:24
I do it later tonight. DispcalGUI must be finished before I can do anything else.
Okay ... I have tested with version 0.89.16 Same problem. Everything is updated to the latest version, Lav Filters, etc.
madshi
26th January 2016, 12:28
I get an error in the upper left corner that says something like: Could not read display mode. It only happens if I disable FSE. AMD control panel crashes and windows behave very strangely and I will have to restart.
Windows 10 x64
MPC-HC x86 latest
madVR x86 latest
AMD R9 270 with latest driver
Display 1920x1080 60Hz
Try installing a different GPU driver. It's probably a GPU driver bug. Or if you have a Crossfire setup, try disabling Crossfire.
MSL_DK
26th January 2016, 12:52
Try installing a different GPU driver. It's probably a GPU driver bug. Or if you have a Crossfire setup, try disabling Crossfire.
Jeez ... I'm so tired of AMD and Windows 10 :/ I try to install version 15.7.1 and returns the result.
MSL_DK
26th January 2016, 13:03
Jeez ... I'm so tired of AMD and Windows 10 :/ I try to install version 15.7.1 and returns the result.
Solved nothing. It must be a Windows bug.
EDIT: Just want to add that it is a clean Windows 10 installation, nothing but, MPC-HC, Lav Filters and madVR is installed.
huhn
26th January 2016, 13:17
i have a r9 270 and windows 10 too.
what type of display and windows 10 version are you running currently? and what type of connection is used?
MSL_DK
26th January 2016, 13:28
i have a r9 270 and windows 10 too.
what type of display and windows 10 version are you running currently? and what type of connection is used?
Windows 10 Pro x64 OS Build 10586.63
Panasonic CX700@1080p /HDMI
huhn
26th January 2016, 13:30
i try later today my r9 270 at my cx700 and the windows 10 build on that Pc should be at the 105XX
Tarzan
26th January 2016, 14:23
...
Are you using native DXVA decoding, maybe? Currently black bar detection doesn't work for native DXVA decoding. Any other mode should work, though.
...
This! I disabled hardware decoding and now it's working.
Thank you!
MSL_DK
26th January 2016, 14:47
i try later today my r9 270 at my cx700 and the windows 10 build on that Pc should be at the 105XX
That would be great :thanks:
madshi
26th January 2016, 15:10
This! I disabled hardware decoding and now it's working.
FWIW, you can use DXVA copyback, or really any other mode. The only one which doesn't work for black bar detection is "native DXVA".
Backflash
26th January 2016, 15:30
Freesync question.
I have range of 35-90hz( windows10 stable update 1 build, r9 390 crimson 16.1), i keep it at 90 due to how windows sometimes doesn't switch monitor back on if i leave it idle and keep it at 120hz in desktop. i don't know if it's driver or windwos issue with displayport or maybe a monitor hard to tell.
Is there a way to make windows switch to 72hz when madvr is running? it shouldn't even blackscreen monitor for that.
Oh and, i have same 0.90.x display driver crash that can't recover - have to hard reset, 0.90 is very rare so i use that but 0.90.x+ crashes often.
madshi
26th January 2016, 15:40
Freesync question.
I have range of 35-90hz( windows10 stable update 1 build, r9 390 crimson 16.1), i keep it at 90 due to how windows sometimes doesn't switch monitor back on if i leave it idle and keep it at 120hz in desktop. i don't know if it's driver or windwos issue with displayport or maybe a monitor hard to tell.
Is there a way to make windows switch to 72hz when madvr is running? it shouldn't even blackscreen monitor for that.
I have no Freesync monitor so I can't help you there.
Oh and, i have same 0.90.x display driver crash that can't recover - have to hard reset, 0.90 is very rare so i use that but 0.90.x+ crashes often.
Are you using x86 or x64 version of your media player and madVR? If you're using x64, try using x86 instead to see if you have the same display driver crash problem with that. If you have the same crashes in x86, then please look at this post:
http://forum.doom9.org/showthread.php?p=1754526#post1754526
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.