2019-02-22 18:28 GMT+01:00, Yukun Guo :
> I still can't understand this. Why does FFmpeg need
> MVs? My guess is calculating MVs is just a
> byproduct of extracting the metadata.
The decoder does not know that it was only called to
provide some information about the stream, not the
actual
Thank you for the very helpful replies!
I was busy experimenting with FFmpeg yesterday but got lost in the
complicated codebase. So far I have found FFmpeg keeps decoding frames
until it has collected enough information. In my particular case, it
is the third condition in this while loop
2019-02-20 10:32 GMT+01:00, Ted Park :
>> The original video seems problematic, so FFmpeg outputs
>> several lines of "co located POCs unavailable" error. The
>> error message is printed in `h264_direct.c/ff_h264_direct_ref_list_init`,
>> which is further called by `h264dec.c/h264_decode_frame`.
> The original video seems problematic, so FFmpeg outputs several lines of
> "co located POCs
> unavailable" error. The error message is printed in
> `h264_direct.c/ff_h264_direct_ref_list_init`,
> which is further called by `h264dec.c/h264_decode_frame`. What confuses me
> is why does the copy
>
On 20-02-2019 11:58 AM, Yukun Guo wrote:
Hi,
I'm trying to transmux an H.264 movie in FLV container into raw H.264 in
Annex.B format:
ffmpeg -i movie.flv -c:v copy -an -bsf:v h264_mp4toannexb movie.264
The original video seems problematic, so FFmpeg outputs several lines of
"co located
On Wed, Feb 20, 2019 at 14:28:12 +0800, Yukun Guo wrote:
> I'm trying to transmux an H.264 movie in FLV container into raw H.264 in
> Annex.B format:
>
> ffmpeg -i movie.flv -c:v copy -an -bsf:v h264_mp4toannexb movie.264
[...]
> which is further called by `h264dec.c/h264_decode_frame`. What
