Add option to limit DCP output to the "Bv2.0 profile" (#2470).v2.16.45

I'm far from convinced about the point/sense of all these "profiles"
(rather than just implementing or at least tolerating the standard)
but lots of people are having problems with "QC" processes failing
their DCPs with complaints related to MCASubDescriptors.  It seems to
make sense to have an option to turn them off - at least for now,
until either the "QC" situation settles down or any bugs in DCP-o-matic
are found and fixed.

1 files changed, 10 insertions, 0 deletions

diff --git a/src/lib/config.h b/src/lib/config.h
index a816cd89b..91d779b7a 100644
--- a/src/lib/config.h
+++ b/src/lib/config.h
@@ -93,6 +93,7 @@ public:
 		SHOW_EXPERIMENTAL_AUDIO_PROCESSORS,
 		AUDIO_MAPPING,
 		AUTO_CROP_THRESHOLD,
+		ALLOW_SMPTE_BV20,
 		OTHER
 	};
 
@@ -612,6 +613,10 @@ public:
 		return _default_add_file_location;
 	}
 
+	bool allow_smpte_bv20() const {
+		return _allow_smpte_bv20;
+	}
+
 	/* SET (mostly) */
 
 	void set_master_encoding_threads (int n) {
@@ -1185,6 +1190,10 @@ public:
 		maybe_set(_default_add_file_location, location);
 	}
 
+	void set_allow_smpte_bv20(bool allow) {
+		maybe_set(_allow_smpte_bv20, allow, ALLOW_SMPTE_BV20);
+	}
+
 	void changed (Property p = OTHER);
 	boost::signals2::signal<void (Property)> Changed;
 	/** Emitted if read() failed on an existing Config file.  There is nothing
@@ -1422,6 +1431,7 @@ private:
 	boost::optional<int> _main_divider_sash_position;
 	boost::optional<int> _main_content_divider_sash_position;
 	DefaultAddFileLocation _default_add_file_location;
+	bool _allow_smpte_bv20;
 
 	ExportConfig _export;