1 |
On 05/21/2010 02:03 AM, Canek Peláez Valdés wrote: |
2 |
> On Thu, May 20, 2010 at 5:08 PM, Nikos Chantziaras<realnc@×××××.de> wrote: |
3 |
>> Because as soon as you disable ALSA dmix and/or Pulse, suddenly you get |
4 |
>> acceptable sound latency. |
5 |
>> |
6 |
>> With OSS4, which has in-kernel mixing, it doesn't matter if you enable the |
7 |
>> mixer or disable it; sound always has acceptable latency. |
8 |
> |
9 |
> By that reasoning, the GUI should be in-kernel too. It would be then |
10 |
> really responsive al the time. I don't buy the argument. |
11 |
|
12 |
Then why does dmix lag? |
13 |
|
14 |
|
15 |
>> Thus, I can only conclude that mixing has to happen in-kernel. But I base |
16 |
>> this only on the ALSA/Pulse vs OSS4 comparison. It could also be that the |
17 |
>> user-space implementation of ALSA just sucks. But that's hard to believe, |
18 |
>> since if that were the case they would have fixed it several years ago |
19 |
>> already. |
20 |
> |
21 |
> No, it doesn't has to happen in-kernel; all the linux based phones |
22 |
> (which deal primarily with, you know, audio, including heavy use of |
23 |
> multimedia) use PulseAudio. And these are not very powerful machines; |
24 |
> so if the mixing in user space works in low powered devices, it must |
25 |
> work everywhere. I don't buy this argument either. |
26 |
|
27 |
Then why does dmix lag? |
28 |
|
29 |
|
30 |
>> It sounds reasonable from a designer's point of view. But a system is |
31 |
>> useless if it's only designed good but doesn't actually work in a |
32 |
>> satisfactory manner. |
33 |
> |
34 |
> It works for me, I repeat, and for a lot of other folks too. It's not |
35 |
> only a design decision made because it's "elegant"; it's made because |
36 |
> it works "in a satisfactory manner" (ex. me, others, Linux phones), |
37 |
> and because it's more flexible: put it in the kernel, and you loose |
38 |
> the capacity to do important changes and extensions (specially with |
39 |
> the way the Linux kernel development works). |
40 |
|
41 |
Why on earth would you want to put it in the kernel in the first place? |
42 |
That has nothing to do with the low level mixer. |
43 |
|
44 |
|
45 |
> In short, because it works "in a satisfactory manner" (to me and many |
46 |
> others, including all the N900 and Android users out there), I also |
47 |
> don't buy this argument. |
48 |
> |
49 |
>> Sorry, that just pretentious of you here. PulseAudio is the most flamed at, |
50 |
>> hated, sound-related software around. And this is because it does *not* |
51 |
>> work for many, many users, and the first thing they try to do is find out |
52 |
>> how to disable the thing. |
53 |
> |
54 |
> Sorry, but I believe the you are the one being pretentious; how long |
55 |
> has been since you tried PulseAudio? It has come a loooong way, and I |
56 |
> haven't seen any real flames against PulseAudio in many months (and |
57 |
> it's enabled in all major distributions). And that is because it's |
58 |
> working (I repeat my words) "for me and many more". |
59 |
|
60 |
I've tried it 6 days ago. Ubuntu 10.04. It's still a laggy, buggy, |
61 |
pile of ****. First thing I did was to disable it. |
62 |
|
63 |
|
64 |
>> You're mistaken in that a mixer should be in the same boat as network |
65 |
>> streaming, bluetooth, etc, etc. I believe the *mixer* should be in-kernel. |
66 |
>> Everything else doesn't need to be. PulseAudio's extreme latency problems |
67 |
>> (which even upstream admits can't be fixed easily) stem from that. |
68 |
> |
69 |
> I respectfully disagree; the kernel should pass along data and |
70 |
> messages to the sound hardware, and everything else (*including |
71 |
> mixing*) should be in user space. Not only in theory from an academic |
72 |
> and aesthetic point of view; *it also works*, to me, to many users who |
73 |
> doesn't complain (despite PulseAudio being used by default in ALL |
74 |
> major distributions), and to ALL the users of Android and MeeGo. |
75 |
|
76 |
Yes, you and many people also find it acceptable to run their games with |
77 |
10FPS, or to take their systems 1 minute to boot, etc. |
78 |
|
79 |
I am not one of those people. I don't like it when the sound lags. You |
80 |
may claim that it doesn't bother you. But you can't claim that it |
81 |
doesn't happen. |
82 |
|
83 |
|
84 |
> And to finish, I don't know how much you know about technical |
85 |
> decisions and design, but I know that Linus refused to accept OSS4 in |
86 |
> the kernel, I know that all major distributions decided to go with |
87 |
> PulseAudio, and I know that Intel, Nokia and Google are betting for |
88 |
> it. |
89 |
|
90 |
That doesn't mean ALSA is better. |
91 |
|
92 |
|
93 |
> So, no offense, but I trust more in those guys and the arguments I |
94 |
> have heard from them. And the consensus with them is to use |
95 |
> PulseAudio, and leave the mixing in user space. |
96 |
|
97 |
Then why don't they fix it? It's still crap after all this time. |