You have dual core so 60% means:
50% (full one core) is for decoding,
and the rest 10% is for audio, resizing etc.
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
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
On 7 July 2010 12:27, Daniel Troeder dan...@admin-box.com wrote:
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.
What do you get when you press upper case 'H' in top?
--
Regards,
You have dual core so 60% means:
50% (full one core) is for decoding,
and the rest 10% is for audio, resizing etc.
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
On 07/07/2010 03:01 PM, Mick wrote:
On 7 July 2010 12:27, Daniel Troeder dan...@admin-box.com wrote:
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.
What do you get when you press
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
6 matches
Mail list logo
