[FFmpeg-user] Minimum configuration settings for ffprobe-only

[Frank Tetzel]

Am Sun, 30 Mar 2014 15:15:09 -0500
schrieb Eugene Gekhter <egekhter at pixcel.com>:

> On Sun, Mar 30, 2014 at 3:11 PM, Nathan Lewis
> <nlewis at mail.crawford.com>wrote:
> 
> > On Sun, Mar 30, 2014 at 3:46 PM, Eugene Gekhter <egekhter at pixcel.com
> > ="mailto:egekhter at pixcel.com">> wrote:
> >
> >
> > What would be the recommended configuration settings if all that was
> >
> > required was to build ffprobe for the sole purpose of determining
> > if ffmpeg
> >
> > can decode the input files?
> >
> > The ultimate goal is to compile this with Emscripten into
> > javascript to
> >
> > detect on client-side if the file a user wants to upload is even
> > worth
> >
> > uploading.
> >
> >
> >
> >
> >
> >
> > Wouldn't running "ffmpeg -i" against the incoming file and
> > returning no errors give you what you want?  If so, just running
> > make against source should yield the results you're after.
> 
> True, I am looking for something as light-weight as possible

Maybe you should limit your supported container formats drastically and
then just check against a whitelist of known video and audio codecs.
That way you could just use small container libraries.

Here's an example for mp4 files using libmp4v2:
http://tetzank.github.io/extractbitrate-js/site.html
(in Firefox Ctrl+Shift+K, in Chromium Ctrl+Shift+J for more info)
https://github.com/tetzank/extractbitrate-js

This was just a toy project of mine to try out emscripten. It just
tries to extract the bitrate.

Using ffprobe or libavformat might be too big.