James Almer (12021-03-29): > The idea for attached_pic afaik was that it's always available and easily > accessible to the user from the start, instead of just the one time the > demuxing process would return it in an av_read_frame() call. > The doxy for AV_DISPOSITION_ATTACHED_PIC even mentions that if you seek the > relevant packet may not be returned at all.
Yes, but was it a GOOD idea? For the convenience of the few applications that actually use the attached pictures, libavformat will use memory in all applications. It does not seem like a good compromise to me. I think a better design would be some kind of: int avformat_get_attached_pic(AVStream *st, AVPacket **packet, unsigned flags); In the short run, it could just access the field, but in the long run it could seek back to load the packet only when required. Since applications need to update their API anyway, it is a good time to decide if we want to change something. Regards, -- Nicolas George
signature.asc
Description: PGP signature
_______________________________________________ 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".
