On 07/07/2010 12:35 PM, App Deb wrote: > You have dual core so 60% means: > > 50% (full one core) is for decoding, > > and the rest 10% is for audio, resizing etc. Oh - didn't think about this - yes... you could be seeing the wrong thing in "top". If you have more than 1 CPU/Core you should push "1" in "top" to get separate statistics per CPU/Core. Push "W" to save your settings. (Use "s" to change statistics collection time, "1" sec. is good.)
Use "htop" to see threads. As far as I know "top" won't show those. So you can't check if your multi-threaded mplayer is really using more than 1 thread/process. BTW: On my core2duo 2,4 GHz I have no problems watching H.264 encoded 1080p videos with AAC sound. All decoding is done in software. When I use original mplayer 720p is possible without problem, 1080p only with low bitrate. For high bitrate 1080p I need the mt-version. Daniel > > You can't play the video correctly because your "decoder" is not > multithreaded and uses just the one CPU at its fullest. > > Try using multithreaded version of mplayer "mplayer-mt" (in some overlay > probably) with "lavdopts=threads=2" in mplayer config. > > On Wed, Jul 7, 2010 at 5:17 AM, Grant <emailgr...@gmail.com > <mailto:emailgr...@gmail.com>> wrote: > > I've been using VDPAU acceleration to play back Blu-Ray rips for a > while, but the extra layer is getting to be quite a hassle so I'm > trying to get decent performance via software decoding. It has > actually come a long way since the last time I tried and playing > Blu-Ray rips via mplayer is nearly watchable. I'm using a dual-core > 3.1Ghz CPU and one of the cores is only taxed up to 60% during > playback, but frames are still being dropped constantly. Does anyone > know where the bottleneck might be? > > - Grant > >
