>=media-video/ffmpeg-0.5_p21602[mp3=,threads,x264=] You know, right, that both mp3 and x264 are ENCODING use flags? For lame an x264 (which is an h264 ENCODER), and neither is needed for DECODING?
Oh, that sounds bad indeed. Thanks for spotting it. How do I check that the system ffmpeg supports decoding mp3 and x264 then?
1) It's H.264, not x264, which is the name of one specific _encoder_ implementation 2) FFmpeg always supports MP3 and H.264 for decoding when the default ebuild is used 3) Chromium can easily and should detect this kind of thing at runtime instead of hardcoding it in at compiletime
Fixed with a recent bump, thanks for spotting this. Reimar, thanks for your comment too.