I have written a free and open-source app (available on GitHub) that needs to bundle a static binary build of FFmpeg's command line executable tool, but does not link to its code statically or dynamically. My app invokes the bundled FFmpeg binary as an external (child) process (as if it were installed separately on my machine and I were invoking it from the command line). So, there are no references to any FFmpeg source code or libraries (dylib) anywhere in my app code..
Where I got the ffmpeg binary: FFmpeg download page
I bundle FFmpeg with my app in this way so that my users don't have to worry about having FFmpeg installed and configuring my app to point to their FFmpeg installation.
From my research, I understand that FFmpeg is licensed under GPL V3. I have also read FFmpeg's legal compliance checklist page at FFmpeg legal compliance checklist. The terms of GPL are somewhat clear in the cases of "static linking" and "dynamic linking" of the library (in my case, FFmpeg) with app code. However, my scenario, it seems, is neither of the two.
I have also read this other page here which addresses a similar scenario: (other Stack Exchange question). But what is unclear is - if I need to make the FFmpeg source code available, how exactly? From within my app or in my app's documentation? Do I need to include the source as part of my app bundle? Do I need to provide a link to it from my docs?
I have currently not licensed my own app in any way. It (and its source code) is available for free download on GitHub. So, if I include FFmpeg in the way described above, what must I do to comply with the GPL license terms?
P.S. If you'd like more details about my app and how it uses FFmpeg (including my code), I'll be happy to share.