Hi On Friday 21 January 2005 17:50, Sam Hocevar wrote: > On Fri, Jan 14, 2005, Michael Niedermayer wrote: > > > ffmpeg is not optimized for newer CPUs, quiet the contraty is true, > > > since confflags contains "--disbale-mmx". This makes ffmpeg to slow for > > > my use: While capturing a live video and audio stream yesterday, ffmpeg > > > was to slow to keep up on my old Dual-P3-600 and A/V synchronisation > > > was completely lost after a short time. A selfcompiled ffmpeg with mmx > > > enabled was working completely fine. > > > Please consider providing serveral ffmpeg binaies with (mmx|pthreads) > > > (en|dis)abled. > > > > theres no need for a version with mmx disabled, its detected at runtime > > unless it has been disabled with --disable-mmx > > However, the current MMX code does not build in PIC mode, which is > required by policy. This is why --disable-mmx is used until it is fixed.
do you use -fomit-frame-pointer? you should if its not already used and if it doesnt fix it, why dont you disable just the problematic part instead of disabling everything? it might also be interresting to see where compilation fails (and the gcc version would be interresting too) if all else fails, IMHO there should be some warning about this so a user is aware that he could get a much faster ffmpeg by recompiling with pic disabled [...] -- Michael "nothing is evil in the beginning. Even Sauron was not so." -- Elrond -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
