Something that wasn’t available or good enough for mobile platforms. Moreover, I created MobileFFmpeg to fill a gap. So, adding support for those platforms wasn’t that easy. flutter_ffmpeg was backed by MobileFFmpeg and MobileFFmpeg was only Android and iOS (and tvOS). Also, I didn’t have native implementations for them. Initially, I rejected them because they were not in the scope of the project. Some of those requests came in flutter_ffmpeg, my Flutter port of MobileFFmpeg. Recently, I received a lot of requests about supporting non-mobile platforms like macOS, Linux, etc. The list below also shows some of the major features implemented since then.

Changelog of MobileFFmpeg includes all those changes implemented since 2018. Meanwhile, I had already added support for GPL licensed libraries and created prebuilt packages.Īfter releasing these updates, I kept fixing bugs and continued to develop new features. In the end, I decided to drop them and re-implemented the iOS library with static libraries. Apple documentation wasn’t helping me much. They were working in Xcode but App Store Connect wasn’t accepting apps built using them. Then, I spent quite a lot of time on shared libraries for iOS. It took a few iterations to stabilise it but after that it became one of the core features of the library. First, I developed the log callbacks to redirect console output of FFmpeg. I felt the need to make some changes in the implementation.

And some features weren’t working that well. But then realised that the wrapper library I created wasn’t easy to use. The main idea was to run FFmpeg commands on mobile platforms as you run them on desktop. At first, I wasn’t too keen to add new features to MobileFFmpeg.

Xamarin android ffmpeg