madVR Options Explained

[Nullack]

Thanks mate I appreciate your words of wisdom

[CarlosCaco]

What the new option "use Sigmoidal light" on image upscaling does?

[Asmodian]

What the new option "use Sigmoidal light" on image upscaling does?

Finally added a description; description borrowed from the DitherTools (http://avisynth.nl/index.php/Dither_tools) manual.

Updated for madVR v0.90.3

[Asmodian]

Updated for madVR v0.90.4

[Asmodian]

Updated for madVR v0.90.12.

A lot of improvements in madVR but the only major change for this post was removal of all mention of Jinc only being for upscaling and 3D doesn't crash anymore. :)

[Siso]

Excellent explanation to the madvr options, will there be an info for the stats in madvr etc. "average rendering time, present" and more?

For example I'm kinda confused which of the two modes are good for my card gtx 550 ti, the "present" stats are different and I don't know what they mean exactly.

http://t1.someimage.com/UYsBa8K.jpg (https://someimage.com/UYsBa8K) http://t1.someimage.com/3bSCuNP.jpg (https://someimage.com/3bSCuNP)

[huhn]

you can usually ignore present times unless you have an issue.

present times has "nothing" to do with performance. of cause this is over simplified.

[JarrettH]

I have a 550 Ti too. It's still capable of quite a lot. :cool:

[Siso]

I have a 550 Ti too. It's still capable of quite a lot. :cool:

Yeah, it has some sort of good potential :D

[CountryBumkin]

I think it would be great if you could add some information on the first page (or so) that explains a little about what the Queue numbers and Render/Present times mean.

It would help us "madVR-challenged" to understand what is going on when things don't work/look just right.

For example my "Present Queue" is 0-1/8 and "Render Queue" is 1-2/8. And I have a lot of dropped frames.

I believe a low Present Queue means that my computer is too weak for the settings. Is this correct?

Also my Present Time is 4.02ms and the Rendering Time is 86.41ms. What is the acceptable Rendering Time(s)?


BTW - I am so clueless on this stuff, it took me ten tries to answer the spam question in order to post.

[Asmodian]

I don't think I want to put more of that kind of information in the first post, it is meant to be a description of all the options, not really a guide. I want to keep the beginning of the post limited to only describing options.

I think I do mention everything you need to know about queues and present times already, but in the second post.

CPU queue size: [16] The buffer in system memory for decoded video and xySubFilter subtitles.
GPU queue size: [8] The buffer in the graphics memory for madVR’s rendering.
how many video frames shall be presented in advance or how many backbuffers shall be used: [8 or 3] A final buffer after madVR is done rendering.

At the start of "More Advanced Topics" I have:
"The sum of the average stats "deinterlace" (if present), "rendering", and "present" should be a bit below the frame time in the line "v-sync [X] ms, frame [Y] ms" to avoid dropped frames and presentation glitches."

Is this the information you were looking for or is there something else you want to know? Do I need a "Trouble Shooting" section in "Advanced Topics" so people do not miss it? Or maybe simply a "madVR OSD" section instead? I think I like that idea, I will add that before Advanced Topics.

I did update the description of "how many video frames shall be presented in advance" to:
how many video frames shall be presented in advance or how many backbuffers shall be used: [8 or 3] The present queue, a final buffer in DirectX, after madVR sends completed frames to Windows.

Is this better?

Thanks. :)

[CountryBumkin]

I think I do mention everything you need to know about queues and present times already, but in the second post.

CPU queue size: [16] The buffer in system memory for decoded video and xySubFilter subtitles.
GPU queue size: [8] The buffer in the graphics memory for madVR’s rendering.
how many video frames shall be presented in advance or how many backbuffers shall be used: [8 or 3] A final buffer after madVR is done rendering.

At the start of "More Advanced Topics" I have:
"The sum of the average stats "deinterlace" (if present), "rendering", and "present" should be a bit below the frame time in the line "v-sync [X] ms, frame [Y] ms" to avoid dropped frames and presentation glitches."

