-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Release 2.4.1 #3711
Comments
I hope 2.4.1 includes also #3707. |
+1 from me on both of the above. |
Hi @fluffy, we believe the current OpenH264 release is seriously broken. Suggest creating a 2.4.1 release with the fix that has already landed. Unfortunately I don't know any way to contact the OpenH264 developers other than to ping you directly, which is unfortunate. It would be nice if this issue tracker were monitored more actively. |
Hi @mcatanzaro, I will release version 2.4.1 in the next few days. |
That's great news, @BenzhengZhang! |
@torokati44 Unfortunately, I cannot include this PR because it has not been reviewed yet and I am not sure whether there is a risk of regression. We will evaluate it in the next release. You are also welcome to review it. |
@joakim-tjernlund These fixes are expected to be included in the next release and will be picked up after review : ) |
v2.4.1 release completed https://github.com/cisco/openh264/releases/tag/v2.4.1 |
Thank you! (And now I know whom to ping in the future... sorry Benzheng. :) |
openh264 has not moved at all since release, surely you must have an hour/week to spend on open264? |
Hi, it would be nice to have an OpenH264 2.4.1 release with this fix that's required to play the Big Buck Bunny test video.
The text was updated successfully, but these errors were encountered: