Ping. Anything more required on this patch?
Brad
___
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 "unsubscrib
James Almer (12021-04-20):
> I recall long ago i tried to make av_frame_new_side_data() replace the
> existing element if it found one, effectively limiting side data to one per
> type and copying the behavior of packet side data, but it was rejected as it
> was argued more than one per type had so
On 4/20/2021 7:10 AM, Nicolas George wrote:
Brad Hards (12021-04-20):
The existing function allows access the first instance of a given
type. Mostly that is OK, but some types can occur multiple times
(e.g. libx264 can write version info, VANC and UMID related data as
user data unregistered SEI.
Brad Hards (12021-04-20):
> The existing function allows access the first instance of a given
> type. Mostly that is OK, but some types can occur multiple times
> (e.g. libx264 can write version info, VANC and UMID related data as
> user data unregistered SEI.
>
> This adds API to access additiona
The existing function allows access the first instance of a given
type. Mostly that is OK, but some types can occur multiple times
(e.g. libx264 can write version info, VANC and UMID related data as
user data unregistered SEI.
This adds API to access additional instances of a given SEI type.
---
