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

[Michael Niedermayer]

On Mon, Sep 16, 2013 at 06:09:38PM +0200, Stefano Sabatini wrote:
> On date Sunday 2013-09-15 20:15:08 +0200, Stefano Sabatini encoded:
> > On date Wednesday 2012-10-24 22:27:27 +0200, Michael Niedermayer encoded:
> > > On Tue, Oct 23, 2012 at 01:41:14AM +0200, Stefano Sabatini wrote:
> > > > On date Monday 2012-10-22 17:09:01 +0200, Michael Niedermayer encoded:
> > > > > On Mon, Oct 22, 2012 at 04:02:16PM +0200, Stefano Sabatini wrote:
> > > > > > This is useful to test seeking on an input file.
> > > > > 
> > > > > if its for testing seeking, it might be interresting to allow
> > > > > specifying more than 1 value.
> > > > > that is seek to X demux for Y duration then seek to Z
> > > > 
> > > > What about:
> > > > 
> > > > INTERVAL ::= (START+DURATION)|(START-END) 
> > > > INTERVALS ::= INTERVAL[,INTERVALS]
> > > > 
> > > > where START, END, and DURATION are duration specifications.
> > > 
> > > LGTM
> > 
> > Implemented this (in attachment). Now in ticket:
> > http://ffmpeg.org/trac/ffmpeg/ticket/1437
> > 
> > they ask to implement the equivalent of -frames:SPEC (indeed this
> > looks like a different feature), but maybe I could extend the syntax
> > START+#NB_FRAMES
> > 
> > and/or accept the syntax:
> > -END
> > +DURATION
> > 
> > to mean to read from the very start of the file (or from the current
> > position) until the ending point is met. Suggestions are welcome.
> > 
> > For example to read just the first 10 packets, we could specify:
> > -si +#10
> > 
> > or maybe I could implement a distinct -frames:SPEC option.
> 
> 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).

iam fine with any implementation you like ...

[...]

-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

Frequently ignored answer#1 FFmpeg bugs should be sent to our bugtracker. User
questions about the command line tools should be sent to the ffmpeg-user ML.
And questions about how to use libav* should be sent to the libav-user ML.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-devel/attachments/20130916/3860471e/attachment.asc>