madVR - high quality video renderer (GPU assisted)

[romulous]

@jmonier: Zoom has its own setting to control madVR's Smooth Motion. Check the following and disable it if it is enabled:
http://i.imgur.com/lQTWXyW.png

[dansrfe]

Originally Posted by romulous

@jmonier: Zoom has its own setting to control madVR's Smooth Motion. Check the following and disable it if it is enabled:
http://i.imgur.com/lQTWXyW.png

That's not a good move by the ZoomPlayer devs IMHO. That's two places for the same setting and AFAIK only madVR knows when to change it's own value on the interface and that's when it changes the value itself. ZoomPlayer changing the value behind madVR's back or the other way around while either of the two is running is a setup for unwanted behavior and on the road for increased debugging headaches.

[jkauff]

Originally Posted by dansrfe

That's not a good move by the ZoomPlayer devs IMHO. That's two places for the same setting and AFAIK only madVR knows when to change it's own value on the interface and that's when it changes the value itself. ZoomPlayer changing the value behind madVR's back or the other way around while either of the two is running is a setup for unwanted behavior and on the road for increased debugging headaches.

I think if you uncheck Smooth Motion in Zoom options, it completely ignores the setting in madVR options. The only rationale I can see for this is perhaps a bug in Zoom code that doesn't process the setting in madVR the way it should. It can't be for user convenience, because the setting is disabled by default in madVR.

Since this "feature" is only in the beta version, maybe they'll ditch it for the final release.

[jmonier]

Originally Posted by romulous

@jmonier: Zoom has its own setting to control madVR's Smooth Motion. Check the following and disable it if it is enabled:
http://i.imgur.com/lQTWXyW.png

Thanks. I was aware of the option but the language is ambiguous and I had interpreted it as simply allowing Smooth Motion to be used. What it does, in fact, is to absolutely turn it on or off at the beginning of playback. Once playback is started, however, it has no effect and madVR has control via the dialog or keyboard shortcut.

It does allow you to control it from ZP via a keyboard shortcut or the Communications API when you cannot do it from madVR, i.e. when nothing is playing. This could be useful. That does make it confusing, however.

[romulous]

Originally Posted by jmonier

What it does, in fact, is to absolutely turn it on or off at the beginning of playback.

Correct.

Once playback is started, however, it has no effect and madVR has control via the dialog or keyboard shortcut.

Correct again. madVR controls it whether it is used or not while a video is playing - Zoom just enables or disables the setting to begin with.

It does allow you to control it from ZP via a keyboard shortcut or the Communications API when you cannot do it from madVR, i.e. when nothing is playing.

Also correct.

language is ambiguous and I had interpreted it as simply allowing Smooth Motion to be used

Do you have any suggestions for alternate wording? If so, I will put it to Blight.

[jmonier]

Originally Posted by romulous

Do you have any suggestions for alternate wording? If so, I will put it to Blight.

"Turn on/off madVR Smooth Motion (overrides MadVR option)" ?

[romulous]

What about if we add the 'override' bit to the end of the current naming? As in:
"Enable MadVR's smooth motion (over-ride madVR option)"

I don't think we need both the enable/disable bit in the text - just one of those should be fine. The confusion is not so much about whether ticking the option will enable something, or will disable something - but more so that the option affects madVR's option. That bit needs to be made clearer.

[jmonier]

Originally Posted by romulous

What about if we add the 'override' bit to the end of the current naming? As in:
"Enable MadVR's smooth motion (over-ride madVR option)"

I don't think we need both the enable/disable bit in the text - just one of those should be fine. The confusion is not so much about whether ticking the option will enable something, or will disable something - but more so that the option affects madVR's option. That bit needs to be made clearer.

That would be better, but to my mind it still doesn't make it clear that un-checking the option also controls madVR.

Maybe: "...(always over-rides madVR option)"

[romulous]

Cool, that sounds fine to me. I will put it to Blight that the option be renamed to "Enable MadVR's smooth motion (always over-rides madVR option)".

[madshi]

madVR v0.86.11 released

http://madshi.net/madVR.zip

* added import option for eeColor 3dluts (e.g. from LightSpace CMS)

[jkauff]

Originally Posted by romulous

Cool, that sounds fine to me. I will put it to Blight that the option be renamed to "Enable MadVR's smooth motion (always over-rides madVR option)".

Does the Zoom checkbox enable "Use always" or "Use only when needed"? Will that be clear to the user?

[jmonier]

Originally Posted by jkauff

Does the Zoom checkbox enable "Use always" or "Use only when needed"? Will that be clear to the user?

It does whatever is checked in madVR. It controls the overall use of Smooth Motion but not the way in which it is applied.

[romulous]

Yes, as jmonier has stated, the option in Zoom only controls the state of this option here:
http://i.imgur.com/s9cDfmR.png (the one inside the red rectangle)

Everything else outside that is controlled by madVR, specifically by what the user has set inside madVR's options dialog - so while Zoom can switch Smooth Motion on and off, madVR itself decides if Smooth Motion will be used (and if so, how) when it is enabled. There isn't enough room in the Zoom options dialog to put a whole paragraph on it, but as well as renaming the option in that dialog, I will ask Blight to make it clear in the Zoom help file that this option only changes the enable/disable state of Smooth Motion, and nothing else (the help file for Zoom is only updated for each stable release, so the help file does not yet list the "enable madVR's smooth motion" option - but it will).

[pankov]

I think that it will be better if there is a third state (cbGrayed) for this option in Zoom Player with the meaning of "don't change anything - respect madVR's settings" and this should be the default state. Otherwise madshi will get a lot of complaints from ZP users that madVR's options don't work.

[romulous]

@pankov: I've added that idea to the tracker report.

[jmonier]

Originally Posted by pankov

I think that it will be better if there is a third state (cbGrayed) for this option in Zoom Player with the meaning of "don't change anything - respect madVR's settings" and this should be the default state. Otherwise madshi will get a lot of complaints from ZP users that madVR's options don't work.

Once the changed wording is put in, there will be a lot less chance of these complaints, but I agree that it could still be a problem.

If this third choice is put in it would have to disable the fnMadVRSmoothMo ZP Function, thus breaking any skinning, keyboard shortcut or script that uses this Function. So, there is a possibility of confusion, no matter what, unless the feature and the ZP Function is removed completely. Since I feel that the feature has value, I think that it should be retained as is (but with the changed wording and with a clear description in the documentation).

[burfadel]

Would Directx 11.2 provide any benefits for MadVR? If so, any plans to implement them for Windows 8.1 when it comes out?

[dbcooper]

Hi All, is it confirmed that MadVR can disable the default windows LUT when it plays video and uses a 3DLUT?

[dansrfe]

Originally Posted by dbcooper

Hi All, is it confirmed that MadVR can disable the default windows LUT when it plays video and uses a 3DLUT?

devices -> [your_device] -> calibration -> disable GPU gamma ramps

[dbcooper]

Cheers. That's what I've been doing. I assume that Fullscreen Exclusive mode must be used?