On Thu, Jan 09, 2020 at 11:32:03PM +0200, Martin Storsjö wrote:
> On Wed, 8 Jan 2020, Martin Storsjö wrote:
>
> >On Fri, 20 Dec 2019, Michael Niedermayer wrote:
> >
> >>On Tue, Dec 17, 2019 at 03:15:09PM +0200, Martin Storsjö wrote:
> >>>Keep all the existing data fields as they are (there's lots
On Wed, 8 Jan 2020, Martin Storsjö wrote:
On Fri, 20 Dec 2019, Michael Niedermayer wrote:
On Tue, Dec 17, 2019 at 03:15:09PM +0200, Martin Storsjö wrote:
Keep all the existing data fields as they are (there's lots and
lots of nontrivial calculation and heuristics based on them in
their curren
On Fri, 20 Dec 2019, Michael Niedermayer wrote:
On Tue, Dec 17, 2019 at 03:15:09PM +0200, Martin Storsjö wrote:
Keep all the existing data fields as they are (there's lots and
lots of nontrivial calculation and heuristics based on them in
their current form), but derive the duration as the diff
On Tue, Dec 17, 2019 at 03:15:09PM +0200, Martin Storsjö wrote:
> Keep all the existing data fields as they are (there's lots and
> lots of nontrivial calculation and heuristics based on them in
> their current form), but derive the duration as the difference
> between the pts of the first packet t
Keep all the existing data fields as they are (there's lots and
lots of nontrivial calculation and heuristics based on them in
their current form), but derive the duration as the difference
between the pts of the first packet to the maximum pts+duration
(not necessarily the last packet); use this d