A few years ago, this change was made to reclock:
1.8.8.2 - 20/01/2014
* Change: Manual framerate settings override automatic framerate detection
Since this version, the setting "assumed frame rate when not found" does not work anymore. Setting it to 23.976 for instance makes reclock use this as the default framerate for all files regardless of the actual framerate of the specific file. Setting it to unknown makes relock correctly detect different framerate from different files. Setting it to anything else thus overrides any framerate reclock might detect. So now it is only usable if one only use reclock for one specific framerate.
Going back to version prior to 1.8.8.2 makes the issue go away.
I tested on 2 PC’s. Installing different versions prior or after 1.8.8.2 changes the behavior back and forth.
is this intended?
/Jens
http://hometheatersettings.com/ - HTPC SETUP
1.8.8.2 - 20/01/2014
* Change: Manual framerate settings override automatic framerate detection
Since this version, the setting "assumed frame rate when not found" does not work anymore. Setting it to 23.976 for instance makes reclock use this as the default framerate for all files regardless of the actual framerate of the specific file. Setting it to unknown makes relock correctly detect different framerate from different files. Setting it to anything else thus overrides any framerate reclock might detect. So now it is only usable if one only use reclock for one specific framerate.
Going back to version prior to 1.8.8.2 makes the issue go away.
I tested on 2 PC’s. Installing different versions prior or after 1.8.8.2 changes the behavior back and forth.
is this intended?
/Jens
http://hometheatersettings.com/ - HTPC SETUP