GNOME Bugzilla – Bug 648002
[0.11] [h264parse] Remove old, non-base-parse version
Last modified: 2012-02-08 20:13:47 UTC
See summary
Let's do this after the release. Keeping the legacy element around allows people to revert to that in case there are regressions. Also, it has an output-format property which the new one does not have, and IIRC there's a known issue with negotiation based on output caps in a dynamic-plugging context.
Is there something more known on this known issue, so it may be fixed and/or made to handle by the new h264parse ?
> Is there something more known on this known issue, so it may be fixed and/or > made to handle by the new h264parse ? Don't remember any more, I'm afraid. May be fixed by now of course. Removed legacyh264parse in 0.11. Feel free to also remove it from master if you want to kill it. I'm happy to just let it fizzle out in 0.10. commit 8765068879331b2f911d70ee88baa36c4217aec2 Author: Tim-Philipp Müller <tim.muller@collabora.co.uk> Date: Wed Feb 8 20:09:39 2012 +0000 Remove legacyh264parse element One h264 parser ought to be enough for anybody. https://bugzilla.gnome.org/show_bug.cgi?id=648002