| Age | Commit message (Collapse) | Author |
|
Otherwise if we seek to the frame just before the end of the DCP
we'll call emit_video_until() with _next_video unset, causing that
method to emit video for the whole film.
The point of this emit_video_until() call is only to pad a space
between the end of the video content and the end of the film.
|
|
|
|
|
|
|
|
|
|
|
|
the film is currently using.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
commands.
|
|
|
|
|
|
|
|
|
|
This reverts a change made in
8ca6fd6d97e6d42492afddb655fa85130946853c
"Fix doubled subtitles if subtitle stop times are specified."
That change breaks the case where a subtitle _does_ have a stop time,
but it's wrong (30s from the start time) and we want the next subtitle
to clear the previous one.
I can't now see how reverting this could cause doubled subtitles,
so maybe that problem wlil come back. At least now there's a test
for #2792.
|
|
|
|
|
|
|
|
Setting the optional to 0 here means we never even looked at the
packet side data. This seems to be more of a problem with the
v2.17.x branch for some reason.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|