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
About http://mikeboers.github.io/PyAV/examples.html #255
Comments
Sorry, please ignore the third question. (I have not noticed #222.) |
Part 1: The example is very likely bad given recent changes to the API (in which
... because we should no longer need to call it multiple times to flush either; a single flushing call should clear it out. Part 2: We still test against 2.6 and 2.7 on Travis. I'm still largely stuck in 2.7 (due to working in the VFX field and that I expect Maya to never upgrade to Python 3). I imagine once it flushes properly, the video will be as expected. Part 3: Like you found, we're just using the FFmpeg API in a way they don't like. It is just deprecated, and works fine. It is an annoying message though. |
Part 1. Originally my question is:
We need to do this? And You might explain this in the context of design of PyAV as developer, if so, in the future we will have no need to "Finish encoding the stream" for flushing? Part 2:
Do you mean PyAV can fix it or the end-user can fix it? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
The bellow snippet is almost the same as Examples:
About this example, I have three questions.
av/utils.pyx
:Question: Must we do always "Finish encoding the stream"? If so, how do we write this? And what does it mean?
Question: According to classifiers, PyAV doesn't drop the support for Python 2.7, but actually seems not. What is the situation for supporting Python 2.x?
the warning from AVStream:
(I tried this with ffmpeg 3.2.4 and 3.3.2, the both seems the same.)
Question: What version of ffmpeg should we use currently? At least, the build-deps seems to expect 3.2.
The text was updated successfully, but these errors were encountered: