Hi, On Tue, Oct 4, 2011 at 5:52 PM, Luca Barbato <[email protected]> wrote: > On 10/4/11 9:48 PM, Justin Ruggles wrote: >> Do you mean side_data as-in, still use AVDictionary to store the info >> but make metadata one of the types of side_data a decoder can export >> into the AVFrame? > > yes, btw if we plan to use AVDict for anything intensive we might consider > making it a little faster.
I'm a little confused now, side_data is an array and dict is a dict, so now we have both an array and a dict? What else do we intend to store in it? We're using side_data[] in AVPacket because AVDict is too heavy, right? If we're using dict anyway, then using side_data[] is not really useful. (I should probably look at what we're going to store in here, it should based on that be either a dict or a side_data[], not both.) Ronald _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
