diff options
| author | Carl Hetherington <cth@carlh.net> | 2023-03-01 01:26:49 +0100 |
|---|---|---|
| committer | Carl Hetherington <cth@carlh.net> | 2023-03-03 01:49:55 +0100 |
| commit | 34b2b0fe412332505e3d543358c9741bd068602d (patch) | |
| tree | f83f2dad55f17a9b03c6fb105995dd045e8a5d4c /src/lib/writer.cc | |
| parent | 03d6d6a8e7bcb7b2bfa920841ac7421f08dcc9b6 (diff) | |
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.
Diffstat (limited to 'src/lib/writer.cc')
| -rw-r--r-- | src/lib/writer.cc | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/lib/writer.cc b/src/lib/writer.cc index a36944723..1c8f1a0cd 100644 --- a/src/lib/writer.cc +++ b/src/lib/writer.cc @@ -691,7 +691,7 @@ Writer::finish (boost::filesystem::path output_dcp) dcp.set_creator(creator); dcp.set_annotation_text(film()->dcp_name()); - dcp.write_xml (signer, Config::instance()->dcp_metadata_filename_format()); + dcp.write_xml(signer, !film()->limit_to_smpte_bv20(), Config::instance()->dcp_metadata_filename_format()); LOG_GENERAL ( N_("Wrote %1 FULL, %2 FAKE, %3 REPEAT, %4 pushed to disk"), _full_written, _fake_written, _repeat_written, _pushed_to_disk |