On 21-04-08 15:43, Takashi Iwai wrote: > Yeah, I'm indeed very fond of automatic volume setup for desktop > users, too. I don't know whether it's a role of PA. Rather I feel > we'd need to add a feature to alsactl, such as, > % alsactl init > then it'll either initialize or restore the previous setup. > > So, anyway, what we really need is to gather the data for each > available device to initialize to the "sane" state... People were worried about the maintainability of this (proposed as shipped /usr/share/cards/<card>.state files) but I feel this shouldn't be too bad indeed. I'd suggest "alsactl defaults" to just load those "unmuted card defaults" and leave looking for previously saved settings to an init script same as now. Distributions then have full freedom. Is the "id" parameter to modules (and multiple cards with the later ones having an id postfix) a problem for finding the right state file to load? That is, is it a problem for the current <card>.conf files in there? Not sure how that works... Rene. _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
