You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's hard to say when it happened, but it used to be different on some earlier version of Ubuntu, with PulseAudio instead of PipeWire, and with some earlier version of headsetcontrol. So I have no idea which component is responsible, but I figured this issue tracker is the most reasonable place to get started.
It used to be the case that with headsetcontrol -s 128 the feedback got quite loud - I'd hear my breathing, rubbing of the chord against my shirt, etc. Of course, the voice would come out of the headphones louder than what I'd hear without the headphones
Now with the the same command I get barely any feedback. There's still a difference between 128 and 0, of course, but almost insignificant.
How should I approach debugging and, hopefully, fixing it so that 128 is again the "almost too loud to be useful" level?
Headset Name
Logitech G PRO X
On which OS does the problem happen?
Linux
Device information
Detailed Device Information
Device Found
VendorID: 0x046d
ProductID: 0x0aaa
path: /dev/hidraw5
serial_number: 000000000000
Manufacturer: Logitech
Product: PRO X
Interface: 3
Usage-Page: 0xc Usageid: 0x1
Device Found
VendorID: 0x046d
ProductID: 0x0aaa
path: /dev/hidraw5
serial_number: 000000000000
Manufacturer: Logitech
Product: PRO X
Interface: 3
Usage-Page: 0xc Usageid: 0x36
Device Found
VendorID: 0x046d
ProductID: 0x0aaa
path: /dev/hidraw5
serial_number: 000000000000
Manufacturer: Logitech
Product: PRO X
Interface: 3
Usage-Page: 0xb Usageid: 0x5
Device Found
VendorID: 0x046d
ProductID: 0x0aaa
path: /dev/hidraw5
serial_number: 000000000000
Manufacturer: Logitech
Product: PRO X
Interface: 3
Usage-Page: 0xff99 Usageid: 0x1
Device Found
VendorID: 0x046d
ProductID: 0x0aaa
path: /dev/hidraw5
serial_number: 000000000000
Manufacturer: Logitech
Product: PRO X
Interface: 3
Usage-Page: 0xff99 Usageid: 0xff00
Device Found
VendorID: 0x046d
ProductID: 0x0aaa
path: /dev/hidraw5
serial_number: 000000000000
Manufacturer: Logitech
Product: PRO X
Interface: 3
Usage-Page: 0xff99 Usageid: 0x20
Device Found
VendorID: 0x046d
ProductID: 0x0aaa
path: /dev/hidraw5
serial_number: 000000000000
Manufacturer: Logitech
Product: PRO X
Interface: 3
Usage-Page: 0xff99 Usageid: 0x24
Device Found
VendorID: 0x046d
ProductID: 0x0aaa
path: /dev/hidraw5
serial_number: 000000000000
Manufacturer: Logitech
Product: PRO X
Interface: 3
Usage-Page: 0xff99 Usageid: 0x48
Device Found
VendorID: 0x046d
ProductID: 0x0aaa
path: /dev/hidraw5
serial_number: 000000000000
Manufacturer: Logitech
Product: PRO X
Interface: 3
Usage-Page: 0xff99 Usageid: 0x2b
Device Found
VendorID: 0x046d
ProductID: 0x0aaa
path: /dev/hidraw5
serial_number: 000000000000
Manufacturer: Logitech
Product: PRO X
Interface: 3
Usage-Page: 0xff99 Usageid: 0xff17
Device Found
VendorID: 0x046d
ProductID: 0x0aaa
path: /dev/hidraw5
serial_number: 000000000000
Manufacturer: Logitech
Product: PRO X
Interface: 3
Usage-Page: 0xff43 Usageid: 0x202
The text was updated successfully, but these errors were encountered:
LMAO, my bad - apparently, the friction over my t-shirt has been gradually turning the volume control and I've been compensating by increasing the output volume in my OS.
Description
It's hard to say when it happened, but it used to be different on some earlier version of Ubuntu, with PulseAudio instead of PipeWire, and with some earlier version of
headsetcontrol
. So I have no idea which component is responsible, but I figured this issue tracker is the most reasonable place to get started.It used to be the case that with
headsetcontrol -s 128
the feedback got quite loud - I'd hear my breathing, rubbing of the chord against my shirt, etc. Of course, the voice would come out of the headphones louder than what I'd hear without the headphonesNow with the the same command I get barely any feedback. There's still a difference between
128
and0
, of course, but almost insignificant.How should I approach debugging and, hopefully, fixing it so that
128
is again the "almost too loud to be useful" level?Headset Name
Logitech G PRO X
On which OS does the problem happen?
Linux
Device information
Detailed Device Information
The text was updated successfully, but these errors were encountered: