-
Notifications
You must be signed in to change notification settings - Fork 375
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
Triage issues for v0.4.0 #268
Comments
I'm tempted to just cut a |
Any update on this? |
No not really. I've had a lot of personal stuff coming up. Honestly, while I've been reading all of the notifications from GitHub (as you can tell my be noticing this at all) I've been stuffing them into a "FLOSS" folder for when I eventually dig myself out. As responsible as it may or may not be, I think I could be okay with releasing as-is, and seeing what happens. Can I get some 👍 on that? |
👍 from me |
I would appreciate that too! |
+1 Use pyav in my project. |
So... uh... I just released v0.4.0. A couple tests fail, I think because of FFmpeg changes in the ~6 months since I've run them. |
There has been a ton of work done since v0.3.3. We should cut out a new release.
However, I get the feeling that there are some regressions with it. We should triage the tickets still open since v0.3.3 to make sure they can be "ignored" for a new release.
(edited to just be the issues left to address)
Stream.encode
returns a list of packets, instead of a single packet.AudioFifo
andAudioResampler
will raiseValueError
if input framesinconsistant
pts
.CodecContext.rate
has been removed, but proxied toVideoCodecContext.framerate
and
AudioCodecContext.sample_rate
. The definition is effectively inverted fromthe old one (i.e. for 24fps it used to be
1/24
and is now24/1
).time_base
,rate
) will beNone
if they are invalid.InputContainer.seek
andStream.seek
will raise TypeError if givena float, when previously they converted it from seconds.
😨
The text was updated successfully, but these errors were encountered: