Attachment 129105 Details for Bug 99479 – fixed headphone path

fixed headphone path

analog-output-headphones.conf (text/plain), 3.32 KB, created by Tanu Kaskinen on 2017-01-23 11:16:34 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Tanu Kaskinen

Created: 2017-01-23 11:16:34 UTC

Size: 3.32 KB

patch

obsolete

># This file is part of PulseAudio.
>#
># PulseAudio is free software; you can redistribute it and/or modify
># it under the terms of the GNU Lesser General Public License as
># published by the Free Software Foundation; either version 2.1 of the
># License, or (at your option) any later version.
>#
># PulseAudio is distributed in the hope that it will be useful, but
># WITHOUT ANY WARRANTY; without even the implied warranty of
># MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
># General Public License for more details.
>#
># You should have received a copy of the GNU Lesser General Public License
># along with PulseAudio; if not, see <http://www.gnu.org/licenses/>.
>
>; Path for mixers that have a 'Headphone' control
>;
>; See analog-output.conf.common for an explanation on the directives
>
>[General]
>priority = 90
>description-key = analog-output-headphones
>
>[Properties]
>device.icon_name = audio-headphones
>
>[Jack Dock Headphone]
>required-any = any
>
>[Jack Dock Headphone Phantom]
>required-any = any
>state.plugged = unknown
>state.unplugged = unknown
>
>[Jack Front Headphone]
>required-any = any
>
>[Jack Front Headphone Phantom]
>required-any = any
>state.plugged = unknown
>state.unplugged = unknown
>
>[Jack Headphone]
>required-any = any
>
>[Jack Headphone Phantom]
>required-any = any
>state.plugged = unknown
>state.unplugged = unknown
>
># This jack can be either a headphone *or* a mic. Used on some ASUS netbooks.
>[Jack Headphone Mic]
>required-any = any
>
>[Element Hardware Master]
>switch = mute
>volume = merge
>override-map.1 = all
>override-map.2 = all-left,all-right
>
>[Element Master]
>switch = mute
>volume = merge
>override-map.1 = all
>override-map.2 = all-left,all-right
>
>[Element Master Mono]
>switch = off
>volume = off
>
>[Element Speaker+LO]
>switch = off
>volume = off
>
>[Element Headphone+LO]
>required-any = any
>switch = mute
>volume = merge
>override-map.1 = all
>override-map.2 = all-left,all-right
>
>[Element Headphone]
>required-any = any
>switch = mute
>volume = merge
>override-map.1 = all
>override-map.2 = all-left,all-right
>
>[Element Headset]
>required-any = any
>switch = mute
>volume = merge
>override-map.1 = all
>override-map.2 = all-left,all-right
>
>[Element Line HP Swap]
>switch = on
>required-any = any
>
># Asus Xonar DX uses the "Front Panel" element to switch output between the
># front and back panel. We treat the front panel output as the headphone path
># and the back panel output as the lineout path.
>[Element Front Panel]
>switch = on
>required-any = any
>
>; This profile path is intended to control the first headphones, not
>; the second headphones. But it should not hurt if we leave the second
>; headphone jack enabled nonetheless.
>[Element Headphone2]
>switch = mute
>volume = zero
>
>[Element Speaker]
>switch = off
>volume = off
>
>[Element Desktop Speaker]
>switch = off
>volume = off
>
>; On some machines Front is actually a part of the Headphone path
>[Element Front]
>switch = mute
>volume = zero
>
>[Element Rear]
>switch = off
>volume = off
>
>[Element Surround]
>switch = off
>volume = off
>
>[Element Side]
>switch = off
>volume = off
>
>[Element Center]
>switch = off
>volume = off
>
>[Element LFE]
>switch = off
>volume = off
>
>[Element Bass Speaker]
>switch = off
>volume = off
>
>[Element Speaker Front]
>switch = off
>volume = off
>
>[Element Speaker Surround]
>switch = off
>volume = off
>
>[Element Speaker Side]
>switch = off
>volume = off
>
>[Element Speaker CLFE]
>switch = off
>volume = off
>
>.include analog-output.conf.common

Actions: View

Attachments on bug 99479: 129078 | 129105 | 129106 | 132648 | 132649

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.