Quote:
|
due to the clock deviation so your display will never exactly be 23.976.
|
There is only an indirect relationship between madVR's reported Refresh Rate and madVR's Clock Deviation calculation, so thinking in those terms will only cause confusion. madVR's refresh Rate calculation is accurate relative to other measurements from your computer, and that's all that matters for our purposes.
On the other hand, Clock Deviation has a direct relationship to your a/v
Playback Rate which causes it to never be exactly 23.9760 FPS. Depending on your Clock Deviation, your actual Playback Rate would likely fall into the range of 23.9760 +/- 0.0005 FPS. Microsoft designed DirectShow in such a way that makes this skew completely invisible and transparent to the end-user. This can be confusing, since it results in all DirectShow playback FPS statistics being technically incorrect at face value.
If you match the Refresh Rate madVR reports to a multiple of your actual playback rate (calculated from Clock Deviation), you should never experience dropped frames assuming no madVR processing slowdowns or GPU driver glitches, but locking in such a high precision Refresh Rate is not always possible. See my post
here for how to calculate optimal Refresh Rate from madVR's Clock Deviation statistic.
Reclock works from the opposite direction, by adjusting your a/v Playback Rate to match your Refresh Rate.