- 27 Oct, 2015 1 commit
-
-
Timothy Gu authored
-
- 30 Sep, 2014 1 commit
-
-
Clément Bœsch authored
-
- 14 Apr, 2013 1 commit
-
-
Clément Bœsch authored
Since 4f112a8e, this is not necessary anymore. Also, it allows to actually disable the flushing.
-
- 20 Dec, 2012 1 commit
-
-
Clément Bœsch authored
-
- 10 Nov, 2012 1 commit
-
-
Clément Bœsch authored
This way we don't abort in the middle of remuxing, just warn about an event ignored. The index increment is moved to make sure the output numbers still make sense.
-
- 28 Oct, 2012 1 commit
-
-
Clément Bœsch authored
There is not really a problem in having two events at the same time. Even if it's not perfectly correct, it helps remuxing more files (typically our FATE sample).
-
- 26 Oct, 2012 1 commit
-
-
Clément Bœsch authored
This is useful when you want to remux events with zero (or too small) durations.
-
- 24 Oct, 2012 2 commits
-
-
Clément Bœsch authored
We don't have a text encoder yet, so this commit makes automatic encoding working with srt output.
-
Clément Bœsch authored
-
- 01 Sep, 2012 1 commit
-
-
Philip Langdale authored
After much discussion and back-and-forth, we reached the conclusion that matroska uses convergence_duration for subtitle duration because a 32bit value isn't large enough to store the duration if sub-micro-second timebases are used. Matroska may not be the only one that supports these timebases, but it's certainly the only one that ffmpeg attempts to support in this way. The long term solution that we seemed to reach was that if we encounter a matroska file with a sub-micro-second timebase, we should internally scale it up to at least micro-second, and then duration can be used normally. This suggests that on the encode side, we should not allow generation of files with sub-micro-second timebases, but that's a separate issue. That being a non-trivial change, and the subtitle interoperability breakage being very real, I'm re-submitting this small change for consideration. In this diff, we make sure that duration is populated by the matroska demuxer, and that convergence_duration is respected in matroskaenc and srtenc, but that duration is used otherwise. This ends up being a strict improvement - pipelines that use convergence duration are unchanged, and ones that are currently broken due to the duration mismatch will start working - except for the ones with the extreme timebases, but those were already broken. Signed-off-by:
Philip Langdale <philipl@overt.org>
-
- 16 Aug, 2012 1 commit
-
-
Philip Langdale authored
Unsurprisingly, if a timing-less subrip decoder is desireable, an encoder is as well. With this in place, we can move on to remove the use of the old encoder/decoder with embedded timing and move all timing handling the (de)muxer where they belong. Signed-off-by:
Philip Langdale <philipl@overt.org>
-
- 21 Jun, 2012 1 commit
-
-
Nicolas George authored
This muxer supports CODEC_ID_SRT with the timestamps in the packet data and CODEC_ID_TEXT with the timestamps in the packet fields. Makes -scodec copy work from Matroska.
-