Carl Eugen Hoyos:
> Am Mi., 27. Nov. 2019 um 17:58 Uhr schrieb Andreas Rheinhardt
> :
>
>> I consider this only a slight disadvantage: E.g. the streamhash or the
>> framehash muxers would provide easy ways to examine whether the actual
>> content of the files (besides the UIDs) are different.
>
>
On Wed, Nov 27, 2019 at 05:57:56PM +0100, Andreas Rheinhardt wrote:
> On Wed, Nov 27, 2019 at 4:50 PM Michael Niedermayer
> wrote:
>
> > On Wed, Nov 27, 2019 at 08:25:13AM +0100, Andreas Rheinhardt wrote:
> > > On Mon, Nov 25, 2019 at 2:57 PM Michael Niedermayer
> >
> > > wrote:
[...]
>
> >
> >
Am Mi., 27. Nov. 2019 um 17:58 Uhr schrieb Andreas Rheinhardt
:
> I consider this only a slight disadvantage: E.g. the streamhash or the
> framehash muxers would provide easy ways to examine whether the actual
> content of the files (besides the UIDs) are different.
But that wouldn't show changes
On Wed, Nov 27, 2019 at 4:50 PM Michael Niedermayer
wrote:
> On Wed, Nov 27, 2019 at 08:25:13AM +0100, Andreas Rheinhardt wrote:
> > On Mon, Nov 25, 2019 at 2:57 PM Michael Niedermayer
>
> > wrote:
> >
> > > On Sun, Nov 24, 2019 at 11:05:03PM +0100, Andreas Rheinhardt wrote:
> > > > On Sun, Nov
On Wed, Nov 27, 2019 at 08:25:13AM +0100, Andreas Rheinhardt wrote:
> On Mon, Nov 25, 2019 at 2:57 PM Michael Niedermayer
> wrote:
>
> > On Sun, Nov 24, 2019 at 11:05:03PM +0100, Andreas Rheinhardt wrote:
> > > On Sun, Nov 24, 2019 at 8:28 PM Michael Niedermayer
> >
> > > wrote:
> > >
> > > > On
On Mon, Nov 25, 2019 at 2:57 PM Michael Niedermayer
wrote:
> On Sun, Nov 24, 2019 at 11:05:03PM +0100, Andreas Rheinhardt wrote:
> > On Sun, Nov 24, 2019 at 8:28 PM Michael Niedermayer
>
> > wrote:
> >
> > > On Sun, Nov 24, 2019 at 09:08:00AM +, Andreas Rheinhardt wrote:
> > > > Michael Nied
On Sun, Nov 24, 2019 at 11:05:03PM +0100, Andreas Rheinhardt wrote:
> On Sun, Nov 24, 2019 at 8:28 PM Michael Niedermayer
> wrote:
>
> > On Sun, Nov 24, 2019 at 09:08:00AM +, Andreas Rheinhardt wrote:
> > > Michael Niedermayer:
> > > > On Wed, Nov 06, 2019 at 03:49:02AM +0100, Andreas Rheinha
On Sun, Nov 24, 2019 at 8:28 PM Michael Niedermayer
wrote:
> On Sun, Nov 24, 2019 at 09:08:00AM +, Andreas Rheinhardt wrote:
> > Michael Niedermayer:
> > > On Wed, Nov 06, 2019 at 03:49:02AM +0100, Andreas Rheinhardt wrote:
> > >> Up until now, the TrackUID of a Matroska track which is suppos
On Sun, Nov 24, 2019 at 09:08:00AM +, Andreas Rheinhardt wrote:
> Michael Niedermayer:
> > On Wed, Nov 06, 2019 at 03:49:02AM +0100, Andreas Rheinhardt wrote:
> >> Up until now, the TrackUID of a Matroska track which is supposed to be
> >> random was not random at all: It always coincided with
Michael Niedermayer:
> On Wed, Nov 06, 2019 at 03:49:02AM +0100, Andreas Rheinhardt wrote:
>> Up until now, the TrackUID of a Matroska track which is supposed to be
>> random was not random at all: It always coincided with the TrackNumber
>> which is usually the 1-based index of the corresponding s
On Sun, Nov 24, 2019 at 9:49 AM Michael Niedermayer
wrote:
>
> On Wed, Nov 06, 2019 at 03:49:02AM +0100, Andreas Rheinhardt wrote:
> > Up until now, the TrackUID of a Matroska track which is supposed to be
> > random was not random at all: It always coincided with the TrackNumber
> > which is usua
On Wed, Nov 06, 2019 at 03:49:02AM +0100, Andreas Rheinhardt wrote:
> Up until now, the TrackUID of a Matroska track which is supposed to be
> random was not random at all: It always coincided with the TrackNumber
> which is usually the 1-based index of the corresponding stream in the
> array of AV
Up until now, the TrackUID of a Matroska track which is supposed to be
random was not random at all: It always coincided with the TrackNumber
which is usually the 1-based index of the corresponding stream in the
array of AVStreams. This has been changed: It is now set via an AVLFG
if AVFMT_FLAG_BIT
13 matches
Mail list logo
