<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Headset jack partially not recognized as connected at boot"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103482#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Headset jack partially not recognized as connected at boot"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103482">bug 103482</a>
from <span class="vcard"><a class="email" href="mailto:carlo@caione.org" title="Carlo Caione <carlo@caione.org>"> <span class="fn">Carlo Caione</span></a>
</span></b>
<pre>(In reply to Tanu Kaskinen from <a href="show_bug.cgi?id=103482#c5">comment #5</a>)
<span class="quote">> Ok, both output ports have the same priority. The UCM configuration could
> provide the priority, but your UCM configuration doesn't do that. I don't
> think it's a good idea to use UCM as the priority authority anyway, because
> if the system has both UCM and non-UCM cards, the priorities between the
> cards wouldn't be comparable (and I doubt that the priorities between two
> different UCM cards would be comparable either). Instead, PulseAudio should
> determine the priority based on the device types. AFAIK, UCM doesn't
> currently provide device type information, so that's something to fix in
> UCM. As a workaround, PulseAudio could guess the device type from the device
> name.</span >
Given how many UCM cards are around I wonder why this is not something already
fixed / known.
<span class="quote">> I don't know why the Handset Microphone port has higher priority than the
> default 100. Does your UCM config have any differences to what's currently
> in alsa-lib master branch?</span >
No, I'm using exactly the same UCM config. Weird.
<span class="quote">> Regarding the simultaneous output to both speakers and headphones: I suppose
> this happens only after boot? The UCM config looks like it has appropriate
> mute commands in the DisableSequence sections for both devices. I believe
> the disable sequences aren't executed during boot, however, so the default
> mixer configuration in bytcr-rt5651.conf should be changed to mute all
> outputs.</span >
Yeah, you are right. Fixed that at least :)</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>