2018-08-21 12:58 GMT+02:00, Vasiliy Volkov <[email protected]>: > вт, 21 авг. 2018 г. в 12:25, Carl Eugen Hoyos <[email protected]>: > > If you see such a stream, please provide a sample. >> > > Ok, when we encounter such stream again, I'll create ticket at FFmpeg's > trac.
You could simply post on the user mailing list. >> I already told you that libavcodec has known, long-time issues with >> H.264 timestamps, this is no secret. >> I would be surprised if these issues - that are in no way limited to >> frame-rates - >> wouldn't also manifest themselves in wrong information about stream >> properties. > > Hm, I see... Could you please provide some known tickets with these > problems from FFmpeg's trac? > I'd like to read them to find out better approach or workaround for > handling H.264 streams timestamps. I don't have a ticket number atm, just try to remux paff content. (But from your description, your sample may also be an example.) Carl Eugen _______________________________________________ Libav-user mailing list [email protected] http://ffmpeg.org/mailman/listinfo/libav-user