Do I need a "Trouble Shooting" section in "Advanced Topics" so people do not miss it? Or maybe simply a "madVR OSD" section instead? I think I like that idea, I will add that before Advanced Topics.

I did update the description of "how many video frames shall be presented in advance" to:


Is this better?

Thanks. :)

I would love to see a "Troubleshooting Section". I think it would be very helpful to those of us that are technically challenged in this area.

I found this info posted by madshi (about page 10 of madVR thread):

If you want to give madVR even a chance to achieve smooth playback you have to achieve an "average gpu rendering time" that is a notch lower than the "movie frame interval". I'd say it should not be higher than 35ms for 23.976 playback.

Now the optimal configuration for madVR is if you drive the display with the same refresh rate the source is in (in your case 23.976Hz). If you have to use 59.940Hz, things get slightly more difficult for madVR. In that case you may have to bring "average gpu rendering time" down even more.


and

Originally Posted by yesgrey3 View Post
The frame rendering is ~14ms. For playing in my monitor at 72Hz (13.9ms) is not enough, but should be fine to use with my projector at 48Hz (20ms). If I use Lanczos or Spline resampling the rendering time jumps to ~20ms, so I should not be able to use those resamplers with smooth playing...

You would be right if madVR needed to draw a *new* Blu-Ray frame every VSync. But if it did that, you'd get 3x respectively 2x as fast movie playback as you should get. madVR has to skip lots of VSyncs with your refresh rates. Because of that the most important reference time is not the "vsync interval" but the "frame interval".

This is the "kind of info" I am looking for when it comes to troubleshooting (understand the Stats).

Thanks for your help.

[Asmodian]

From your post I take it that:

The sum of the average stats "deinterlace" (if present), "rendering", and "present" should be a bit below the frame time in the line "v-sync [X] ms, frame [Y] ms" to avoid dropped frames and presentation glitches.

Did not tell you all this already? Everything covered in your post is what I was trying to communicate with that line.

I am having trouble understanding if you want any new information or simply didn't understand what I was trying to say with that line. Do I just need to rephrase it or add an entirely new section? Adding a new section will not help if the problem is with understanding what I wrote instead of actually missing information.

edit: Does this example I included help clarify it?
The sum of the average stats "deinterlace" (if present), "rendering", and "present" should be a bit below the frame time, Y, in the line "v-sync [X] ms, frame [Y] ms" to avoid dropped frames and presentation glitches. For example, progressive 29.97 fps video has a new frame every 33.37 ms so "rendering"+"present" needs to be a few ms below 33.37 ms. 23.976 fps video has a new frame only every 41.71 ms so you can use more demanding settings with lower frame rate video. Exactly how far below the frame time is required for glitch free playback is dependent on the system but a few milliseconds is usually sufficient.

[Warner306]

Bump.

[Asmodian]

Bump.

Thanks. I finally updated to 90.17, I used your description for the anti-bloating filter.

This reduces the fatness created by line sharpeners. Not needed for crispen edges, which is already "skinny."

[Asmodian]

Updated for madVR v0.90.18.

Another artifact removal option, 'reduce ringing artifacts'! :)

[Asmodian]

Updated for v0.90.20.

New flow chart.

[e-t172]

After some experiments I've noticed (http://forum.doom9.org/showthread.php?p=1768980#post1768980) that the way 3DLUTs and GPU gamma curves work can be a bit counter-intuitive at times. I have a suggestion:

Change:

calibrate this display by using external 3DLUT files: Use a calibration package such as Argyllcms, Calman, or LightSpace to generate a 256x256x256 3DLUT to perform a full calibration. For Argyllcms see this AVS Forum thread (http://tinyurl.com/nx87y7c), for Calman (http://tinyurl.com/map94jl), or for LightSpace (http://www.lightillusion.com/madvr_manual.html).
disable GPU gamma ramps: This disables the Windows calibration or monitor profile. It affects everything displayed, not only madVR. madVR will restore the profile when it is closed. This option changes its behavior when using the 'rendering -> general settings' option 'enable windowed overlay' to only apply to madVR because madVR is emulating the gamma ramps in that case.

To:

calibrate this display by using external 3DLUT files: Use a calibration package such as Argyllcms, Calman, or LightSpace to generate a 256x256x256 3DLUT to perform a full calibration. For Argyllcms see this AVS Forum thread (http://tinyurl.com/nx87y7c), for Calman (http://tinyurl.com/map94jl), or for LightSpace (http://www.lightillusion.com/madvr_manual.html). If the provided 3DLUT file contains calibration curves (e.g. in the case of ArgyllCMS, the collink "-a" or "-H" options were used), madVR will load the calibration curves into the system-wide GPU hardware gamma ramps, which affects everything displayed, not just madVR. madVR will restore the original gamma ramps (if any) when it is closed.
disable GPU gamma ramps: Clears system-wide GPU gamma ramps (monitor calibration), if any, replacing them with linear (no-op) curves. This affects everything displayed, not just madVR. madVR will restore the original GPU gamma ramps (if any) when it is closed. This option changes its behavior when using the 'rendering -> general settings' option 'enable windowed overlay' to only apply to madVR because madVR is emulating the gamma ramps in that case. This option has no effect if a 3DLUT file that contains calibration curves is loaded (see above).

(I also took the liberty of avoiding the term "profile", which is confusing because an ICC profile contains more than just calibration curves.)

[Asmodian]

After some experiments I've noticed (http://forum.doom9.org/showthread.php?p=1768980#post1768980) that the way 3DLUTs and GPU gamma curves work can be a bit counter-intuitive at times. I have a suggestion:
..snip..
(I also took the liberty of avoiding the term "profile", which is confusing because an ICC profile contains more than just calibration curves.)

I like it! Done. :D

More precise and very useful information. I also have enough characters to expand that section a bit.

Thanks. :)

[Asmodian]

Updated to v0.90.21, no changes. ;)

[Asmodian]

Updated for madVR v0.90.23, added a section for hdr.

[Asmodian]

Added a section for the empty file based hidden options for madVR.

[leeperry]

Added a section for the empty file based hidden options for madVR.

Sweet, thanks!

I believe ShowBlackBars isn't active anymore but DontRenderAfterStop definitely seems to help with hiccuping during transitions between movies with PotPlayer in seamless playback :)

madshi kept telling me that it was PotP's fault and PotP's coder said it was mVR's so I shall run more tests but closing PotP even seems snappier now.

[Asmodian]

Sweet, thanks!

I believe ShowBlackBars isn't active anymore but DontRenderAfterStop definitely seems to help with hiccuping during transitions between movies with PotPlayer in seamless playback :)

madshi kept telling me that it was PotP's fault and PotP's coder said it was mVR's so I shall run more tests but closing PotP even seems snappier now.

Glad it helped. :)

"ShowBlackBars" is still active, I just tested it with madVR v0.90.23.

[Light001]

Looking for help Again

i5 3550 4.1ghz, Gtx 980, windows 10 pro 64bit and most recent nvidia driver. BenQXl2420T, i watch mostly pirated 1080p Quality vidoes with some older shows 480p. My monitor only supports 60hz and 100hz and 120hz. I used Tft Centrals color calabration for my monitor. Watching things like game of thrones using madvr and Mpc-hc its abit dark unless i turn up brightness. Do i touch anything in the Nvidia Control Panel? under Video ? (Edge Enhance,Noise Reduc,Deinterlacing-unverse telecine)??
Under Devices I do not know what should be set, i assume the pc levels 0-255 is fine and 8 bit for native display? 3d format is auto. calibration is set to disable display modes is also unchecked color and gamma is left alone and hdr which is new, i selected the top option.

