Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Using Pyav for Handling Ffmpeg
See original GitHub issueCurrently, AFAIK, Manim calls Ffmpeg using subprocess, which is very slow. In a plan to making manim more faster we can use a Python Ffmpeg wraper, like Pyav which is written in C and is a lot faster than directly calling using subprocess and also more Pythonic. I think doing this would just need to edit a file scene_writer.py. Also, this would mean that we wouldn’t need to ask users to install Ffmpeg as it would be included in PyAv.
Refs
Pyav Documentation: https://pyav.org/docs/stable/index.html Pyav Project Source: https://github.com/PyAV-Org/PyAV
Issue Analytics
- State:
- Created 3 years ago
- Reactions:3
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Interesting suggestion - I’m generally in favor of this, though I would hesitate to make the change entirely without first having a more robust test suite.
Also, instead of replacing the current file writer to use PyAV, we could implement a new one, FileWriterAV that uses this but keep using the ffmpeg one as default until FileWriterAV is stable.
Any updates here?