Support Windows Platform about ffmpeg-kit

[redbrain]

+1, would be great if support for all desktop platforms existed

[mgenware]

FWIW, you can always embed pre-compiled ffmpeg / ffprobe binaries and run them directly in a windows app. Unlike Apple's app store, Microsoft (at least now) doens't force you to statically link all app components. We have published Microsoft store apps working just fine with embedded (ffmpeg, imagemagick, cwebp...) binaries.

[seamory]

+1, that will be great to using ffmpeg.

[remcova]

UPDATE: I've looked into the web implementation first for CHROME extensions. The option I came across was using ffmpeg in WASM. Unfortunately, Manifest V3.0 brings a lot of issues. With Manifest V2.0 you can get it working but it will stop working in January 2023 in Chrome, so this won't be worth the effort to implement.

To port it to Manifest V3, the code will need to be placed in a worker which doesn't have access to the DOM (document). Also, it can't be published on Chrome Store due to Manifest V2.

I haven't found an alternative yet to create an implementation for the web, it looks like this will be a pain in the ass

[Sandst4]

Any chance there is an update for Windows support? For a new project I'm working on the Windows support is really appreciated. Thanks!

[git-boya]

Hope to support Windows
thanks

[nukes]

+1 for windows support

[PaulineMoovency]

Is there any news about this?

[stephane-archer]

Any news? It feels like it will never come...

[stephane-archer]

@mgenware that would mean two code path, one for FFmpeg Kit and one for the embedded version right?
this would work but I wish FFmpeg was including this by default.
To run the embedded executable, do you copy it in a temporary folder then use Process.run ?

[mgenware]

@stephane-archer Right, windows has a seperate code path. No need to copy EXEs to a temp folder in our case. We are using flutter. Put all pre-built executables into a folder like (bin) and copy it to flutter windows build folder. The msix packaging tool automatically bundles them into a msix package.

To run a specific executable, e.g. bin/ffmpeg.exe:

// Do it only on windows.
assert(Platform.isWindows);

var args = ['a', 'b', 'c'];
// Get current process directory.
var processDir = p.dirname(Platform.resolvedExecutable);
// Get external executable path.
final exe = p.join(processDir, 'bin', 'ffmpeg.exe');

debugPrint('[Run process] $exe ${args.join(' ')}');
final res = await Process.run(exe, args);
if (res.exitCode != 0) {
  throw Exception('Code: ${res.exitCode}\n stdout: ${res.stdout}\n stderr: ${res.stderr}}');
}
// Return process output.
return res.stdout.toString();

Lastly, if you are submitting your app to Microsoft store, do test those pre-built EXEs on new windows 10 and 11 (not a dev machine already have many runtime DLLs installed). If it runs into any missing DLLs issues (e.g. vcomp140.dll), grab one and put it in bin folder as well.