Processing All unchecked, Artifact removal unchecked,Image Enhance unchecked, and zoom, disable scaling if image size changes by only 25 lines or less. Scaling Algorithims are Chroma up- Jinc, Image Down-Jinc,Image doubling-off,image upscale-jinc with active anti ringing on all 3. Nothing in upscale refinement, Rendering has nothing checked off under general and the que for cpu is 16 and gpu is 8, Smooth Motion on, althought i do not know what to be looking for, just that in some movies when the scene is in motion from side to side i see visually its not very smooth, like a little judder or something, Dithering is Ordered and nothing checked in trade quality for preformance.

In Mpc Under lav Decored, top corner is all auto with the box checked 0-255 and ordered dithering, Dxva2 copyback with all boxes checked and software deinterlacing disabled.

Does anything stand out here that i would or should want to change? i would prefer to stay under 70% Gpu usage. Its been along time since i posted and i forgot alot of stuff :(. As i said most the stuff i watch is 1080 or 720 rip with the odd older show @ 480p. or worse. i find it dark watching game of thrones, unless i turn up brightness in mpc, which is kinda annoying. But i gave up trying to find a better set up for the monitors settings. Help me obi won kenobi, your my only hope <3

Sorry to toxic your thread, but if anyone can give me some input base on info provided or can inbox me id greatly appreciate it. if i find movie nirvana or epic results id glady paypal a few bucks for your time. TY!

[Asmodian]

Updated for madVR v0.90.24

[SweetLow]

To Asmodian
As minimum one hidden option exists which not mentioned in your reference:
KeepLastFrameOnStop

[oddball]

I am getting noticeable frame skipping on VFR sources. I can see the numbers of frames repeated/dropped but every now and then I see a visible skip. I tried resetting to defaults and it does not help. I can also not play any video other than in DX11 mode. If I leave it unticked MPC-HC hangs. MadVR settings continue to be accessible. But I have to kill MPC-HC in Win10 Task Manager.

I am using AMD's latest drivers but this has continued through from using a AMD R90 290 to changing the GPU to a RX 480.

I have also tried older versions of MadVR and it still hangs with DX11 unticked. This only occurs over HDMI to a either a Denon AVR or directly to a Panasonic plasma HDTV.

Because MadVR hangs and does not crash I don't know how to get any crash info. Is it MadVR or MPC-HC? If MPC-HC where do I get the crash info? I have also tried older non-nighlty buiilds of MPC-HC.

Also I have had issues with delayed playback enabled with DX11 ticked and switching between fullscreen on the HDTV and windowed on the main monitor.

Please advise on how I can diagnose these issues and post a crash report.

I don't want to have to wipe Win10 and start over but this has been going on for many weeks now and I still don't know how to fix this.

Any help appreciated on what I should do to find crash info and diagnose this pain in the butt problem.

EDIT: I tried it in MPC-BE out of curiosity and with DX11 unticked and sending it stright to fullscreen on the HDTV I get the MPC-BE logo window (no video) and the sound continues on. I also see 'madVR reports -resetting direct3d devices failed (8007000e)' and '-creating direct3d devce failed (8007000e)'. I am at a loss right now.

EDIT2: If I stop it going fullscreen on the HDTV and allow it to play on the monitor first it plays,pauses, ff/rw etc. But if I force it to the HDTV the playback stops and I can do nothing even though the interface still allows me to pause, play etc. But the image and sound remain static on what was previously there.

[Asmodian]

To Asmodian
As minimum one hidden option exists which not mentioned in your reference:
KeepLastFrameOnStop

Thanks! I will add it when I get back home and off mobile.

I am using AMD's latest drivers but this has continued through from using a AMD R90 290 to changing the GPU to a RX 480.

I believe many users are reporting issues with AMD's newest drivers. I think 13.2 is the still the optimal version according to reports but that version doesn't support the RX 480 so I don't know what to suggest. Maybe try a few of the older versions that do support the RX 480. :(

That said you can also try smaller and larger queues, especially the present queues. Try changing the "use a separate device for presentation" and the "present a frame for every v-sync" options as well. Make one change at a time.

Sorry, I do not have any AMD cards myself so I cannot offer better advice.

[oddball]

Thanks! I will add it when I get back home and off mobile.



I believe many users are reporting issues with AMD's newest drivers. I think 13.2 is the still the optimal version according to reports but that version doesn't support the RX 480 so I don't know what to suggest. Maybe try a few of the older versions that do support the RX 480. :(

That said you can also try smaller and larger queues, especially the present queues. Try changing the "use a separate device for presentation" and the "present a frame for every v-sync" options as well. Make one change at a time.

Sorry, I do not have any AMD cards myself so I cannot offer better advice.

Yes I can get it to playback using DX11 just not without it being ticked. Anyhow I have discovered something interesting. When setting the HDTV to 60Hz in Windows and setting MadVR to not switch to any display refreshes (1080p23 etc blanked out) and just having smooth motion ticked I get smooth VFR playback. So something is up with MadVR and refresh rate switching I believe. I tend to run the HDTV at 23Hz and MadVR to just auto switch out at that rate. Let me experiment some more.

EDIT: Ooh! MadVR just made a crash dump.

https://drdump.com/UploadedReport.aspx?DumpID=10749439&SecondVisit=1

[Asmodian]

Yes I can get it to playback using DX11 just not without it being ticked. Anyhow I have discovered something interesting. When setting the HDTV to 60Hz in Windows and setting MadVR to not switch to any display refreshes (1080p23 etc blanked out) and just having smooth motion ticked I get smooth VFR playback. So something is up with MadVR and refresh rate switching I believe. I tend to run the HDTV at 23Hz and MadVR to just auto switch out at that rate. Let me experiment some more.

Really a lot of TVs have bad 24 Hz modes, maybe it is the TV not processing 24Hz correctly with the somewhat odd patterns of VFR video. 60 Hz with smooth motion is a good option IMO, is there a reason you do not like it?

I do not think it is it is likely to be a problem with madVR's refresh rate switching, it works properly for too many people.

Edit: I am highly suspicious that the crashes with anything but DX11 is due to AMD's driver, both AMD and Nvidia have had driver issues exposed by madVR in the past and there have been a lot of reports of issues with the latest Crimson drivers.

Edit2: Are you using Software decoding LAV? If not, try using it.

[oddball]

Really a lot of TVs have bad 24 Hz modes, maybe it is the TV not processing 24Hz correctly with the somewhat odd patterns of VFR video. 60 Hz with smooth motion is a good option IMO, is there a reason you do not like it?

I do not think it is it is likely to be a problem with madVR's refresh rate switching, it works properly for too many people.

Edit: I am highly suspicious that the crashes with anything but DX11 is due to AMD's driver, both AMD and Nvidia have had driver issues exposed by madVR in the past and there have been a lot of reports of issues with the latest Crimson drivers.

Edit2: Are you using Software decoding LAV? If not, try using it.

I always use LAV as it is inbuilt into the latest MPC-HC.

I had already tested this with the default Win10 provided drivers with the same results. The only way to be sure would be to reinstall Win10 from scratch. Not something I would willingly do lightly.

The only way I have got playback to work is by ticking DX11. Exclusive mode seems to work fine 'most' of the time but I have the odd video that gives a MadVR error in the top left corner. Sometimes they playback fine without exclusive mode selected.

What I have found is that unticking *BOTH* 'delay switch to exclusive mode by 3 seconds' and 'present several frames in adance' has helped prevent dropped frames when playing back VFR sources. Also running at 60Hz and selecting Smooth Motion does the same thing (not dropped frames on VFR).

Unticking 'Delay playback until render queue is full' prevents MPC-HC locking up with a blank screen on the HDTV going to fullscreen. If I open it on the monitor instead it plays back no problemo. If I then force it to fullscreen on the HDTV it just locks up MPC-HC.

BTW when I upgrade AMD's drivers I always DDU in safe mode.

[oddball]

I always use LAV as it is inbuilt into the latest MPC-HC.

I had already tested this with the default Win10 provided drivers with the same results. The only way to be sure would be to reinstall Win10 from scratch. Not something I would willingly do lightly.

The only way I have got playback to work is by ticking DX11. Exclusive mode seems to work fine 'most' of the time but I have the odd video that gives a MadVR error in the top left corner. Sometimes they playback fine without exclusive mode selected.

What I have found is that unticking *BOTH* 'delay switch to exclusive mode by 3 seconds' and 'present several frames in adance' has helped prevent dropped frames when playing back VFR sources. Also running at 60Hz and selecting Smooth Motion does the same thing (not dropped frames on VFR).

Unticking 'Delay playback until render queue is full' prevents MPC-HC locking up with a blank screen on the HDTV going to fullscreen. If I open it on the monitor instead it plays back no problemo. If I then force it to fullscreen on the HDTV it just locks up MPC-HC.

BTW when I upgrade AMD's drivers I always DDU in safe mode.

EDIT: MPC-BE does not lockup up when going fullscreen to my HDTV when all the above three options I mentioned are ticked. I tried setting MPC-BE exactly the same as MPC-HC is except MPC-BE does not have LAV built in so I used LAV as external filters. I tried uninstalling MPC-HC completely and reinstalled and as soon as I selected MadVR as the renderer it played once and once only with those 3 options ticked. After that it locks up again going fullscreen on the HDTV at launch. MPC-BE with LAV filters and everything set the same as in MPC-HC works perfectly. I don't know what that tells me really though. I still get dropped frames on VFR so it does not fix that issue.

EDIT2: OK simply by switching to MPC-BE has solved a lot of issues. Not all of them. But most. I can now play with DX11 unticked. I can also enable delay playback and I get a lot less dropped frames on VFR sources. I still have to untick 'present several frames in advance' on the exclusive section though.

[zmaster]

Hello.
Google search not help with questions, so I posted here.
What is the "activate SuperRes filter" in chroma upscaling section? How to use it?
Now I use nnedi32+spline64 (upscaling 720p - 1080p for example), I do not see any difference "activate SuperRes filter" enabled\disabled. This filter works\need only when SuperRes activated in upscaling refinement section? Or what?

[Asmodian]

It does SuperRes to the chroma when upscaling it. To use it check the box. The upscaling refinement option does SuperRes to both the luma and chroma (actually RGB) after the chroma has been upscaled and the video converted to RGB. When used on the chroma only it is a subtle effect, especially when starting from such a sharp upscaling option.

[zmaster]

Explain pls: using SuperRes in both sections (SuperRes filter in chroma upscaling section + SuperRes in upscaling refinement) it make sense? thx in advance.

[Asmodian]

Yes, there are two independent upscaling steps needed, one to get the chroma to match the luma and one to scale the image to the display. SuperRes can be used on both.

Check out the flow chart in the second post, it might help make sense of the steps.

[P.J]

Can you add some screenshot comparisons too?

[Asmodian]

No, sorry. This is not intended as a guide or to promote madVR. I simply want to describe what options are available and what they do.

[e-t172]

Would it be possible to document the smooth motion settings a bit more? I understand what the "always" mode means, but I'm confused about what "only if there would be motion judder without it" means (what's the criteria, exactly? would it match 30p@60Hz? 24p@60Hz? 23.976p@60Hz? I have no idea), and I'm also confused about what "... or if the display refresh rate is an exact multiple of the movie frame rate" means (what's the meaning of the "... or"? And how is that different from "always"?). Can someone please explain? Up until know I've only used the "always" setting solely because I had no idea what the alternatives meant.

[Asmodian]

Would it be possible to document the smooth motion settings a bit more? I understand what the "always" mode means, but I'm confused about what "only if there would be motion judder without it" means (what's the criteria, exactly? would it match 30p@60Hz? 24p@60Hz? 23.976p@60Hz? I have no idea), and I'm also confused about what "... or if the display refresh rate is an exact multiple of the movie frame rate" means (what's the meaning of the "... or"? And how is that different from "always"?). Can someone please explain?

Sure, but I sadly don't have any data on what the criteria is, exactly.

"only if there would be motion judder without it" will activate for 23.976, 24, or 25 fps on a 60Hz display but not for 29.976 on a 60 Hz display or 23.976 fps on a 143.99 Hz display. So it only activates when there would be large motion judders, something like double digit percentages for frame time variance.

"... or if the display refresh rate is an exact multiple of the movie frame rate", the "..." means it is an extension of the previous phrase. It would make just as much sense, or even more, if the "... or" was removed along with the "..." from the end of "only if there would be motion judder without it...". In practice this appears to be synonymous with "always" but if we ever got a perfect video clock this may change.

Did this tell you anything? I think that is all I know. :o

[huhn]

it is very obvious to me how it works. if you understand what judder is.

"... or if the display refresh rate is an exact multiple of the movie frame rate", the "..." means it is an extension of the previous phrase. It would make just as much sense, or even more, if the "... or" was removed along with the "..." from the end of "only if there would be motion judder without it...". In practice this appears to be synonymous with "always" but if we ever got a perfect video clock this may change.

