1 |
On Sat, Apr 20, 2013 at 10:48 PM, Michael Mol <mikemol@×××××.com> wrote: |
2 |
> On 04/20/2013 05:34 AM, Walter Dnes wrote: |
3 |
>> On Fri, Apr 19, 2013 at 09:28:03AM +0200, Alan McKinnon wrote |
4 |
>> |
5 |
> |
6 |
> [snip] |
7 |
> |
8 |
>>> If you need it, PA can be great. Not everyone needs or wants it, many |
9 |
>>> people are quite content to just carry on as they always did and aren't |
10 |
>>> fazed with minor niggles about their audio. You seem to fall in this |
11 |
>>> category, so do many others. |
12 |
>> |
13 |
>> I think you've hit the nail on the head. Complex setups require |
14 |
>> complex software... deal with it. An analogy is that an 18-wheeler |
15 |
>> semi-tractor trailer with a 17-speed manual transmission (plus air brakes |
16 |
>> that require months of training to manage/use) is much more powerful |
17 |
>> than a Chevy Sonic hatchback when it comes to hauling huge loads. But |
18 |
>> for someoneone who merely wants to zip out to the supermarket and buy a |
19 |
>> week's groceries, the hatchback is much more appropriate. |
20 |
>> |
21 |
>> Similarly, PulseAudio may be better at handling complex situations |
22 |
>> like you describe. The yelling and screaming you're hearing are from |
23 |
>> the 99% of people whose setups are not complex enough to justify |
24 |
>> PulseAudio. Making 100% of setups more complex in order to handle the |
25 |
>> 1% of edge cases is simply wrong. |
26 |
>> |
27 |
> |
28 |
> The sad thing is, I've not infrequently wound up with sound systems that |
29 |
> were *too* complex for PulseAudio to handle. At least, they were too |
30 |
> complex for the configuration interfaces available, and documentation |
31 |
> for how to do things more precisely (without writing code) was not |
32 |
> forthcoming. |
33 |
> |
34 |
> Here's a scenario exactly as I was dealing with it around 2008: |
35 |
> |
36 |
> Dodo was a combination HTPC/desktop box.[1] It had five displays and |
37 |
> three audio interfaces attached to it. Four of the displays sat on my |
38 |
> desk, one of the displays was a 32" 720p TV that served as the home |
39 |
> theater screen.[2] The machine was sometimes used in both roles at once. |
40 |
> |
41 |
> The three audio interfaces were: |
42 |
> |
43 |
> 1) The onboard audio, which I sometimes used while using the box as a |
44 |
> workstation. |
45 |
> 2) A USB audio device, which I used if I was chilling on the couch and |
46 |
> needed localized audio |
47 |
> 3) A professional audio interface (I forget what, now) that fed my |
48 |
> receiver as well as a crossover that built an LFE channel. |
49 |
> |
50 |
> PA kinda worked in this scenario, up until I physically interacted with |
51 |
> the USB audio device. If I plugged into that, *everything* would |
52 |
> suddenly route through the USB audio device, despite my careful routing |
53 |
> of different applications to different audio sources. |
54 |
> |
55 |
|
56 |
Probably no longer needed, but this is done by a default pulseaudio |
57 |
module, module-switch-on-connect, which is installed by default on |
58 |
Ubuntu. |
59 |
|
60 |
In /etc/pulse/default.pa, there would be a line |
61 |
load-module module-switch-on-connect |
62 |
|
63 |
that would do this. If disabled, you keep your routing after connects. |
64 |
No nice gui for configuring it as far as I can tell, though. |
65 |
|
66 |
> If I'd learned to use JACK, things probably would have been easier...but |
67 |
> I was using Ubuntu,[3] everything seemed designed around leveraging PA, |
68 |
> and I hadn't learned to discard fancy desktop environments yet. |
69 |
> |
70 |
> You know the sad thing, though? ALSA would support that configuration |
71 |
> very well, too. It has enough internal routing and mixing logic that |
72 |
> it'd work. |
73 |
> |
74 |
> |
75 |
> [1] It was also the home gateway router, too, but that's another |
76 |
> story...and not much of one. |
77 |
> [2] Incidentally, this was the same setup where I'd successfully mixed |
78 |
> ATI and nVidia graphics hardware. I used the nvidia proprietary drivers |
79 |
> and the open-source support for ATI...which admittedly wasn't much. But |
80 |
> that's another story. |
81 |
> [3] I wasn't consistently using Gentoo yet. That rather relates to the |
82 |
> machine doubling as the network gateway...[4] |
83 |
> [4] No, I wouldn't do a setup this complicated as one machine as a |
84 |
> keystone in the network. At least, not again. |
85 |
> |
86 |
|
87 |
|
88 |
|
89 |
-- |
90 |
This email is: [ ] actionable [ ] fyi [ ] social |
91 |
Response needed: [ ] yes [ ] up to you [ ] no |
92 |
Time-sensitive: [ ] immediate [ ] soon [ ] none |