On 7/13/19, Francesco Pretto <cez...@gmail.com> wrote: > On Sat, 13 Jul 2019 at 20:21, Paul B Mahol <one...@gmail.com> wrote: >> What gives you reason this is supported? None of containers mentioned can >> support it even theoretically. >> >> > > I didn't have knowledge enough to speculate about support of this > feature on specific formats but I couldn't either find hints > suggesting very limited support so I just tried. As said nut[1] > format, which I also mentioned, seems to directly support it but I was > not able to make it work by setting AVFrame.metadata and pushing the > frame: when decoding the same field is always NULL. Without an example > I can't understand if I am doing something wrong or the support for > per-frame metadata is broken in nut. Any help is appreciated. >
NUT does not support that. What convinced you it does support it? The only thing that theoretically supports frame metadata is tiff and anything that uses exif. But note that frame metadata is implemented for decoding and for encoding it is simply not there. > Cheers, > Francesco > > [1] https://ffmpeg.org/~michael/nut.txt > _______________________________________________ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-user > > To unsubscribe, visit link above, or email > ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe". _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
