It would be nice if media-plugins/gst-plugins-meta would include media-plugins/gst-plugins-openh264.
As a comment to the title changes - USE=x264 is for "Enable h264 encoding using x264" while openh264 is both encoding and decoding, but not via x264. ffmpeg uses a local openh264 for using openh264 for encoding.
(In reply to Mart Raudsepp from comment #1) > As a comment to the title changes - USE=x264 is for "Enable h264 encoding > using x264" while openh264 is both encoding and decoding, but not via x264. That's what I thought, too. I'm adjusting the summary accordingly. > ffmpeg uses a local openh264 for using openh264 for encoding. So ffmpeg already has a local "openh264" useflag? Maybe that one could be promoted to global and be used for gst-plugins-meta, too?
Global USE flags should generally have usage by 7+ packages or so, but that doesn't mean the local USE flags should all be differently named for the same-ish thing :P Regarding this whole gst-plugins-meta stuff I don't have much more opinions besides that, other than we should really have a working gstreamer missing-plugins implementation instead of all this. So I leave all this USE flag mess for Pacho and co :)
I would use x264 anyway, it seems to be the one used by everything that is not ffmpeg :/ (also, we are currently not making distinction between encoding/decoding, that would make the ebuild even more complicated and, also, reverse deps more prone to have incorrect dependencies on them :S -> bug 425308)
Would love to see this happen currently the only way to have h264 playback in WebKitGTK based applications is to either use the openh264 plugin or the libav one, the latter pulls in the entirety of ffmpeg even tho nothing else on my GNOME system would use it :/
