[jmaw]

You should look into how other companies and tools that use FFMPEG handle this situation.

I wonder if you can keep your application itself closed source, but make an open-source adapter that handles the interaction with FFMPEG.

I'm not super familiar with open source licensing, and IANAL, so make sure to do your own research :)

As an example, I believe Audacity required me to install ffmpeg manually myself, and add it to my path. This is slightly different since Audacity itself is also open source. But could be helpful to reference.

[noduerme]

Yes, Audacity definitely requires that. It can't open or save mp3s unless you separately install ffmpeg.

[kolx]

Thank you, I guess I won't be fixing any bugs tonight but at least I will figure out how to comply. I appreciate the help for real!

[alfg]

This is how I handle it with my latest project, https://video-commander.com.

Prompting the user to install, or auto-installing FFmpeg separately, rather than bundling the binary. The problem is FFmpeg can be configured in so many ways and the general install binaries are usually LGPL compatible.