dcpomatic/src, branch v2.18.22 DCP-o-matic DCP tools https://git.carlh.net/cgit/dcpomatic/atom?h=v2.18.22 2025-08-13T21:55:36Z pot/merge. 2025-08-13T21:55:36Z Carl Hetherington cth@carlh.net 2025-08-13T21:55:34Z urn:sha1:762ebd5841286e82e839554f1e9623ef89006e7b Supporters update. 2025-08-13T21:55:02Z Carl Hetherington cth@carlh.net 2025-08-13T21:55:02Z urn:sha1:71057e641998a287e96e65c132be375a981731eb Rename None -> DCI X'Y'Z' in menu. 2025-08-13T21:13:59Z Carl Hetherington cth@carlh.net 2025-08-13T21:13:59Z urn:sha1:d889a9755d3f0a6d1ec54896f976578672df1d9b Also suggested in #3066, it made no sense to say the source colourspace was "None" (a confusion between 'source colourspace' and 'what conversion should be applied'). Rename colour -> source colourspace. 2025-08-13T21:13:11Z Carl Hetherington cth@carlh.net 2025-08-13T21:13:11Z urn:sha1:a172e67b9684100e063254f4cd0301155ec16edc It's longer but doesn't look too bad (on Linux at least) and helps clarify things. Suggested as part of #3066. New/improved pixel format decision when converting to XYZ. 2025-08-12T15:16:07Z Carl Hetherington cth@carlh.net 2025-07-21T22:48:42Z urn:sha1:98a8023dd774fd82c144a68039e0ea3131fb9142 For a long time we would keep XYZ12LE, if that's what we have, otherwise ask FFmpeg to switch to RGB48LE. Then in 1d5c211dadb9a9dc2318adce86ca9c31b367cabe I tried to fix the case of an XYZ source mis-tagged as YUV. I changed things so that with no colour conversion we'd always ask FFmpeg to convert to XYZ. This meant that RGB sources with no colour conversion would get treatment by FFmpeg due to the RGB -> XYZ switch. Here we're going back to the more-or-less the "long time" behaviour when there is a conversion (keep XYZ12LE but otherwise convert to RGB48). When there's no conversion, keep RGB (to avoid the FFmpeg conversion from RGB -> XYZ) but convert everything else to XYZ. Replace AVPixelFormat parameter to PlayerVideo::image with a functor. 2025-08-12T15:16:07Z Carl Hetherington cth@carlh.net 2025-07-21T22:18:32Z urn:sha1:9b73c143ce568bd8694e3a50f2fefc1ee3a03515 This was removed in df9b4676aba8b941f124b174393988cad21677e1 and surrounding commits, but it turns out we need it after all. Allow finding DKDMs by content title text. 2025-08-12T15:07:39Z Carl Hetherington cth@carlh.net 2025-08-12T15:07:39Z urn:sha1:0114987c5d6040d8fe07a719d7f97b0a5e200458 More detailed KDM CLI help. 2025-08-12T14:21:29Z Carl Hetherington cth@carlh.net 2025-08-12T14:21:29Z urn:sha1:2bcb0fd85d9057c48eaac03f9d5896b8b394d8cb Adjust spacing in KDM CLI tool --help. 2025-08-12T13:11:17Z Carl Hetherington cth@carlh.net 2025-08-12T13:11:17Z urn:sha1:a8d99132613d5e61931ef815e2988f859ba522d3 White space: ffmpeg_image_proxy.{cc,h} 2025-07-21T21:42:00Z Carl Hetherington cth@carlh.net 2025-07-21T21:42:00Z urn:sha1:aeaf8995c5eaff87720b3c7d5bc014183abdddd8