[FFmpeg-devel] [PATCH] ffprobe: add -ss option

[Stefano Sabatini]

On date Tuesday 2013-09-17 14:22:17 +0200, Clément Bœsch encoded:
> On Mon, Sep 16, 2013 at 06:44:52PM +0200, Stefano Sabatini wrote:
> > On date Monday 2013-09-16 18:09:38 +0200, Stefano Sabatini encoded:
> > > On date Sunday 2013-09-15 20:15:08 +0200, Stefano Sabatini encoded:
> > [...]
> > > Updated, #N duration specification not yet implemented (I'll probably
> > > do in a further patch). The new syntax is more flexible but the result
> > > seems a bit overkill (+189 lines of code).
> > 
> > Updated with that change. I'll ruminate upon the syntax a few days and
> > push if nobody wants to review or proposes some changes (also
> > documentation review is welcome).
> > -- 
> > FFmpeg = Frenzy and Frenzy Muttering Practical Ecstatic God
> 
> > From fbee237bfbf257a923b573542c5edcff19f3b68b Mon Sep 17 00:00:00 2001
> > From: Stefano Sabatini <stefasab at gmail.com>
> > Date: Mon, 22 Oct 2012 16:01:29 +0200
> > Subject: [PATCH] ffprobe: add read_intervals option
> > 
> > This is also useful to test seeking on an input file.
> > 
> > TODO: add Changelog entry
> > 
> > This also address trac ticket #1437.
> > ---
> >  doc/ffprobe.texi |  53 ++++++++++++++
> >  ffprobe.c        | 212 ++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> >  2 files changed, 263 insertions(+), 2 deletions(-)
> > 
> > diff --git a/doc/ffprobe.texi b/doc/ffprobe.texi
> > index 20f5f4a..f6980a9 100644
> > --- a/doc/ffprobe.texi
> > +++ b/doc/ffprobe.texi
> > @@ -230,6 +230,59 @@ corresponding stream section.
> >  Count the number of packets per stream and report it in the
> >  corresponding stream section.
> >  
> > + at item -read_intervals @var{read_intervals}
> > +
> > +Read only the specified intervals. @var{read_intervals} must be a
> > +sequence of intervals separated by ",".
> > +
> 
> We can't tell from this if ffprobe is going to seek or just ignore out of
> the range.

> Also, is there any accuracy/behaviour differences between
> packets demuxing and frame decoding?

The intervals only regard *packets*, then the decoder will spit frames
as long as they are available. This could mean that no frames are
decoded in some particular case.
-- 
FFmpeg = Freak and Frightening Most Purposeless Extended Gadget