Re: [DCP-o-matic] Force re-encoding of DCP

Carl Thanks for implementing this. If it's possible to backport this to 2.12.x, that'd be great. I'll use the test version for this DCP, but it's something that would have been useful on a few other DCPs recently so it'd be great to get it in the permanent pipeline when that's possible.

By the way, I saw the changelog for latest test version and there's a ton of brilliant features in there. The keyboard shortcuts for frame forward and backwards are particularly appealing (it's the simple things!). When do you think this is all likely to make it into 2.12.x? Please don't take that as me trying to push you if it's not stable yet - the rock-solid stability of DCP-o-matic is a massive asset - just asking...

Jim On 07/11/2018 23:28, Carl Hetherington via DCPomatic wrote: stubborn Carl can be at times ;-) damage - e.g. cropping a single line. Another less obtrusive option could be to burn-in an invisible char, e.g. small dot. I guess you can set it's transparency to 100% and still force reencoding. The timing for that SRT burn-in has to extend from the first to the last frame so that all frames have to be reencoded. <dcpomatic(a)carlh.net>et>: illegally high bitrate, and would like to re-process it to re-encode the frames at a lower bitrate. DCP-o-matic is clever enough just to repackage the original J2K frames without re-encoding. But is there any way to force it to do a re-encode? sequence and then re-import that for example? _______________________________________________ DCPomatic mailing list DCPomatic(a)carlh.net http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic