Evaluating FFmpeg-Kit Capabilities on iOS: Simulator vs. Real Device

When developing media processing applications in Flutter, ffmpeg_kit_flutter is often the go-to solution for harnessing the power of FFmpeg. However, ensuring consistent behavior across different deployment targets—specifically between the iOS Simulator and physical iOS devices—can sometimes be a source of anxiety for developers.

In our recent project, we conducted a rigorous evaluation of ffmpeg_kit_flutter_new_full (version ^2.0.0, running FFmpeg n8.0) to definitively map out the available capabilities and identify any true discrepancies between the two environments.

Here is a summary of our findings and the methodology we used.

1. A Robust Evaluation Methodology

Historically, developers might rely on "probe" commands—attempting to run a specific filter and checking if it fails—to determine if a feature is compiled into the FFmpeg binary. This approach is prone to false negatives due to minor syntax errors or missing input files.

To eliminate these false negatives, we adopted a "self-describing" evaluation method. By querying FFmpeg directly for its compiled capabilities, we obtained a definitive list of what is and isn't supported.

The evaluation process executes the following commands sequentially:

1. ffmpeg -filters (Lists all available filters)
2. ffmpeg -encoders (Lists all available encoders)
3. ffmpeg -h filter=palettegen (Checks specific parameters for the palettegen filter)
4. ffmpeg -h filter=paletteuse (Checks specific parameters for the paletteuse filter)

Judgment Rules:

• Filter Availability: Is the filter listed in the -filters output?
• Encoder Availability: Is the encoder listed in the -encoders output?
• Parameter Availability: Does the parameter appear in the specific -h filter=* help text?

2. Capability Comparison: Simulator vs. Real Device

Applying this methodology, we compared the capabilities of the iOS Simulator build against a physical iOS device build.

Here is a subset of the critical capabilities we evaluated:

Capability	Simulator	Real Device
mpeg4 (Encoder)	AVAILABLE	AVAILABLE
h264_videotoolbox (HW Encoder)	AVAILABLE	AVAILABLE
libx264 (SW Encoder)	UNAVAILABLE	UNAVAILABLE
decimate (Filter)	AVAILABLE	AVAILABLE
mpdecimate (Filter)	UNAVAILABLE	UNAVAILABLE
palettegen (Filter)	AVAILABLE	AVAILABLE
paletteuse (Filter)	AVAILABLE	AVAILABLE
colorspace (Filter)	AVAILABLE	AVAILABLE
zscale (Filter)	AVAILABLE	AVAILABLE
wb (Filter)	UNAVAILABLE	UNAVAILABLE
bilateral (Filter)	AVAILABLE	AVAILABLE
vibrance (Filter)	AVAILABLE	AVAILABLE
gamma (Filter Parameter)	UNAVAILABLE	UNAVAILABLE
quant_mode_neuquant	UNAVAILABLE	UNAVAILABLE
weight_w	UNAVAILABLE	UNAVAILABLE
diff_only	UNAVAILABLE	UNAVAILABLE
sierra_lite	UNAVAILABLE	UNAVAILABLE

The Verdict on Capabilities

The capabilities are perfectly consistent.

Under the same ffmpeg_kit version (full package), there are zero instances where a filter or encoder is available on the Simulator but missing on the real device, or vice versa. The fear of "it works on the simulator but fails on the device due to missing FFmpeg modules" is unfounded when using this package.

Note: The full package deliberately excludes GPL-licensed libraries like libx264 by default, which is why it shows as UNAVAILABLE. Hardware acceleration (h264_videotoolbox) is available and recommended for iOS.

3. Understanding the True Differences

If the capabilities are identical, what are the actual differences developers need to be aware of?

3.1 Architectural Differences

• Simulator: Built for x86_64 (or arm64 depending on your Mac's silicon, but fundamentally a macOS execution environment).
• Real Device: Built natively for arm64 iOS hardware.

3.2 Execution and Startup Stability

While FFmpeg itself behaves consistently, the environment it runs in does not:

• Real Device Nuances: Running heavy FFmpeg tasks on a real device during development can sometimes be affected by the USB connection stability, code signing processes, or the Dart VM Service discovery mechanism. This can occasionally lead to timeouts or apparent hangs during debugging that do not occur in a release build.
• Simulator Stability: The Simulator generally exhibits more stable startup and debugging attachment phases since everything is local to the host machine.

Conclusion

By shifting from syntax-dependent probing to a self-describing capability query, we confirmed that ffmpeg_kit_flutter_new_full provides a highly consistent feature set across iOS Simulators and real devices.

When encountering issues that appear on a real device but not the Simulator, developers should look past missing FFmpeg modules and instead investigate file path permissions, hardware resource constraints (like memory limits during heavy processing), or debugger connection instability.