On 1/27/2021 2:40 PM, Lynne wrote:
Jan 27, 2021, 16:07 by jamr...@gmail.com:
On 1/27/2021 6:16 AM, Anton Khirnov wrote:
Quoting James Almer (2021-01-26 20:11:16)
On 1/26/2021 1:17 PM, Anton Khirnov wrote:
We could start by adding a field to AVPacket that would be set to a
magic value by a
Jan 27, 2021, 16:07 by jamr...@gmail.com:
> On 1/27/2021 6:16 AM, Anton Khirnov wrote:
>
>> Quoting James Almer (2021-01-26 20:11:16)
>>
>>> On 1/26/2021 1:17 PM, Anton Khirnov wrote:
>>>
We could start by adding a field to AVPacket that would be set to a
magic value by av_packet_alloc()
On 1/27/2021 6:16 AM, Anton Khirnov wrote:
Quoting James Almer (2021-01-26 20:11:16)
On 1/26/2021 1:17 PM, Anton Khirnov wrote:
We could start by adding a field to AVPacket that would be set to a
magic value by av_packet_alloc().
Then have e.g. AVCodecContext/AVFormatContext warn when they see
Quoting James Almer (2021-01-26 20:11:16)
> On 1/26/2021 1:17 PM, Anton Khirnov wrote:
> > We could start by adding a field to AVPacket that would be set to a
> > magic value by av_packet_alloc().
> > Then have e.g. AVCodecContext/AVFormatContext warn when they see a
> > packet without this magic v
On 1/26/2021 1:17 PM, Anton Khirnov wrote:
Quoting James Almer (2021-01-26 17:07:28)
On 1/26/2021 1:02 PM, Anton Khirnov wrote:
Quoting Lynne (2021-01-24 18:34:36)
Some devs (JEEB) wanted reception timestamps and original, overflowed
timestamps for MPEG-TS.
I'd be willing to add a reception
Quoting James Almer (2021-01-26 17:07:28)
> On 1/26/2021 1:02 PM, Anton Khirnov wrote:
> > Quoting Lynne (2021-01-24 18:34:36)
>
> Some devs (JEEB) wanted reception timestamps and original, overflowed
> timestamps for MPEG-TS.
> I'd be willing to add a reception timestamp as lo
On 1/26/2021 1:02 PM, Anton Khirnov wrote:
Quoting Lynne (2021-01-24 18:34:36)
Some devs (JEEB) wanted reception timestamps and original, overflowed
timestamps for MPEG-TS.
I'd be willing to add a reception timestamp as long as we add an additional
time_base field
and make it independent of t
Quoting Lynne (2021-01-24 18:34:36)
> >>
> >> Some devs (JEEB) wanted reception timestamps and original, overflowed
> >> timestamps for MPEG-TS.
> >> I'd be willing to add a reception timestamp as long as we add an
> >> additional time_base field
> >> and make it independent of the packet's pts f
Jan 24, 2021, 17:05 by an...@khirnov.net:
> Quoting Lynne (2021-01-23 20:10:46)
>
>> This is an RFC about the upcoming additions to the AVPacket structure
>> (whose size is still part of the ABI, so we need to plan for any changes).
>>
>> The current RFC patch adds 3 fields:
>> - "void *opaque
Quoting Lynne (2021-01-23 20:10:46)
> This is an RFC about the upcoming additions to the AVPacket structure
> (whose size is still part of the ABI, so we need to plan for any changes).
>
> The current RFC patch adds 3 fields:
> - "void *opaque;" for the user to use as they wish, same as AVFram
Jan 23, 2021, 23:12 by c...@passwd.hu:
>
>
> On Sat, 23 Jan 2021, Lynne wrote:
>
>> Jan 23, 2021, 21:42 by c...@passwd.hu:
>>
>>>
>>>
>>> On Sat, 23 Jan 2021, Lynne wrote:
>>>
Jan 23, 2021, 21:04 by c...@passwd.hu:
>
>
> On Sat, 23 Jan 2021, Lynne wrote:
>
>> This is
On Sat, 23 Jan 2021, Lynne wrote:
Jan 23, 2021, 21:42 by c...@passwd.hu:
On Sat, 23 Jan 2021, Lynne wrote:
Jan 23, 2021, 21:04 by c...@passwd.hu:
On Sat, 23 Jan 2021, Lynne wrote:
This is an RFC about the upcoming additions to the AVPacket structure
(whose size is still part of the
Jan 23, 2021, 21:42 by c...@passwd.hu:
>
>
> On Sat, 23 Jan 2021, Lynne wrote:
>
>> Jan 23, 2021, 21:04 by c...@passwd.hu:
>>
>>>
>>>
>>> On Sat, 23 Jan 2021, Lynne wrote:
>>>
This is an RFC about the upcoming additions to the AVPacket structure
(whose size is still part of the ABI, so w
On Sat, 23 Jan 2021, Lynne wrote:
Jan 23, 2021, 21:04 by c...@passwd.hu:
On Sat, 23 Jan 2021, Lynne wrote:
This is an RFC about the upcoming additions to the AVPacket structure
(whose size is still part of the ABI, so we need to plan for any changes).
The current RFC patch adds 3 fields
Jan 23, 2021, 21:04 by c...@passwd.hu:
>
>
> On Sat, 23 Jan 2021, Lynne wrote:
>
>> This is an RFC about the upcoming additions to the AVPacket structure
>> (whose size is still part of the ABI, so we need to plan for any changes).
>>
>> The current RFC patch adds 3 fields:
>> - "void *opaque;
On Sat, 23 Jan 2021, Lynne wrote:
This is an RFC about the upcoming additions to the AVPacket structure
(whose size is still part of the ABI, so we need to plan for any changes).
The current RFC patch adds 3 fields:
- "void *opaque;" for the user to use as they wish, same as AVFrame.opaqu
On 24-01-2021 12:40 am, Lynne wrote:
This is an RFC about the upcoming additions to the AVPacket structure
(whose size is still part of the ABI, so we need to plan for any changes).
The current RFC patch adds 3 fields:
- "void *opaque;" for the user to use as they wish, same as AVFrame.op
17 matches
Mail list logo
