![]() MPlayer would stop playing altogether if the CPU couldn't keep up. Compare to VLC, which was able to play the video at ~24 fps during low motion screens and then just stop updating the picture for a while if decoding couldn't keep up. The best results I've seen for a sufficiently high bitrate H.264 1080p stream on OS X was by using Media Player Classic Home Cinema running in Windows inside VMware. Nothing like watching blade runner final cut and being slowly infuriated by those epic scenes being subjected to massive chop and screen tears. Im sure they both drop frames, but VLC does so much more gracefully, resulting in no noticeable distortion, while mplayer extended makes it obvious (and incredibly annoying) to the viewer. On my macbook pro (exactly a year old at this point) vlc plays it without a stutter, mplayer extended will drop frames like an epileptic. ![]() (which may not be any more difficult than trying to understand the old quicktime C API.)Ĭompare 1080p H.264 matroska playback in vlc to mplayer: It could have been the framework but it looks like mkv will be the open container and somebody will tie together enough libraries and codecs into a generalized framework- or we'll just have to jam it all together ourselves. Not much out there as far as I've seen that competes with the power of quicktime. This makes those easier to implement while quicktime has been open ended and not tied to any 1 format (other than its own container format) the timecode in quicktime is confusing because its not a video time code but an abstraction.īasically apple dropped the ball when they didn't open source the library years ago (and they did ask for public input for a short period without much attention given to it) now we have MKV containers and the zombee avi containers and many specialized libraries. What I see now is alternatives usually built around a single format library with an import/export system added on. It is a solid library with a lot of extendability for its size, age, and complexity - its in C and I've coded for it a little bit. The quicktime file format is the basis of the mp4 file format as well. It has gotten stale and others have replaced it but it was the foundation for digital video for many years and its still around being used for this. Its OLD and used to be the basis of nearly all video editing software. It is a massive video library (with a larger code base than windows 95) used to power video editing etc. I live in Australia, youtube and many flash videos here are frankly, bloody annoying, often we open a youtube video here, click play, let it start playing then quickly hit pause so it fills the full buffer :/ (if you don't quickly hit pause and it plays up to where the buffer end is, that can be a problem too)įWIW: I'm not a coder, perhaps this is significantly more complex than it sounds to impliment but damnit it could make many things smoother and simpler. I want this on my PS3 media playbakc, my Xbox 360, Media player classic, GOM, VLC - everything damnit! I'm willing to goddamn wait as long as the end result is a smoother experience! ![]() This is pretty straightforward stuff and yet, do we have these kind of controls? I frequently play back files which just happen to be close to the bitrate of my wireless connection, why can't I have the program specifically pre-buffer 100mb of data and then play back from the 100mb? Then when the bitrate is higher, it drops to 80 or 50 but when it's lower, it re-fills. I still don't see enough buffering code and SPECIFICALLY buffering controls for users in any media player.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |