Replies: 2 comments
-
See: https://basswood-io.com/blog/why-were-forking-pyav Switching to BasswoodAV is comparable to upgrading one major version of PyAV. One notable breaking change is how subtitles are handled: # PyAV 14
for subset in packet.decode():
for sub in subset:
print(sub)
# BasswoodAV
for sub in packet.decode():
print(sub) |
Beta Was this translation helpful? Give feedback.
0 replies
-
I see, thanks for clarification! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello PyAV maintainers,
I've noticed some changes in the PyAV ecosystem that have left me confused about the current state of the project, particularly regarding its relationship with BasswoodAV. I'd greatly appreciate some official clarification on the following points:
Project Status and Ownership
I've observed that PyAV documentation is now hosted at pyav.basswood-io.com, and the installation instructions on PyPI refer to a GitHub repository at https://github.com/basswood-io/PyAV.git. This suggests a transition from the PyAV-Org organization to basswood-io.
Package Naming and Recommendations
There appears to be multiple ways to install what seems to be the same or similar functionality:
For users who want to use FFmpeg bindings in Python:
Documentation
Compatibility Considerations
I appreciate any clarification you can provide on these matters. This information would be very helpful for current PyAV users who are trying to understand the best path forward.
Thank you for your time and for maintaining this valuable project.
Beta Was this translation helpful? Give feedback.
All reactions