Unfortunately, it is nowhere as straightforward as it may seem, as strings change between releases, as do sane value ranges.
Peter Clifton <email address hidden> wrote:
>Yes, the alsactl workaround (and patched kernel) fixes the issue.
>
>Your last comment suggests that it might be useful to compare a
>description of the saved asound.state (what property knobs it lists),
>with those from the currently detected card. Whether they are compatible
>ought to be fairly straightforward to ascertain.
>
>--
>No audio HP 6730b
>https://bugs.launchpad.net/bugs/315971
>You received this bug notification because you are a member of Ubuntu
>Audio Team, which is subscribed to pulseaudio in ubuntu.
Unfortunately, it is nowhere as straightforward as it may seem, as strings change between releases, as do sane value ranges.
Peter Clifton <email address hidden> wrote:
>Yes, the alsactl workaround (and patched kernel) fixes the issue. /bugs.launchpad .net/bugs/ 315971
>
>Your last comment suggests that it might be useful to compare a
>description of the saved asound.state (what property knobs it lists),
>with those from the currently detected card. Whether they are compatible
>ought to be fairly straightforward to ascertain.
>
>--
>No audio HP 6730b
>https:/
>You received this bug notification because you are a member of Ubuntu
>Audio Team, which is subscribed to pulseaudio in ubuntu.