I am running pulseaudio 12.2 For me the volume is properly restored but it does take PA about two seconds to respond to my keyboard control the first time I press them after boot. So keyboard control does have a small regression for me. If these issues are there maybe it would be wise to drop the UCM profile until they are fixed because there weren't and real issues in the old situation. I can test other things if needed so let me know. René On 31-10-2018 13:02, Takashi Iwai wrote: > On Tue, 30 Oct 2018 16:55:31 +0100, > Ren9 Santing wrote: >> As a user I do think the ucm profile works as intended with the latest >> git. Pulseaudio is now able to use the headphone and speaker output of >> the docking station at the same time and I wasn't able to do that >> before. Also for me in KDE the volume/mute controls are working as >> intended. But if the profile gives more issues for other users I can >> confirm that my normal usecase also works fine without the profile on my >> setup. > Thanks, that's interesting. I rethought of dropping the UCM profile > just because of some complaints about PA behavior. > > Is the volume restored properly by PA? The reporter told that the > lack of priority values lead to the failure of the volume-restore > behavior. This could be relatively easily fixed in UCM profile side, > we may just add the priority values. > > Another complaint was about the lack of the keyboard control. It was > supposed to be due to the lack of the hardware flag exposed from PA. > And, PA UCM parser doesn't seem to take the volume / mute definitions > even if defined in UCM profile, so far. This could be fixed in PA > side as well. > > The last complaint was about the missing icon; this might be tricky, > maybe PA could guess the more appropriate icon from the UCM stream > name string... > > In anyway, I'd be glad if we keep UCM profile as an option, too. > > Which version of PA are you using, BTW? > > > Takashi > >> René >> >> On 30-10-18 16:45, Takashi Iwai wrote: >>> On Tue, 30 Oct 2018 10:48:26 +0100, >>> Takashi Iwai wrote: >>>> On Tue, 30 Oct 2018 10:41:10 +0100, >>>> Ren9 Santing wrote: >>>>> I totally missed that commit sorry for the redundant bug report. Yes it >>>>> works with the updated conf file. >>>> Good to hear, thanks for quick testing! >>>> >>>> Jaroslav, what do you think of 1.1.7.1 release addressing regression? >>>> IIRC, we had an issue with alsa-plugins as well. >>> Or maybe we should drop this UCM profile. >>> >>> Since PA seems addressing the issue by itself via its own specific >>> profile, we may leave the things to PA alone. >>> >>> I hoped that UCM profile support can improve the things in a cleaner >>> way, but PA-UCM integration isn't fully done (e.g. the volume / mute >>> controls seem ignored), and UCM overrides the PA profile, it can be >>> more harm than good as of now. >>> >>> >>> Takashi >>> >>>> Takashi >>>> >>>>> Thanks, >>>>> >>>>> René Santing >>>>> >>>>> On 30-10-18 10:35, Takashi Iwai wrote: >>>>>> On Tue, 30 Oct 2018 10:10:07 +0100, >>>>>> Ren9 Santing wrote: >>>>>>> Hello Alsa developers, >>>>>>> >>>>>>> I would like to file a bug report about the Dell-WD15-Dock. This dock >>>>>>> stopped working for me on archlinux/kde. The device was not picked up at >>>>>>> all by pulse audio after some updates I installed last week. >>>>>>> By trial and error I found out it was caused by the ucm profile that was >>>>>>> added in alsa-lib 1.1.7. >>>>>> Could you try the alsa-lib git repo? The fix is already included. >>>>>> >>>>>> >>>>>> thanks, >>>>>> >>>>>> Takashi _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
