Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
18th September 2016, 17:20 | #241 | Link | |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Quote:
"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.
__________________
madVR options explained |
|
18th September 2016, 18:45 | #242 | Link | |
Registered User
Join Date: Oct 2012
Posts: 7,925
|
it is very obvious to me how it works. if you understand what judder is.
Quote:
|
|
18th September 2016, 18:59 | #243 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
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.
__________________
madVR options explained |
19th September 2016, 07:45 | #244 | Link | |||
Registered User
Join Date: Oct 2012
Posts: 7,925
|
i don't think madVR looks the inaccurate refreshrate to enable SM.
if SM is used this is fixed too. Quote:
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...). Quote:
Quote:
|
|||
19th September 2016, 07:55 | #245 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
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.
__________________
madVR options explained |
20th September 2016, 12:33 | #246 | Link |
Registered User
Join Date: Oct 2012
Posts: 7,925
|
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. |
20th September 2016, 16:18 | #247 | Link | |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Quote:
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?
__________________
madVR options explained |
|
20th September 2016, 20:16 | #248 | Link | |
Registered User
Join Date: Oct 2012
Posts: 7,925
|
Quote:
i guess it is there to remove the 1 frame drop/repeat every "what ever". |
|
24th September 2016, 13:20 | #251 | Link | |
Registered User
Join Date: Jul 2015
Posts: 76
|
Quote:
But what about "always"? Now i suppose - in this mode madVR ignore source rate (and simply construct frames with target rate). So we never get dropped/repeated frame. Is this true? |
|
3rd November 2016, 21:36 | #253 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
Updated formatting and some descriptions and added that black bar detection doesn't work with DXVA Native.
__________________
madVR options explained |
4th November 2016, 01:09 | #255 | Link |
Registered User
Join Date: Feb 2002
Location: San Jose, California
Posts: 4,407
|
I will do some testing and update it to be more specific, thanks.
Edit: Which image shifting did you test? I cannot get anything in "automatically detect hard coded black bars" to function when using DXVA2 Native, the always shift the image option doesn't have an effect. Even the hidden option ShowBlackBars doesn't do anything when using DXVA2 Native, it looks like detect hard coded black bars doesn't run at all when using DXVA2 Native.
__________________
madVR options explained Last edited by Asmodian; 4th November 2016 at 04:20. |
4th November 2016, 08:57 | #256 | Link |
Registered User
Join Date: Oct 2012
Posts: 7,925
|
a screen should be better:
https://abload.de/img/imageshiftqcs9f.jpg and yes hard coded bars are not detected. "cleanup image boarders by..." and "if there are big black bars:" works with DXVA native too. i even forgot they exist. maybe something like: most black bar detection features doesn't work with DXVA native(DXVA copy back is recommended) in a proper english is a enough or it is getting complicated in the end. |
4th November 2016, 13:37 | #257 | Link |
Registered User
Join Date: Jul 2015
Posts: 76
|
Of course. Basic logic tell us - this option have nothing related to black bars _detection_ and fully independent of this.
And I don't understand, why madshi put this option in group of "detect hardcoded bars" (and disable image shifting when detect option disabled). May be ask him in main thread? |
4th November 2016, 14:36 | #258 | Link |
Registered User
Join Date: Oct 2012
Posts: 7,925
|
they where added at about the same time and he said before that he wants to rework/rearrange all these option/menus at one point and i'm pretty sure he looks over this in thread from time to time anyway.
but the place is not that far of. remove the words "hard coded" and it makes total sense but a lot of thy other option could be confusion. in the end this is about black bars. madshi had problem with place on settings pages too and the first thing that comes up to my mind was "just add tabs" but in the end i'm pretty sure creating these menus is not fun at all and creating new algorithms feels more rewarding and make more fun. i will come up on these topic when he is actively working on these options. |
4th November 2016, 16:15 | #260 | Link |
Registered User
Join Date: Oct 2012
Posts: 7,925
|
if hard coded black bars are not the problem them the player should do that in my eyes.
i'm pretty sure mpc-hc can only do this manually maybe another play can do that. what stops you from using this current option? off is centered. |
|
|