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

Reindl Harald h.reindl at thelounge.net
Sun Mar 30 22:19:29 CEST 2014

Am 30.03.2014 22:11, schrieb Nathan Lewis:
> 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.

besides that your quoting is completly broken

did you read "Emscripten into javascript to detect on client-side"?
if you can force the client to a) install ffmpeg and b) call it from the
browser you must have found a unknown security bug in a specific browser
and force the user to use exactly that client and never update

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 246 bytes
Desc: OpenPGP digital signature
URL: <http://ffmpeg.org/pipermail/ffmpeg-user/attachments/20140330/cdde3332/attachment.asc>

More information about the ffmpeg-user mailing list