dcpomatic/test/bv20_test.cc, branch processor DCP-o-matic DCP tools https://git.carlh.net/cgit/dcpomatic/atom?h=processor 2025-03-27T00:43:05Z Bump libdcp for Bv2.0 fixes (#2988). 2025-03-27T00:43:05Z Carl Hetherington cth@carlh.net 2025-03-27T00:43:05Z urn:sha1:059f68ed9d6d74fc6dd28e034db8a4f743c7a76c Rename new_test_film2 -> new_test_film. 2024-05-22T08:33:45Z Carl Hetherington cth@carlh.net 2024-05-20T14:55:57Z urn:sha1:c95ba3eb99c5e4d6dca90cee7e5bb9077b6ed02c Bump libdcp for new asdcplib version. 2024-03-22T14:49:58Z Carl Hetherington cth@carlh.net 2024-03-20T22:34:22Z urn:sha1:32b5af27f00f80054ab0f502ebd7b8a3fa0d4061 Add option to limit DCP output to the "Bv2.0 profile" (#2470). 2023-03-03T00:49:55Z Carl Hetherington cth@carlh.net 2023-03-01T00:26:49Z urn:sha1:34b2b0fe412332505e3d543358c9741bd068602d 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.