madVR - high quality video renderer (GPU assisted)

[Anime Viewer]

According to your log the Direct3D device is tied to the Intel GPU and as a result OpenCL is also executed on the Intel GPU. Are you sure you really forced the NVidia GPU active? Here's a test build which prefers NVidia/AMD over Intel, if both are available. Maybe it helps?

http://madshi.net/madVRoptimus.rar




I also have an Optimus system, and I can confirm that I have the Nvidia as the forced GPU for the renamed mpc-hc2.exe, and I have the green screen too. I tried the madVRoptimus.rar madvr.ax and the problem still exists. If you'd like me to submit a bug log too in case it will tell you anything new let me know how to go about it.

[madshi]

I also have an Optimus system, and I can confirm that I have the Nvidia as the forced GPU for the renamed mpc-hc2.exe, and I have the green screen too. I tried the madVRoptimus.rar madvr.ax and the problem still exists. If you'd like me to submit a bug log too in case it will tell you anything new let me know how to go about it.
A log won't help. Try this build, which has OpenCL forcefully disabled for Intel and AMD GPUs:

http://madshi.net/madVRoptimus2.rar

If that build doesn't work, either, there's probably not much I can do.

[n2k3]

Hey, I was wondering why my two CRT monitors show up under 1 device, now I can't choose a 3dlut file for the monitors individually.
They both have a unique name from the driver, and they both have a unique id, and have different raw EDID's.
This has been going on for some versions now, not just the latest one

http://i.imgur.com/0CboZgy.png

[madshi]

Hey, I was wondering why my two CRT monitors show up under 1 device, now I can't choose a 3dlut file for the monitors individually.
They both have a unique name from the driver, and they both have a unique id, and have different raw EDID's.
This has been going on for some versions now, not just the latest one
Judging by the screenshot, your display has 2 different identifications. Try manually creating a new display device in the madVR devices setup, then drag & drop one of the identification cards to the new device. Does that help?

[n2k3]

Judging by the screenshot, your display has 2 different identifications. Try manually creating a new display device in the madVR devices setup, then drag & drop one of the identification cards to the new device. Does that help?

Oh wow, I didn't know that was possible (not really intuitive) :D
I'll try when I'm back home (in 2 hours) to see if this worked, thanks!

[madshi]

Oh wow, I didn't know that was possible (not really intuitive)
It was the most intuitive solution that came to my mind. Of course if you don't know that it's possible it might be hard to find. But if you actually think about it logically: If you want to manually redefine the way the identifications are interpreted by madVR, drag&dropping them with the mouse from one display to another is the easiest way to achieve that.

Now one key question would be why in your case you had 2 identifications in one display. That's not normal behaviour. But I guess both monitors are the same model and manufacturer? Maybe even the same serial number of something? There are certain situations when madVR sees a slightly different EDID block but thinks that it's probably the same because it's nearly identical. This can happen in real life. E.g. depending on settings some receivers/TVs output slightly different EDID blocks. So madVR checks some things (like model, serial number) to find out how likely it is that it's the same display. In your case it seems madVR thought that both displays would be one and the same.

[chano22000]

Hello,

Since v0.87, "settings can now be edited without madVR running".

How to proceed ?

I would like to have a shortcut to open madvr property page (such as rundll.exe madvr.ax openconfiguration).

Thank you.

[n2k3]

It was the most intuitive solution that came to my mind. Of course if you don't know that it's possible it might be hard to find. But if you actually think about it logically: If you want to manually redefine the way the identifications are interpreted by madVR, drag&dropping them with the mouse from one display to another is the easiest way to achieve that.

Now one key question would be why in your case you had 2 identifications in one display. That's not normal behaviour. But I guess both monitors are the same model and manufacturer? Maybe even the same serial number of something? There are certain situations when madVR sees a slightly different EDID block but thinks that it's probably the same because it's nearly identical. This can happen in real life. E.g. depending on settings some receivers/TVs output slightly different EDID blocks. So madVR checks some things (like model, serial number) to find out how likely it is that it's the same display. In your case it seems madVR thought that both displays would be one and the same.