it will not trigger with a 23p source at 23 hz always is even used there.

[Asmodian]

it will not trigger with a 23p source at 23 hz always is even used there.

Ah, you are correct. Even with my fairly inaccurate 23.9701Hz. Does that mean it doesn't trigger only when fps = refresh rate? I know smooth motion will still activate for 23.976 fps video on a well tuned 119.88Hz. :p

[huhn]

i don't think madVR looks the inaccurate refreshrate to enable SM.

if SM is used this is fixed too.

"... or if the display refresh rate is an exact multiple of the movie frame rate"

SM is not used with this option if the refresh rate is very close to the source.

23p source at 24 HZ does not really have a judder so the always option is needed here to get SM (don't do this...).

I know smooth motion will still activate for 23.976 fps video on a well tuned 119.88Hz.
make sense with:
"... or if the display refresh rate is an exact multiple of the movie frame rate"

[Asmodian]

make sense with:

Shouldn't SM deactivate with a 23.976 source and a 119.880 Hz display when using "... or if the display refresh rate is an exact multiple of the movie frame rate"? 119.880 is an exact multiple (5) of 23.976.

[huhn]

no clearly not.

"enable smooth motion frame rate conversation only if there would be motion judder without it or if the display refresh rate is an exact multiple of the movie frame rate."

the only sightly misleading thing is "exact" because it doesn't have to be exact.

that why this option is there so it will trigger with refresh rates that are a multiply of the source or very very close to it. for a 23p source 120 hz is close enough to trigger this option.

my english is pretty bad but this is totally clear to me.

[Asmodian]

no clearly not.

"enable smooth motion frame rate conversation only if there would be motion judder without it or if the display refresh rate is an exact multiple of the movie frame rate."

the only sightly misleading thing is "exact" because it doesn't have to be exact.

that why this option is there so it will trigger with refresh rates that are a multiply of the source or very very close to it. for a 23p source 120 hz is close enough to trigger this option.

my english is pretty bad but this is totally clear to me.

You are right about the english, I think I have always added a "not" in my head when reading that line. :o

So this option is basically "always, unless the refresh rate equals the source frame rate"? I think the "exact" threw me off.

However, why does it work this way? Is there a reason to want smooth motion to trigger when the refresh rate is an exact multiple of the source? Is this for slightly off refresh rates and because smooth motion blurs too much when used at source frame rate?

[huhn]

So this option is basically "always, unless the refresh rate equals the source frame rate"? I think the "exact" threw me off.

pretty much.

i guess it is there to remove the 1 frame drop/repeat every "what ever".

[Shiandow]

Would almost make more sense to just define some acceptable frequency of dropped / repeated frames, say once every hour / day / year.

[huhn]

but when are you going to calculate that?

BTW i'm using this option. at 60 HZ SM is fine for me anyway.