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