1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<TITLE> [Mageia-dev] [changelog] cauldron core/release sound-scripts-0.61-2.mga2
</TITLE>
<LINK REL="Index" HREF="index.html" >
<LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bchangelog%5D%20cauldron%20core/release%0A%09sound-scripts-0.61-2.mga2&In-Reply-To=%3CCAONrEtYsVKdo6ifSwVfweZNy9tc4VX8Umdg9Bj0Pyp3%3Dv-3O_A%40mail.gmail.com%3E">
<META NAME="robots" CONTENT="index,nofollow">
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<LINK REL="Previous" HREF="008238.html">
<LINK REL="Next" HREF="008241.html">
</HEAD>
<BODY BGCOLOR="#ffffff">
<H1>[Mageia-dev] [changelog] cauldron core/release sound-scripts-0.61-2.mga2</H1>
<B>Thierry Vignaud</B>
<A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20%5Bchangelog%5D%20cauldron%20core/release%0A%09sound-scripts-0.61-2.mga2&In-Reply-To=%3CCAONrEtYsVKdo6ifSwVfweZNy9tc4VX8Umdg9Bj0Pyp3%3Dv-3O_A%40mail.gmail.com%3E"
TITLE="[Mageia-dev] [changelog] cauldron core/release sound-scripts-0.61-2.mga2">thierry.vignaud at gmail.com
</A><BR>
<I>Mon Sep 19 16:27:32 CEST 2011</I>
<P><UL>
<LI>Previous message: <A HREF="008238.html">[Mageia-dev] [changelog] cauldron core/release sound-scripts-0.61-2.mga2
</A></li>
<LI>Next message: <A HREF="008241.html">[Mageia-dev] [changelog] cauldron core/release sound-scripts-0.61-2.mga2
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#8239">[ date ]</a>
<a href="thread.html#8239">[ thread ]</a>
<a href="subject.html#8239">[ subject ]</a>
<a href="author.html#8239">[ author ]</a>
</LI>
</UL>
<HR>
<!--beginarticle-->
<PRE>On 19 September 2011 16:14, Colin Guthrie <<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">mageia at colin.guthr.ie</A>> wrote:
>>>>><i> Did you fixed the war against webcam another way?
</I>>>>><i>
</I>>>>><i> Is this a problem of webcam mics not working if they are present during
</I>>>>><i> boot? If not, can you remember the problem better?
</I>>>>><i>
</I>>>>><i> If so, no I've not fixed, but will find an official way that we can
</I>>>>><i> submit upstream.
</I>>>><i>
</I>>>><i> Whoops, it seems this conversation went off list accidentally.
</I>>>><i>
</I>>>><i> TV clarified that the problem the snd-usb-audio modprobe rule solved was
</I>>>><i> that of webcams getting the card0 slot on boot and pushing the normal,
</I>>>><i> built in audio system to card1.
</I>>>><i>
</I>>>><i> As this problem attempts to resolve the underlying limitations of alsa
</I>>>><i> (not preserving the audio device order) in a generic way (specific
</I>>>><i> index= arguments could be added to your own specific hardware to solve
</I>>>><i> it also), and considering that device order really shouldn't matter when
</I>>>><i> PulseAudio is used (it has it's own built in system for determining the
</I>>>><i> "priority" of devices when a first boot with a new user is encountered
</I>>>><i> so that the correct defaults will be picked on first boot and there
</I>>>><i> after it's the user's choice), I'm not really inclined to attempt to fix
</I>>>><i> this "bug".
</I>>>><i>
</I>>>><i> If people feel super strongly about it I can look into it, but I think
</I>>>><i> it's really a matter of "tough love" for the non-PA case if it means we
</I>>>><i> have to put in lots of crazy work arounds like this.
</I>>>><i>
</I>>>><i> Opinions welcome.
</I>>><i>
</I>>><i> Not all people use PA.
</I>>><i> We even have options in draksound in order to disable it...
</I>>><i> Hence we must still support the case were PA isn't around...
</I>><i>
</I>><i> Yeah, but by the same token, turning off PA is obviously not part of the
</I>><i> recommended config.
</I>><i>
</I>><i> If people turn off PA, they have to expect a less integrated solution.
</I>><i>
</I>><i> And it's not as if things don't work. It's just that their systems would
</I>><i> require a little more configuration than before. But in turning off PA,
</I>><i> that's pretty much what they are signing up for anyway.
</I>><i>
</I>><i> Hence my desire not to fix this "bug" when it's already fixed in the
</I>><i> default setup.
</I>><i>
</I>><i> But if this is a show stopper for more people, I will see what we can do.
</I>
What about reverting a change :-) ?
</PRE>
<!--endarticle-->
<HR>
<P><UL>
<!--threads-->
<LI>Previous message: <A HREF="008238.html">[Mageia-dev] [changelog] cauldron core/release sound-scripts-0.61-2.mga2
</A></li>
<LI>Next message: <A HREF="008241.html">[Mageia-dev] [changelog] cauldron core/release sound-scripts-0.61-2.mga2
</A></li>
<LI> <B>Messages sorted by:</B>
<a href="date.html#8239">[ date ]</a>
<a href="thread.html#8239">[ thread ]</a>
<a href="subject.html#8239">[ subject ]</a>
<a href="author.html#8239">[ author ]</a>
</LI>
</UL>
<hr>
<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
mailing list</a><br>
</body></html>
|
