Could not find ffprobe executable
See original GitHub issuethis could be an issue with dependencies not up to date, or within the ffprobe package itself. I am running into an error saying Could not find ffprobe executable
. Not sure if this has been addressed yet or I am the first to tell you.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:6
- Comments:17 (5 by maintainers)
Top Results From Across the Web
Cannot find ffprobe? - node.js - Stack Overflow
If the FFMPEG_PATH environment variable is set, fluent-ffmpeg will use it as the full path to the ffmpeg executable.
Read more >@ffprobe-installer/ffprobe - npm
Platform independent binary installer of FFprobe for node projects. Latest version: 1.4.1, last published: a year ago.
Read more >@ffprobe-installer/ffprobe - npm package | Snyk
Useful for tools that should "just work" in multiple environments. Installs a binary of ffprobe for the current platform and provides a path...
Read more >FFMpeg Executable not found - Laracasts
I have installed FFMPeg on my system and have added it to the system variables, when I run ffmpeg on console it shows...
Read more >ffmpeg and ffprobe in electron - autoEdit 2 User Manual
So we don't want to either assume ffmpeg/ffprobe that is installed nor install it on their system as it could lead to conflicts...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I had this issue also, everything worked fine on windows… But when I ran on an azure ubuntu agent I got the error about not finding the ffprobe executable.
I also have @ffmpeg-installer/ffmpeg and fluent-mpeg installed and am ultimately chopping up some cypress videos with ffmpeg commands. I was using get-video-duration in this process.
Incidentally I got a similar message when trying to use ffprobe directly to get the video duration (some maybe the problem lies elsewhere):
Ultimately I got around the problem by using a different module, node-video-lib to get video durations and everything is working again (this doesnt use ffmpeg/ffprobe).
I dont know if this helps anybody.
I spent a lot of time trying to resolve it so would love to know what is actually going on here
I bumped get-video-duration down a version and things have been working file. currently running on
3.0.2