←back to thread

1113 points Bluestein | 1 comments | | HN request time: 0.418s | source
Show context
Agingcoder ◴[] No.41277899[source]
I didn’t know mplayer had been forked - this looks good to me. The primary reason why I used mplayer in the early 2000s was performance, both in terms of cpu and for lack of a better word ‘ smoothness ‘.

Basically all other players seemed to produce choppy videos ( including regular dvd players ) but mplayer didn’t ( and there was no motion interpolation). A friend of mine told me that mplayer was very accurate ( ie each frame lasted exactly the same duration), unlike most players on the market at the time and this explained the ‘smooth’ feeling.

Is this smoothness advantage still the case ? Would anyone know why it felt like that years ago ?

replies(3): >>41277955 #>>41278808 #>>41279401 #
1. lysace ◴[] No.41279401[source]
The primary reason that many of us still used MPlayer 20 years ago was that it did keyboard-based seeking really well. Nothing fancy, just look for the closest I-frame from the target time and move exactly there.

This art of quick seeking sort of got lost in time as the distance between UX people and people who understand H.264/265/etc in detail grew.

On Apple TV: At best it takes like 500 ms. At worst (the Max app), like 6000 ms.

MPlayer 20 years ago: 17 ms.