Stream timebase should be set using avpriv_set_pts_info, otherwise
avctx->pkt_timebase is not correct.
This should fix ticket #4766.
Patch is only compile tested.
Signed-off-by: Marton Balint <cus@passwd.hu>
Reviewed-by: Stephen Hutchinson <qyot27@gmail.com>
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
As suggested, posting the combined patch with the fate changes.
The patch sets the default style in ASS from the default style
information present in the movtext header.
Signed-off-by: Niklesh <niklesh.lalwani@iitb.ac.in>
The double meaning of the faststart flag (moving a moov atom
to the start of files, making them streamable, for non-fragmented
files, vs inserting a global sidx index at the start of files
for fragmented files) is confusing - see 40ed1cbf1 for
explanation of its origins.
Since the second meaning of the flag hasn't been part of any
libav release yet, just rename it to get rid of the confusion
without any extra deprecation (which wouldn't get rid of the
potential confusion, of users adding -movflags faststart
even for fragmented files, where it isn't needed for making
them "streamable").
This gets back the old behaviour, where -movflags faststart
doesn't have any effect for fragmented files.
Signed-off-by: Martin Storsjö <martin@martin.st>
* commit 'f5e486f6f8c242bb2be01ad3ae952b5733ba1113':
x86inc: Fix instantiation of YMM registers
See e93d3a22cb
Merged-by: Hendrik Leppkes <h.leppkes@gmail.com>
* commit 'b114d28a18050b5ebd22fc067332e5487243889c':
x86inc: warn when instructions incompatible with current cpuflags are used
See a1684311b3
Merged-by: Hendrik Leppkes <h.leppkes@gmail.com>
* commit '9f1245eb9620a70feaa00ba745c6c7a56a839556':
x86inc: Support arbitrary stack alignments
See 826790f596
Merged-by: Hendrik Leppkes <h.leppkes@gmail.com>
* commit '8c75ba55a4367c854b577c849ea2195bd78c4c81':
x86inc: warn if XOP integer FMA instruction emulation is impossible
See 8db0f71b49
Merged-by: Hendrik Leppkes <h.leppkes@gmail.com>
* commit '8f4a06faf45c1cbcabec610f4b47824171379934':
checkasm: Remove unnecessary include
See 5e8e121fcc
Merged-by: Hendrik Leppkes <h.leppkes@gmail.com>
A parser should never be called with a mismatching codec
Found-by: Ganesh Ajjanagadde <gajjanag@mit.edu>
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
FATE is non-interactive; it should not listen to user commands
Signed-off-by: Ganesh Ajjanagadde <gajjanagadde@gmail.com>
This should fix leaving the terminal in a messed up state with
zsh in case of crashes during fate
Signed-off-by: Michael Niedermayer <michael@niedermayer.cc>
Don't try to do a blocking wait for MMAL output if we haven't even sent
a single real packet, but only flush packets. Obviously we can't expect
to get anything back.
Additionally, don't send a flush packet to MMAL in the same case. It
appears the MMAL decoder will sometimes hang in mmal_vc_port_disable()
(called from ffmmal_close_decoder()), waiting for a reply from the GPU
which never arrives. Either MMAL disallows sending flush packets without
preceding real data, or it's a MMAL bug.
I can't come up with a nice way to handle this. It's hard to keep the
lock-stepped input/output in this case. You can't predict whether the
MMAL decoder will output a picture (because it's asynchronous), so
you have to assume in general that any packet could produce 0 or 1
frames. You can't continue to write input packets to the decoder,
because then you might get too many output frames, which you can't
get rid of because the lavc decoding API does not allow the decoder
to return an output frame without consuming an input frame (except
when flushing).
The ideal fix is a M:N decoding API (preferably asynchronous), which
would make this code potentially much cleaner. For now, this hack
will do.
