Summary: | phonon should associate "sound keys" with the active sound card | ||
---|---|---|---|
Product: | [Applications] kmix | Reporter: | m.wege |
Component: | general | Assignee: | Matthias Kretz <kretz> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | esken |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Unspecified | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
m.wege
2009-07-18 23:40:30 UTC
Surely you can use multiple soundcards. The Phonon configuration allows to define which soundcard to use for different categories like Music, Desktop, Notification or Chat. Could you explain what you mean in detail with "In that case in should be configurable.". You can already define which channel in which soundcard is affected by the volume keys. Just use the context menu on the dock icon to select the Master channel. Hi Christian, when I select my external soundcard as master channel, the sound keys of my laptop do not work for the external soundcard. If this feature does not work for me, may it is distro-related or specific for my thinkpad. What do I mean with "In that case in should be configurable." -> Orginally I would like to see that when I select my external soundcard as priority resource in phonon, that it would be automatically master channel and the keys of the laptop get bound to this sound card. By the above sentence I meant, that I do not know technically if it is possible to have more than one souncard active. If this is the case, the above wish should be configurable, just in case some other users want it different. Thanks for the quick answer. But as explained in comment #1, the Master keys are already configurable. And I cannot trivially follow Phonon changes, as there can be more than one active card. Is something missing there? Oh, and I just noted, this bug report is a duplicate of bug 181652. I'll mark this as a duplicate. Please report further input there. *** This bug has been marked as a duplicate of bug 181652 *** |