On 3/28/2018 7:47 PM, Nicolas George wrote: > Derek Buitenhuis (2018-03-28): >> Do you have an actual suggest though? > > Maybe not using a badly designed API that requires everything to be > stored in a serialized uint8_t array.
Isn't this the same as saying "don't use the existing side data APIs at all"? Do you expect me to design a whole new side data API first? >> Afaict, this is exactly how the recently >> pushed encryption support works with AVSubsampleEncryptionInfo entries in the >> AVEncryptionInfo struct. is this now not acceptable, even though we pushed >> that a few days ago after months of review? > > It just means that these months of review failed to see that flaw. Let > us hope we will not need to extend AVSubsampleEncryptionInfo. I guess the only consistent thing about FFmpeg APIs is that they are inconsistent. I am still open to a different propose solution. - Derek _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
