Hi Gerald
Approach 2 has the advantage that it is much easier for DVD-o-matic to
generate new DCPs with different trim settings. But, yes, approach 1
means unnecessary encodings. The feature was originally intended only
for small amounts of trimming.
As Carsten suggests, I will make it an option.
Carl
On Fri, 12 Apr 2013, Gérald Maruccia wrote:
Hi,
"1. encode only the frames within the trimmed portion."
For me it should be the only way or that means you'd ingest dozens of
Go into your servers only for some short playback ?
Best regards,
G.
Le 12/04/2013 11:16, Carl Hetherington a écrit :
On Fri, 12 Apr 2013, Carsten Kurz wrote:
Hi Carl,
nice work. Used a few other DCP creating tools before,
was a bit sceptical at first about your 'all-in-one-converter'.
However, great functionality in a single package, and, most important
for me, all
processing/conversion steps for video and audio explained
and documented.
Thanks!
Now, I'm using the most recent version 0.83/64bit
Windows. Seems the Trim frames feature doesn't work. Whatever numbers
I dial in for Start/End, it will always create the full length DCP
from my 1:31:42
source. All dialogs show these 137564 frame count (also
'Properties'). Currently I have Start 1 and End 100, but it's
creeping through the full 90mins of footage.
There's a bit of a complication here. I think there are two
ways of doing the trim:
1. encode only the frames within the trimmed portion.
2. encode all frames and then mark the portion to play in the
associated XML metadata.
(1) would be preferable in most cases, except for the situation
when:
i) you encode a big DCP with a start trim of, say, 48 frames.
ii) you decide that after all you want a start trim of 24 frames.
Now with approach (2) this would just be a rewrite of the
metadata, which is quick. For (1) I see no way of doing it other
than encoding the new frames and then copying the entire remainder of
the MXF from the old to the
new.
In other words, it's a trade off between making it quick to
alter start and end trims (but slower if the trims are large, as
unnecessary encoding will be done) and making it quicker to do big
trims (as the unnecessary
frames will not be encoded).
Maybe it should be an option, or maybe it should just go for
approach (2) in all cases. I'm not sure. Any thoughts?
Regardless of all that, if the DCP you make with the current
version does not *play back* with the trims in place, something else
is going wrong!
The trim parameters do not show up in the log file.
Should they?
They don't, I think; I should add them.
Best regards
Carl
- Carsten
_______________________________________________
DVDomatic mailing list
DVDomatic(a)carlh.net
http://carlh.dnsalias.org/cgi-bin/mailman/listinfo/dvdomatic
_______________________________________________
DVDomatic mailing list
DVDomatic(a)carlh.net
http://carlh.dnsalias.org/cgi-bin/mailman/listinfo/dvdomatic
_______________________________________________
DVDomatic mailing list
DVDomatic(a)carlh.net