The ffmpeg configure script accepts --enable-nonfree and --enable-optimizations which are not turned on by default. I have noticed that the optimization flag makes a *huge* performance increase in some cases. I'll submit a patch for ffmpeg-0.5-r1 which creates USE flags for these options. Are there any reasons why they are not already included in the ebuilds? Reproducible: Always
Created attachment 189559 [details, diff] patch for new use flags
(In reply to comment #0) > any reasons why they are not already included in the ebuilds? 'optimizations' seems to be enabled by default; why do you get a "huge" difference? 'nonfree' is enabled as needed, e.g., when amr is enabled and recently faac.
indeed, optimizations yes which is output of current ./configure i don't see any reason to keep this bug open (except placebo feeling by enabling USE optimizations maybe? :-))
Right. For version 0.5 --enable-optimizations and --enable-nonfree make no difference. I think this was different with some 0.4.x pre-release versions.
