I just wanted to send a reminder about this patch...
wm4 had some concerns about publishing a metadata update on each timestamp
(which would essentially be on each segment). I updated it to not set the
metadata updated event flag in those cases, although it will still add that
metadata to the
On Fri, 18 May 2018 11:54:52 -0700
Richard Shaffer wrote:
> On Fri, May 18, 2018 at 2:54 AM, wm4 wrote:
>
> > On Thu, 17 May 2018 20:49:42 -0700
> > rshaf...@tunein.com wrote:
> >
> > > From: Richard Shaffer
> > >
> > > The
On Fri, May 18, 2018 at 2:54 AM, wm4 wrote:
> On Thu, 17 May 2018 20:49:42 -0700
> rshaf...@tunein.com wrote:
>
> > From: Richard Shaffer
> >
> > The HLS demuxer will process any ID3 tags at the beginning of a segment
> in
> > order to obtain
On Thu, 17 May 2018 20:49:42 -0700
rshaf...@tunein.com wrote:
> From: Richard Shaffer
>
> The HLS demuxer will process any ID3 tags at the beginning of a segment in
> order to obtain timestamp data. However, when this data was parsed on a second
> or subsequent segment, the
From: Richard Shaffer
The HLS demuxer will process any ID3 tags at the beginning of a segment in
order to obtain timestamp data. However, when this data was parsed on a second
or subsequent segment, the updated metadata would be discarded. This change
preserves the data and