2016-05-18, 20:31
the clock deviation is the difference between the video clock and the reference clock. which is usually the audio clock.
you are trying to get the clock deviation as close to zero as possible that all the "magic".
you are doing this with try and error.
if the video clock is to slow you are making it faster if it is to fast you make it slower.
and never forget using a custom resolution is kind of the same as overclocking you are running hardware outside of it's specs.
nothing should go wrong with small changes but this doesn't mean this is bulletproof. bigger changes can make huge problems!
people shouldn't be encouraged to blindly do this!
not sure if someone told you guys this before but you can speed up the clock deviation calculation speed by changing the audio volume rapidly. easily done using the mouse reel in mpc-hc.
and yet again aiming blindly at 24000/1001 (23.976) is a waste of time.
you are trying to get the clock deviation as close to zero as possible that all the "magic".
you are doing this with try and error.
if the video clock is to slow you are making it faster if it is to fast you make it slower.
and never forget using a custom resolution is kind of the same as overclocking you are running hardware outside of it's specs.
nothing should go wrong with small changes but this doesn't mean this is bulletproof. bigger changes can make huge problems!
people shouldn't be encouraged to blindly do this!
not sure if someone told you guys this before but you can speed up the clock deviation calculation speed by changing the audio volume rapidly. easily done using the mouse reel in mpc-hc.
and yet again aiming blindly at 24000/1001 (23.976) is a waste of time.
