Use of ffmpeg-python Complicating Incorporation of uv, PyInstaller AND Breaking Windows Executables

[ebb-earl-co]

When using PyInstaller to create system-specific executables, even though FFmpeg is compiled right in place and included in the binary, the ffmpeg-python package does not look in the current directory for an ffmpeg{.exe} executable!

Therefore, on systems that do not have FFmpeg installed anywhere, I had pointed out that it wouldn't be necessary as it would be bundled in the tidal-wave binary! This is untrue, as ffmpeg-python doesn't know how to look for the "local" ffmpeg{.exe}.

Solution is to divest from ffmpeg-python and just expand use of subprocess, shlex, and probably some other helpers that know how to interact with the $SHELL being used for common executable locations/paths.