My computer is a 800MHz Celeron and yes I did test it and the performance loss is noticeable. Monitor's refresh rate is not my limiting factor at all. It runs at 60Hz and if I play a double (or triple) speed video it looks a lot smoother when seeking forward. MPlayer was always very famous of being efficient on hardwares very different from each other. This is the number one property I really like it for. I don't use FFMpeg, but libmpeg2, never used FFMpeg for MPEG-2 decoding because it's slow as hell for this purpose including seeking as well. So I was talking about libmpeg2 producing "incorrect frames like that". 2010/1/4 Uoti Urpala <uoti.urpala at pp1.inet.fi>: > On Mon, 2010-01-04 at 23:18 +0100, Barnabas Hajas wrote: >> Answering to your idea - compiling Mplayer from git will give me fast >> seeking - I don't care about picture being accurate for performance >> loss. I do want those nasty blocks :) like in 1.0pre7 or 1.0rc1 >> because the more picture I see the more efficiently I can look for a >> part in a movie clip, also I think they look cool. Do I need to mess >> around with libmpeg2 if I want this "feature" or is there another >> tricky command line option? ;) > > Is your machine really slow enough that any "performance loss" is > noticeable? Did you actually test it? Most machines should be fast > enough decoding mpeg2/4 video frames that monitor refresh rate is more > likely to be the actual limiting factor on number of frames you can see. > > I think there's no way to make the FFmpeg decoder produce incorrect > frames like that, so if you actually want to see them then you'll have > to use libmpeg2. > > _______________________________________________ > MPlayer-users mailing list > MPlayer-users at mplayerhq.hu > https://lists.mplayerhq.hu/mailman/listinfo/mplayer-users >
