On 04/04/13 07:51, Anton Khirnov wrote: >> +#define AVFMT_TS_NEGATIVE 0x40000 /**< Format allows muxing >> negative timestamps. If not set the timestamp will be shifted in >> av_write_frame and av_interleaved_write_frame so they start from 0. >> */ > > What happened to your love for 80-columns hard limit? =p
Felt lazy and I'd change the formatting for the block later. I'll update as well. > Have you verified that none of the remaining muxers support negative > timestamps? I'll go over them again to be absolutely sure, 2 were missing from the first patch. > Can it happen that even with the offset the timestamp will still be > negative because of rounding here? That would require an extremely coarse timebase, should I check for it and error out in the case? lu _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
