Replies: 3 comments 7 replies
-
That's fantastic to hear! I'm thrilled you found the migration smooth and that the type hints and docstrings integrated seamlessly with VSCode. If you have any further feedback or questions as you continue to use the library, feel free to reach out. Your input helps us improve the project for everyone! |
Beta Was this translation helpful? Give feedback.
-
I also used this library to replace ffmpeg-python (after getting stuck with the bug where multiple upstream nodes have the same label) and it works really well for my use case (many concat filters -> xstack filter). The API design is clean and consistent. (I don't have much experience with ffmpeg, so it would have been nice to get a few more examples of usage) |
Beta Was this translation helpful? Give feedback.
-
I switched to this library as an alternative to ffmpeg-python after encountering issues with duplicate labels in complex filter graphs (many concat filters feeding into an xstack filter). It has proven to be a solid solution for my workflow, thanks to its well-designed and consistent API. Although I’m not very experienced with FFmpeg, having more usage examples would have been helpful for getting started more smoothly. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Just used this library to replace
ffmpeg-python
- really easy migration, and the type hints and docstrings show up in VSCode without a hitchBeta Was this translation helpful? Give feedback.
All reactions