It works, thanks!

Yes, both are the same model (P1220) and same manufacturer (Compaq), same Plug and Play ID (CPQ1421), same manufacture date (week 4 of 2002), but not same serial number. There's an odd thing about one of the screens serial numbers though, it's a negative number :o (as detected by MonInfo). And yes the raw EDID is very similar, only a couple of bytes are different.

And here's why it wasn't intuitive, because in previous versions madVR always detected my two monitors as separate devices, until it didn't. No idea why, but possibly related to me fiddling with EDID override software, which I needed to force certain refresh rates at certain resolutions (possible that it's not even be madVR related). So I had no idea dragging was an option. The thing about the config menu is that it's list based with folder icons which you can fold open some stuff, and usually the only thing you can do then is click on them to activate it. So the idea to first create a new device (which from my perspective is also weird, because then I thought what do I do with this?) and then drag the identification list element to the new device would've never occurred to me. Until recently I also had no idea I could create profiles by right clicking the folders.

One quick (unrelated) question, I suppose Smooth Motion isn't really applicable to a CRT monitor running at 100hz ?

[madshi]

Since v0.87, "settings can now be edited without madVR running".

How to proceed ?

I would like to have a shortcut to open madvr property page (such as rundll.exe madvr.ax openconfiguration).
You can make a shortcut with "madHcCtrl.exe editLocalSettingsDontWait".

Yes, both are the same model (P1220) and same manufacturer (Compaq), same Plug and Play ID (CPQ1421), same manufacture date (week 4 of 2002), but not same serial number. There's an odd thing about one of the screens serial numbers though, it's a negative number :o (as detected by MonInfo). And yes the raw EDID is very similar, only a couple of bytes are different.

And here's why it wasn't intuitive, because in previous versions madVR always detected my two monitors as separate devices, until it didn't. No idea why, but possibly related to me fiddling with EDID override software, which I needed to force certain refresh rates at certain resolutions (possible that it's not even be madVR related).
Yes, the EDID override would nicely explain the problem. It might make both monitors look like having the same serial number to madVR, which would explain why madVR thought it's the same display.

So I had no idea dragging was an option. The thing about the config menu is that it's list based with folder icons which you can fold open some stuff, and usually the only thing you can do then is click on them to activate it. So the idea to first create a new device (which from my perspective is also weird, because then I thought what do I do with this?) and then drag the identification list element to the new device would've never occurred to me. Until recently I also had no idea I could create profiles by right clicking the folders.
Well, my GUI design philosophy is: Try what makes sense to you, and it might actually work. Maybe my thinking of what makes sense it different from yours, that would then explain why you consider is non-intuitive. But I don't really see how to make the same features available in a better way. Ok, I guess I could add a context sensitive menu and button toolbar, but that's too much work at this stage of madVR development...

One quick (unrelated) question, I suppose Smooth Motion isn't really applicable to a CRT monitor running at 100hz ?
I don't know. For PAL content probably it would be useless. If you can't switch the CRT to a refresh rate that is a simple multiply of the video framerate then maybe Smooth Motion FRC could be helpful. Just give it a try and trust your eyes.

[chano22000]

You can make a shortcut with "madHcCtrl.exe editLocalSettingsDontWait".


Thank you !

[Anime Viewer]

A log won't help. Try this build, which has OpenCL forcefully disabled for Intel and AMD GPUs:

http://madshi.net/madVRoptimus2.rar

If that build doesn't work, either, there's probably not much I can do.

I'm happy to report that worked, and NNEDI3 now appears to be working on my system. (Both when running on the Nvidia and when running on the Intel). :D

[bxyhxyh]

When I watch YV12 or YV16 video using madvr renderer, color changes. YV24 is ok.
Is it bug or something?
I didn't change defaults.
http://screenshotcomparison.com/comparison/68836

[truexfan81]

I am pleased to report that with my gtx650 i can use nnedi3 luma doubling with 32neurons for certain content, and 16 for others, so i have made some more profiles, and it all works quite well. :D

Great Job Madshi

[JonnyRedHed]

Can I ask, how do you make profiles auto switch with SD and versions of HD content. If my play list goes from a SD to a HD and back, to have profiles switch automatically.

Thank you.

[madshi]

I'm happy to report that that worked for me, and NNEDI3 now appears to be working on my system. (Both when running on the Nvidia and when running on the Intel). :D
Are you sure that NNEDI3 is really active and that it isn't just silently disabled? Please double check by looking at the rendering times.

When I watch YV12 or YV16 video using madvr renderer, color changes. YV24 is ok.
Is it bug or something?
I didn't change defaults.
http://screenshotcomparison.com/comparison/68836
Not enough information. Which format is the source encoded in? h264 4:2:0 8bit? Or something else? Which video decoder are you using? Why do you test with YV12, YV16 and YV24?

You should probably double check the decoding matrix. Try switching it by pressing Ctrl+Alt+Shift+M multiple times. Does that change anything?

[truexfan81]

Can I ask, how do you make profiles auto switch with SD and versions of HD content. If my play list goes from a SD to a HD and back, to have profiles switch automatically.

Thank you.

make 2 profiles one for SD and one for HD, then make a rule for example
if (srcHeight <= 720) "SD"
else "HD"
you can change the number to whatever you need it to be, but its that easy

this (http://forum.doom9.org/showthread.php?p=1271417#post1271417) will also help you out

[leeperry]

someone earlier mentioned:
if (srcHeight <= 360) "doubling-quad2"
elseif (srcHeight <= 480) "doubling-quad"
elseif (srcHeight <= 720) "doubling-on"
else "doubling-off"
doubling-quad2: Luma NNEDI3 128/16 neurons (1.5x/3x)
doubling-quad: Luma NNEDI3 64/16 neurons (1.5x/3x)
doubling-on: Luma NNEDI3 16 neurons (1.5x)
doubling-off: Everything unchecked

I'll also have to work out profiles soon, basically I can do 64x NNEDI for 720p@1080p for >=1.85 24fps but 1.78 >=24fps is no workee @64x...not too sure how to work this out without a zillion profiles yet.

[e-t172]

So I swapped back my colleague's 770 for my own 780 Ti and now that the smooth motion frame drop has been fixed (thanks again madshi), further testing reveals the following:

There is a regression in nVidia drivers 334.89 and all later versions (up to and including the latest one, 335.23) that results in noticeable presentation glitches every ~10 minutes with the GeForce 780 Ti. This doesn't seem to affect other nVidia GPUs (at least the 770 is unaffected). If you are experiencing this issue, going back to 332.21 (last good version) will fix it.

This is completely unrelated to the smooth motion frame drop bug (which was a pure madVR bug), which is why I was so confused by the results of my earlier testing while trying to troubleshoot these bugs.

[madshi]

<sigh> No end of driver trouble in sight, it seems...

[QBhd]

someone earlier mentioned:
if (srcHeight <= 360) "doubling-quad2"
elseif (srcHeight <= 480) "doubling-quad"
elseif (srcHeight <= 720) "doubling-on"
else "doubling-off"


I'll also have to work out profiles soon, basically I can do 64x NNEDI for 720p@1080p for >=1.85 24fps but 1.78 >=24fps is no workee @64x...not too sure how to work this out without a zillion profiles yet.

Frame rates also play a big role in maximizing GPU usage.

Here is a sample of mine (still a work in progress as I add profiles depending on source res/fps):

if (srcHeight < 500) "SD"
elseif (srcHeight > 500) and (srcHeight < 700) and (deintFps > 26) and (deintFps < 31) "SD 30fps"
elseif (srcHeight < 721) and (deintFps < 25) "720p24"
elseif (srcHeight < 721) and (deintFps > 26) and (deintFps < 31) "720p30"
elseif (srcHeight < 721) and (deintFps > 31) "720p60"
else "1080p"

QB

[truexfan81]

<sigh> No end of driver trouble in sight, it seems...

yep, when nvidia's drivers are not broken amd's are, it just never stops

[JonnyRedHed]

make 2 profiles one for SD and one for HD, then make a rule for example
if (srcHeight <= 720) "SD"
else "HD"
you can change the number to whatever you need it to be, but its that easy

this (http://forum.doom9.org/showthread.php?p=1271417#post1271417) will also help you out


Thanks,
Both yours and Leeperry's.. I just start to see a wall of fog... and get my 'its maths' 'or looks and smells like maths' wall of fog.



I can see where to create profiles for different features, and then there is a keyboard hotkey section and then command line. I don't know what command line means. Where does the script your talking about go.

[truexfan81]

Thanks,
Both yours and Leeperry's.. I just start to see a wall of fog... and get my 'its maths' 'or looks and smells like maths' wall of fog.



I can see where to create profiles for different features, and then there is a keyboard hotkey section and then command line. I don't know what command line means. Where does the script your talking about go.

hold on, i'll show you a screenshot of mine, i have 3 profiles for nnedi3 1 for 32neurons, 1 for 16neurons, and 1 that turns it off

edit: here ya go link (http://i.imgur.com/7lFvOsn.jpg)

had posted the pic, decided it was too big

[JonnyRedHed]

Ah I see now yes. I was clicking on the section that gave the command line, I didn't see this section. I understand now. Thank you.

[Anime Viewer]

Are you sure that NNEDI3 is really active and that it isn't just silently disabled? Please double check by looking at the rendering times.


That may be the case. Especially since it appeared I could set everything NNEDI3 to 256 neurons in all areas when configured to use the Nvidia and not see any dropped frames (leading me to believe perhaps it isn't running).

How can I judge based on render times?
The render times don't appear to be any different from when I run in any of the other upscaling or doubling formats.

[truexfan81]

madshi I have a suggestion, it would be awesome to have the ability to import and export profiles and settings to/from a file. It would be nice to be able to back those up.

[biggerpapi]

Are you sure that NNEDI3 is really active and that it isn't just silently disabled? Please double check by looking at the rendering times.

Yea I too thought it was working until I checked the rendering times and noticed they were the same when I wasn't using any nnedi3 features. So I guess they are just disabled. Maybe somebody else with an optimus system can double check that however?

[Asmodian]

madshi I have a suggestion, it would be awesome to have the ability to import and export profiles and settings to/from a file. It would be nice to be able to back those up.

Select All, Copy, open notepad, paste.. at least this is what I do. ;)

[QBhd]

Select All, Copy, open notepad, paste.. at least this is what I do. ;)

Sure that works for your script... but it does not help with the individual profiles the script calls. It would be nice to be able to export each profile separately... as of now I will be taking a screenshot to save my settings of each profile

QB

[Anima123]

Yea I too thought it was working until I checked the rendering times and noticed they were the same when I wasn't using any nnedi3 features. So I guess they are just disabled. Maybe somebody else with an optimus system can double check that however?

Very dark screen with either version once NNEDI3 enabled. I have HD 4000 with a NV 640m Optimus.

[trip_let]

HD 4000 / 650M Optimus here. Driver is 335.23, Win 8.1.

I get the dark screen + increased GPU usage for NNEDI3 enabled except on madVRoptimus2, which disables NNEDI3 (fails silently and doesn't use it at all). Well drat, same no-go as before, not like I'm expecting Nvidia to fix things any time soon. For what it's worth, I don't think (most?) Optimus users reporting in here actually have the GTX 780M or whatever that can actually handle NNEDI3, so it's not a huge loss.

[bxyhxyh]

Not enough information. Which format is the source encoded in? h264 4:2:0 8bit? Or something else? Which video decoder are you using? Why do you test with YV12, YV16 and YV24?

You should probably double check the decoding matrix. Try switching it by pressing Ctrl+Alt+Shift+M multiple times. Does that change anything?

It is same for all my bluray rips which is 720p, YV12 and YV16 colorspace videos.
Ctrl+Alt+Shift+M helps.
It is choosing BT.601 as "correct" matrix.

[Audionut]

Thanks guys for the discussion regarding profiles. I worked out how to do manual switching of profiles, but obviously, scripting is much better.

@madshi, perhaps you can add this screenshot from truexfan81 above (or similar), into post 3 of this thread. Everything made sense after looking at that single screenshot.

[John Carmack]

Today, I reinstalled Win7 and (obviously) MPC-HC, MadVR and all the cream. But I don't remember something: when using smooth motion with Hi10p content, I can get like 1 dropped frame AND presentation glitch per second even if my rendering times are between 5 and 10 ms. Using an AMD r9 280X with the 13.12 drivers and a FX8350 (I verified, none of those are getting overloaded during the playback). Does someone have an idea of what could trigger this? Oh, and Madshi, wonderful software, thank you for your dedication.

[DragonQ]

So I installed an AMD R9 270 and I'm confused. When I enable NNEDI3, the stats window stops displaying average and max stats, and the image is very choppy and no longer deinterlaced, even with 16 neurons. GPU usage shoots up but is not always 100%. Am I doing something wrong?

[jkauff]

Thanks guys for the discussion regarding profiles. I worked out how to do manual switching of profiles, but obviously, scripting is much better.

@madshi, perhaps you can add this screenshot from truexfan81 above (or similar), into post 3 of this thread. Everything made sense after looking at that single screenshot.
Have you looked at the online Help in madVR? It also has a sample script.

[mirkosp]

RGB24 and RGB32 inputs with an odd height result in a black video. RGB48 and Y410 with odd height work as expected.

[seiyafan]

So I installed an AMD R9 270 and I'm confused. When I enable NNEDI3, the stats window stops displaying average and max stats, and the image is very choppy and no longer deinterlaced, even with 16 neurons. GPU usage shoots up but is not always 100%. Am I doing something wrong?

I get the stats not to display when rendering time was up through the roof, you need to dial it down quite a lot.

[DragonQ]

Quite a lot from what? NNEDI3 16 neurons is the lowest possible to test. For downscaling I'm just using CR + AR, nothing fancy. :/

[nevcairiel]

Quite a lot from what? NNEDI3 16 neurons is the lowest possible to test. For downscaling I'm just using CR + AR, nothing fancy. :/

Which version are you using? the fixed "b" build I hope, and not the latest "official" release?
Hope madshi has a new official release soon to avoid these questions. :)

[seiyafan]

Well, I wasn't sure which resolution you use. But for me when I did 1080 -> 1440 upscaling on my 270x I couldn't get NNEDI3 to work without dropping frame on some of my videos, so the solution to those stubborn videos was simple, (1.) turn NNEDI3 off, or (2.) upgrade video card.

I did end up with a 290x and I could use NNEDI3 all I wanted :D, but I returned it later for some other reasons.

[DragonQ]

Which version are you using? the fixed "b" build I hope, and not the latest "official" release?
Hope madshi has a new official release soon to avoid these questions. :)
Yeah I'm pretty sure I installed 0.87.8b and missed 0.87.8. Will double-check that when I get home because I use MadVR on 3 machines...it's tough to keep track of which versions are on which machines!

[madshi]

That may be the case. Especially since it appeared I could set everything NNEDI3 to 256 neurons in all areas when configured to use the Nvidia and not see any dropped frames (leading me to believe perhaps it isn't running).

How can I judge based on render times?
The render times don't appear to be any different from when I run in any of the other upscaling or doubling formats.
Yea I too thought it was working until I checked the rendering times and noticed they were the same when I wasn't using any nnedi3 features. So I guess they are just disabled. Maybe somebody else with an optimus system can double check that however?
Very dark screen with either version once NNEDI3 enabled. I have HD 4000 with a NV 640m Optimus.
HD 4000 / 650M Optimus here. Driver is 335.23, Win 8.1.

I get the dark screen + increased GPU usage for NNEDI3 enabled except on madVRoptimus2, which disables NNEDI3 (fails silently and doesn't use it at all). Well drat, same no-go as before, not like I'm expecting Nvidia to fix things any time soon. For what it's worth, I don't think (most?) Optimus users reporting in here actually have the GTX 780M or whatever that can actually handle NNEDI3, so it's not a huge loss.
Lots of Optimus users here. The next build (v0.87.9) will contain a new feature which might help you, or maybe not. Give it a try.

If you want to know whether NNEDI3 is enabled, set it to 256 neurons. If the rendering times don't change much then when you enable/disable NNEDI3, then it's definitely not working. Rendering times with 256 neurons should go through the roof.

madshi I have a suggestion, it would be awesome to have the ability to import and export profiles and settings to/from a file. It would be nice to be able to back those up.
Just copy the settings.bin file. In order to go back to a stored settings.bin file, first run "restore default settings.bat", then copy the stored settings.bin file into the madVR folder. For any of this to work, madVR requires write access to its own folder. If you don't want to give madVR write access to its own folder, open regedit, browse to "HKCU\Software\madshi\madVR" and export to a reg file. Then when you later want to go back, again first run "restore default settings.bat", then double click the saved reg file.

It is same for all my bluray rips which is 720p, YV12 and YV16 colorspace videos.
Ctrl+Alt+Shift+M helps.
It is choosing BT.601 as "correct" matrix.
Two questions:

(1) Which decoder are you using?
(2) Is the decoder matrix stored in the video bitstream headers?

Generally a 720p file with BT.601 is "weird". Such a file usually uses BT.709, and that's what madVR uses by default for such files, unless the file is encoded with the information that it needs BT.601.

Today, I reinstalled Win7 and (obviously) MPC-HC, MadVR and all the cream. But I don't remember something: when using smooth motion with Hi10p content, I can get like 1 dropped frame AND presentation glitch per second even if my rendering times are between 5 and 10 ms. Using an AMD r9 280X with the 13.12 drivers and a FX8350 (I verified, none of those are getting overloaded during the playback). Does someone have an idea of what could trigger this? Oh, and Madshi, wonderful software, thank you for your dedication.
Try increasing the GPU queue size and the number of pre-presented frames for exclusive mode. Smooth motion FRC benefits from bigger queues.

So I installed an AMD R9 270 and I'm confused. When I enable NNEDI3, the stats window stops displaying average and max stats, and the image is very choppy and no longer deinterlaced, even with 16 neurons. GPU usage shoots up but is not always 100%. Am I doing something wrong?
Which PCIe version does your mainboard have? PCIe 1.x is quite slow and results in very slow OpenCL <-> Direct3D9 interop performance.

Which video resolution did you test with? Start with an SD file, just to be safe.

RGB24 and RGB32 inputs with an odd height result in a black video. RGB48 and Y410 with odd height work as expected.
This will be fixed in the next build.

[madshi]

madVR v0.87.9 released

http://madshi.net/madVR.zip

* fixed: NNEDI3 didn't work properly on AMD/Intel (introduced in v0.87.8)
* fixed: native DXVA decoding + NNEDI3 chroma up + NVidia -> green color cast
* fixed: #032: Smooth Motion FRC sometimes failed to activate
* fixed: #096: Smooth Motion FRC resulted in last/only frame being hidden
* fixed: #097: Smooth Motion FRC didn't respect "treat 25p movies as 24p"
* fixed: #098: "Treat 25p movies as 24p" now only activates up to 25.5fps
* fixed: #104: "Delay playback until ..." failed when toggling subtitles
* fixed: #113: film mode key shortcut didn't enable Smooth Motion FRC
* fixed: #124: videoLUTs were not properly restored in multi monitor setup
* fixed: #132: Image corruption when leaving FSE with 3dlut loaded
* fixed: #171: film mode activation with display mode change could crash
* fixed: #178: RGB/YUV 4:4:4 with mod2 height showed black screen
* fixed: #182: NNEDI3 chroma up neuron count wasn't properly memorized
* fixed: #187: switching subtitles triggered a short black screen
* fixed: #189: Smooth Motion FRC sometimes activated when not needed
* NNEDI3 no longer offsets by 0.5 pixel if Luma needs to be resampled, anyway
* added "HKCU\Software\madshi\madVR\OpenCL\forceVendor" override option
* modified madLevelsTweaker GUI to make intended multi monitor usage clearer
The bug tracker is now mostly cleaned up. Some bugs are marked as "acknowledged". These are either not very important/urgent, or difficult to fix. I'll fix those at some point in the future, but not soon. Some bugs are marked as "feedback". If you have open bugs in the bug tracker, please double check if any of them are marked as "feedback" and make sure you reply there. Thanks.

There's one new (hidden) feature which may help Optimus users: You can now force madVR to use a specific GPU vendor for OpenCL rendering. You can do this by manually adding the following registry value:

HKEY_CURRENT_USER\Software\madshi\madVR\OpenCL\forceVendor REG_SZ "nVidia"

Alternatively you can also use "AMD" or "Intel", of course, which will force madVR to use the specified vendor for OpenCL rendering. Of course telling madVR to use a specific vendor does not guarantee that doing so will actually work, but madVR will try. If it fails, NNEDI3 will silently be disabled.

[flashmozzg]

If you want to know whether NNEDI3 is enabled, set it to 256 neurons. If the rendering times don't change much then when you enable/disable NNEDI3, then it's definitely not working. Rendering times with 256 neurons should go through the roof.

Isn't there any more convenient method to determine if something is enabled or had silently fallen back to something else? I mean doesn't madVR report it any way? Like it can make options red or grayed out if they do not work or something with annotation to explain.

[madshi]

It's not that easy. The same settings may work on monitor 1 but not on monitor 2, if the two monitors are driven by different GPUs. So I can't just make things red in the settings dialog. However, madVR could show some sort of OSD complaint, I guess, if an enabled setting doesn't work.

[leeperry]

Frame rates also play a big role in maximizing GPU usage.

Here is a sample of mine (still a work in progress as I add profiles depending on source res/fps)
Oh, very nice! But pretty much all 1.78 720p25 files allow me to go 64x neurons for luma, all queues fill in instantly....OTOH there are 1.78 720p24 movies that don't fill the queues at all, but 1.85 720p24 always does. I'm using software decoding so I don't really understand why, all this to say that I can't really make rules at this point as I usually try 64x and should it drop frames I revert to 32x. I can always use 64x for SD.

I could provide samples should madshi want to investigate but I'm more than likely experiencing the random interop lag :mad:

I'm still extremely impressed by pictures viewing with 256 neurons for chroma/luma, I guess a few years from now we'll be able to go crazy on NNEDI settings with motion pictures....hopefully nvidia will become a viable option as that random lag with AMD is unacceptable.

[flashmozzg]

Yep, that would be good. Because with, for example, dithering it's nearly impossible to tell if it works on normal videos without any alert if you haven't followed the discussion int this thread.

[sandman7920]

In latest build (0.87.9) nod32 detect madHcCtrl.exe as a threat.

http://madshi.net/madVR.zip » ZIP » madHcCtrl.exe probably unknown NewHeur_PE virus

[DragonQ]

Which PCIe version does your mainboard have? PCIe 1.x is quite slow and results in very slow OpenCL <-> Direct3D9 interop performance.
It's an Asus P6T Deluxe V2, so PCI-E 2.0.

Which video resolution did you test with? Start with an SD file, just to be safe.
Yes, I was using a 720x576i/25 file.

I'll try 0.87.9 in a minute.