Re: [FFmpeg-devel] [PATCH 4/6 v2] avutil/mastering_display_metadata: add a new allocator function that returns a size

2024-03-27 Thread James Almer
On 3/27/2024 9:40 AM, Anton Khirnov wrote: Quoting James Almer (2024-03-27 13:35:35) On 3/27/2024 4:41 AM, Anton Khirnov wrote: Quoting James Almer (2024-03-25 22:13:25) On 3/25/2024 6:02 PM, Andreas Rheinhardt wrote: James Almer: I don't mind a function like that being added to simplify

Re: [FFmpeg-devel] [PATCH 4/6 v2] avutil/mastering_display_metadata: add a new allocator function that returns a size

2024-03-27 Thread Anton Khirnov
Quoting James Almer (2024-03-27 13:35:35) > On 3/27/2024 4:41 AM, Anton Khirnov wrote: > > Quoting James Almer (2024-03-25 22:13:25) > >> On 3/25/2024 6:02 PM, Andreas Rheinhardt wrote: > >>> James Almer: > I don't mind a function like that being added to simplify future > additions, but

Re: [FFmpeg-devel] [PATCH 4/6 v2] avutil/mastering_display_metadata: add a new allocator function that returns a size

2024-03-27 Thread James Almer
On 3/27/2024 4:41 AM, Anton Khirnov wrote: Quoting James Almer (2024-03-25 22:13:25) On 3/25/2024 6:02 PM, Andreas Rheinhardt wrote: James Almer: I don't mind a function like that being added to simplify future additions, but this API is orthogonal to the frame side data one. It's also used

Re: [FFmpeg-devel] [PATCH 4/6 v2] avutil/mastering_display_metadata: add a new allocator function that returns a size

2024-03-27 Thread Anton Khirnov
Quoting James Almer (2024-03-25 22:13:25) > On 3/25/2024 6:02 PM, Andreas Rheinhardt wrote: > > James Almer: > >> I don't mind a function like that being added to simplify future > >> additions, but this API is orthogonal to the frame side data one. It's > >> also used in packets, for example, and

Re: [FFmpeg-devel] [PATCH 4/6 v2] avutil/mastering_display_metadata: add a new allocator function that returns a size

2024-03-25 Thread James Almer
On 3/25/2024 6:02 PM, Andreas Rheinhardt wrote: James Almer: On 3/25/2024 5:40 PM, Andreas Rheinhardt wrote: James Almer: av_mastering_display_metadata_alloc() is not useful in scenarios where you need to know the runtime size of AVMasteringDisplayMetadata. Signed-off-by: James Almer ---  

Re: [FFmpeg-devel] [PATCH 4/6 v2] avutil/mastering_display_metadata: add a new allocator function that returns a size

2024-03-25 Thread Andreas Rheinhardt
James Almer: > On 3/25/2024 5:40 PM, Andreas Rheinhardt wrote: >> James Almer: >>> av_mastering_display_metadata_alloc() is not useful in scenarios >>> where you need to >>> know the runtime size of AVMasteringDisplayMetadata. >>> >>> Signed-off-by: James Almer >>> --- >>>  

Re: [FFmpeg-devel] [PATCH 4/6 v2] avutil/mastering_display_metadata: add a new allocator function that returns a size

2024-03-25 Thread James Almer
On 3/25/2024 5:40 PM, Andreas Rheinhardt wrote: James Almer: av_mastering_display_metadata_alloc() is not useful in scenarios where you need to know the runtime size of AVMasteringDisplayMetadata. Signed-off-by: James Almer --- libavutil/mastering_display_metadata.c | 13 +

Re: [FFmpeg-devel] [PATCH 4/6 v2] avutil/mastering_display_metadata: add a new allocator function that returns a size

2024-03-25 Thread Andreas Rheinhardt
James Almer: > av_mastering_display_metadata_alloc() is not useful in scenarios where you > need to > know the runtime size of AVMasteringDisplayMetadata. > > Signed-off-by: James Almer > --- > libavutil/mastering_display_metadata.c | 13 + > libavutil/mastering_display_metadata.h

[FFmpeg-devel] [PATCH 4/6 v2] avutil/mastering_display_metadata: add a new allocator function that returns a size

2024-03-25 Thread James Almer
av_mastering_display_metadata_alloc() is not useful in scenarios where you need to know the runtime size of AVMasteringDisplayMetadata. Signed-off-by: James Almer --- libavutil/mastering_display_metadata.c | 13 + libavutil/mastering_display_metadata.h | 9 + 2 files