Expose ffprobe command from ffmpeg.wasm

[izogfif]

ffprobe.c is already present in src/fftools folder. Let's expose it via .ffprobe command!

[netlify]

✅ Deploy Preview for ffmpegwasm canceled.

Name	Link
🔨 Latest commit	bd903bb
🔍 Latest deploy log	https://app.netlify.com/sites/ffmpegwasm/deploys/66d1ddb844cf6c000999ccc8

[arielr]

@izogfif do you know when this feature will be marged to main?
Is there any other way access to ffprobe?

[izogfif]

@izogfif do you know when this feature will be marged to main? Is there any other way access to ffprobe?

@arielr I don't know. I have no relation to maintainers of ffmpeg.wasm and can't say when they decide to merge any pull request into ffmpeg.wasm repository.
There is no built-in way to access ffprobe from the current ffpeg.wasm code. You can just clone the repository with this feature and build it yourself.

[SimonHudec]

Please can someone merge this?

[lucasgelfond]

+1 please merge!

[lucasgelfond]

Looks great!

[lucasgelfond]

LOL i became a maintainer on this project specifically to merge this PR — @izogfif thank you so much

[SimonHudec]

lol glad to have this merged, ty

[lucasgelfond]

ofc! @SimonHudec @izogfif the build is failing on my local machine so I'm struggling to deploy, any tips? I tried to publish the build artifacts produced in the GH action to npm, but the newest package still doesn't seem to have ffprobe exposed. Would love to get tue across the finish line if you have any tips, I also should have some time to actually figure out emscripten and debug this build myself after the holidays

[izogfif]

@lucasgelfond Please provide more details: what you do, what you expect to happen, and what happens instead. Clone repository https://github.com/izogfif/ffmpeg.wasm/tree/main and try building that version. Will it work for you?