> > Exactly, you need to use the format string for uint64_t, PRIu64 from > memory; check in the code base and standard. >
Thanks for the pointer, didn't knew this. > Then I think the timestamp of the frame would be a better choice. IIUC, > the field you print depends on the way ffmpeg processes the frames, > including seek: it is not robust. > Would you advice using the AVFrame::best_effort_timestamp field ? One problem I see is that it doesn't seems to be aware of trim command (eg. -ss flag). _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
