Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Incorrect Usage of PyInstaller to Bundle FFmpeg #236

Closed
ebb-earl-co opened this issue Mar 8, 2025 · 1 comment
Closed

Incorrect Usage of PyInstaller to Bundle FFmpeg #236

ebb-earl-co opened this issue Mar 8, 2025 · 1 comment

Comments

@ebb-earl-co
Copy link
Owner

Based on errors reported in #235 and #230 and #39, investigation using $PREFERRED_SEARCH_ENGINE revealed that there is a special distinction between running tidal-wave from the source code and running tidal-wave from the PyInstaller-created binaries. In no particular order:

  • For Windows, a semicolon is needed in the value passed to pyinstaller --add-data= rather than a colon on the UNIX-like platforms: StackOverflow link
    • More specific information around FFmpeg and PyInstaller together here
  • Because of various system paths and library finding behaviors, it isn't generally possible to just add the FFmpeg binary (ffmpeg or ffmpeg.exe) to the top-level directory of tidal-wave that is bundled using PyInstaller. Rather, a special attribute of the Python standard library, sys._MEIPASS needs to be interrogated and logic based on its value: StackOverflow link
  • The python-ffmpeg package looks in specified directories for the FFmpeg binary, and that does not include the current working directory!
@ebb-earl-co
Copy link
Owner Author

Closed with the merging of #237

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant