Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

FFMPEG crashes if the script is a .pyw #517

Closed
whelly opened this issue Mar 29, 2017 · 3 comments
Closed

FFMPEG crashes if the script is a .pyw #517

whelly opened this issue Mar 29, 2017 · 3 comments

Comments

@whelly
Copy link

whelly commented Mar 29, 2017

I'm trying to integrate my script into a background service, which means I need the command window to be invisible for compatibility issues. Everything works great as a normal .py file, but trying to hide the console as a .pyw causes some issues when the render starts. I see a spike in my CPU usage for a few seconds, then it exits. I also tried setting the FFMPEG parameter "loglevel" to silent but that didn't help either. Any idea what's causing this problem? I'm using Windows, Python 2.7, and the MoviePy package from pip.

@whelly
Copy link
Author

whelly commented Mar 30, 2017

Figured it out! There is a nifty parameter for write_videofile called progress_bar, so setting that to False fixed the issue! You may also have to set verbose to False as well. It's missing from the documentation which is why I didn't think of it, so perhaps adding that might help others looking for windowless renders. BTW, thanks for an awesome library Zulko!

@ghost
Copy link

ghost commented Mar 30, 2017

Awesome!

@ghost ghost closed this as completed Mar 30, 2017
@tburrows13
Copy link
Collaborator

The reason its not in the docs is because it was only recently added (#380 and #458), and is not in the PyPI version of moviepy. When we release another version, I assume we'll redo the docs to include all the added docstrings. Until then, we can't have the docs documenting unimplemented stuff!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants