Probably makes sense to default to checking KDM validity ranges
authorCarl Hetherington <cth@carlh.net>
Tue, 18 Sep 2018 20:01:00 +0000 (21:01 +0100)
committerCarl Hetherington <cth@carlh.net>
Tue, 18 Sep 2018 20:01:00 +0000 (21:01 +0100)
so that testing KDMs is more like real life.

src/lib/config.cc

index b28f8b957960b3a5a885829a6e0a49e7cb588742..702da44d084d72bec99c3aba9c715340d7c052a3 100644 (file)
@@ -164,7 +164,7 @@ Config::set_defaults ()
        _gdc_password = optional<string>();
        _interface_complexity = INTERFACE_SIMPLE;
        _player_mode = PLAYER_MODE_WINDOW;
-       _respect_kdm_validity_periods = false;
+       _respect_kdm_validity_periods = true;
        _player_log_file = boost::none;
 
        _allowed_dcp_frame_rates.clear ();
@@ -493,7 +493,7 @@ try
                _player_mode = PLAYER_MODE_DUAL;
        }
 
-       _respect_kdm_validity_periods = f.optional_bool_child("RespectKDMValidityPeriods").get_value_or(false);
+       _respect_kdm_validity_periods = f.optional_bool_child("RespectKDMValidityPeriods").get_value_or(true);
        _player_log_file = f.optional_string_child("PlayerLogFile");
 
        /* Replace any cinemas from config.xml with those from the configured file */