Sennheiser GSX 1000/1200: only one subdevice exposed by Pulse & incorrect channel mapping
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pulseaudio (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Similar to the Steelseries Arctis headphones, these sound "cards" present as two output devices, one intended for voice chat and one for everything else. As a result they also need a special profile.
But there's another complication. They also have hardware HRTF that requires no special driver logic; instead, the "everything else" output pretends to be 7.1, and simply applies the HRTF to the streams sent by the host. However, the channel mappings picked up by ALSA are wrong -- the rear speakers and center/LFE are swapped.
I know, technically this is two bugs, but they have the same fix which is impractical to separate. I'm attaching a "sennheiser-
ATTRS{idVendor}
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.2
ProcVersionSign
Uname: Linux 4.18.0-16-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
/dev/snd/
CurrentDesktop: ubuntu:GNOME
Date: Sat Mar 23 23:09:21 2019
InstallationDate: Installed on 2018-09-12 (193 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
TERM=xterm-
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/07/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2004
dmi.board.
dmi.board.name: H87M-E
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: ASUS MB
dmi.product.name: All Series
dmi.product.sku: All
dmi.product.
dmi.sys.vendor: ASUS
modified.
modified.
mtime.conffile.
mtime.conffile.
Status changed to 'Confirmed' because the bug affects multiple users.