Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fall back to ffmpeg instead of ffprobe #681

Closed
phihag opened this issue Feb 13, 2013 · 1 comment
Closed

Fall back to ffmpeg instead of ffprobe #681

phihag opened this issue Feb 13, 2013 · 1 comment

Comments

@phihag
Copy link
Contributor

@phihag phihag commented Feb 13, 2013

Some users (notably on Mac OSX) do have ffmpeg, but not ffprobe. We should simply call

ffmpeg -i file -invalid

(or something better, if possible) in these cases.

@ubitux
Copy link

@ubitux ubitux commented Mar 19, 2013

Note that contrary to ffmpeg, ffprobe has various outputs such as JSON, XML, CSV, "flat", etc. which might be more stable (and friendly) than parsing ffmpeg output. See http://ffmpeg.org/ffprobe.html#Writers for more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.