7 Nov
2018
7 Nov
'18
11:28 p.m.
Hi all,
Now now, play nicely ;)
I've added a button which will be in 2.13.68 if you're in a position to
use the test version (even for just this DCP). It's not tremendously
invasive so I could be persuaded to backport to 2.12.x I expect.
Best,
Carl
On Wed, 7 Nov 2018, Carsten Kurz via DCPomatic wrote:
Hi Jim,
I have an open feature request for this on Mantis, but you know how stubborn Carl can be
at times ;-)
Currently I think the only way to force reencoding is to do some minor 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.
- Carsten
...gesendet von unterwegs
Am 07.11.2018 um 18:41 schrieb Jim Dummett via
DCPomatic <dcpomatic(a)carlh.net>et>:
Hi all.
Is there any way to force re-encoding of a DCP? We have a DCP which has an illegally high
bitrate, and would like to re-process it to re-encode the frames at a lower bitrate.
Usually, where you don't alter the image (crop, colour conversion etc) 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?
Or can anyone suggest a workaround? A good way to export to an image sequence and then
re-import that for example?
Many thanks,
Jim
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic
_______________________________________________
DCPomatic mailing list
DCPomatic(a)carlh.net
http://main.carlh.net/cgi-bin/mailman/listinfo/dcpomatic