On Fri, 30 Oct 2009 06:17:51 -0500, Dale <rdalek1...@gmail.com> wrote: > Alan McKinnon wrote: >> >> I haven't snipped - the output might be useful later in the thread. >> >> First, the "slow system" message always means something, but it's a bit
>> generic. It means that mplayer can't process the audio fast enough and >> like >> the message says is often buggy driver or wrong configs. Try the >> suggestions >> listed. >> >> An OOo compile in the background will indeed kill interactive processes. >> I >> find that even on this DualCore2 2.6 notebook with 4G of RAM, building >> OOo >> sends the load through the roof, especially when it starts printing >> progress >> lines with lots of dots. It's IO blocking on something and the entire >> machine >> just sits there doing nothing whatsoever except sit in a tight loop >> waiting >> for soemthing to happen in the build. >> >> Try again once emerge OOo has completed. emerge KDE should not affect >> things >> anywhere near the same amount. >> >> >> >> > > I'm a snipping. LOL I haven't ignored this reply, I been testing some > things. It appears that some file types are worse than others. .mp4 > for example seems to be worse than a .flv. I'm still trying to make > some sense out of this so I can report back something that makes sense. > Trust me, that can be a challenge for me sometimes. ;-) kmplayer can get in the middle, can you -please- test regular mplayer from command line? I've had a similar issue a couple of weeks ago, and we were able to track it down on the mplayer mailing lists. If it's the same bug, I was able to consistently reproduce it in streams with ac3 (5.1) audio (stereo worked fine), and only when using ALSA. So, check that and see if you can see a pattern there. If you see that same pattern, then it might be the same bug, it's been fixed in the development branch, and the following ebuilds should work fine: 1.0_rc4_p20091026, 1.0_rc4_p20091026-r1, 9999 If not, then it's probably something else. But try with mplayer alone when debugging, since kmplayer just adds another level to worry about. For your reference, here's the bug I opened, there you can also find links to the relevant mails in the mplayer ML. http://bugs.gentoo.org/show_bug.cgi?id=286020 -- Jesús Guerrero
