[Ffmpeg-devel] avformat/mpegts reads too much data for lowbitratestreams
Fri Jun 10 21:41:35 CEST 2005
torsdag 9. juni 2005, 22:59, skrev Michael Niedermayer:
> On Thursday 09 June 2005 22:09, M?ns Rullg?rd wrote:
> > Michael Niedermayer <michaelni at gmx.at> writes:
> > > On Thursday 09 June 2005 18:14, M?ns Rullg?rd wrote:
> > >> Kenneth Aafl?y <kenneth at aafloy.net> writes:
> > >> > Say you have a ts with two services, and the user is currently
> > >> > decoding the first service. If this service stops it's transmission
> > >> > the user (app) either want to exit (since it's the end of the
> > >> > 'stream') or switch to the other service (since it's not the end of
> > >> > the 'file'). With your interface it's impossible (close to) to
> > >> > trigger either change, since there is no notion of 'end of
> > >> > substream'.
> > >>
> > >> Consider it a deficiency in libavformat. Fixing it appears to be
> > >> nontrivial.
> > >
> > > hmm, whats non trivial from the lavf api point of view?
> > > you could add a flag to AVStream or AVPacket to indicate "end of
> > > stream"
> > Are you proposing a special end-of-stream packet? I'm not against the
> > idea as such, but it would change the semantics.
> yes, though iam not saying its a good or bad idea just that it seems
> relatively trivial
Ok, so if I got the gist of it, the patches would be:
- remove sdt scan, as it's not required for proper operation
(all info needed is present in pat/pmt)
- replace pat/pmt scan by constant filters that can detect
- insert method (flag) into AVStream to indicate 'end of stream'
More information about the ffmpeg-devel