NoiseTorch icon indicating copy to clipboard operation
NoiseTorch copied to clipboard

Inconsistent crunchy microphone on discord

Open pfych opened this issue 3 years ago • 6 comments

Sometimes when starting noise-torch and joining a discord call the mic sounds bit-crushed & crunchy. Not sure how to go about debugging this since I don't know much about Linux audio. Here's some outputs that might help?

noisetorch -l

Sources:
        Device Name: Monitor of Arctis Pro Wireless Game
        Device ID: alsa_output.usb-SteelSeries_Arctis_Pro_Wireless-00.stereo-game.monitor

        Device Name: Arctis Pro Wireless Chat
        Device ID: alsa_input.usb-SteelSeries_Arctis_Pro_Wireless-00.mono-chat

Sinks:
        Device Name: Arctis Pro Wireless Game
        Device ID: alsa_output.usb-SteelSeries_Arctis_Pro_Wireless-00.stereo-game

uname -a

Linux desktop 5.14.9-arch2-1 #1 SMP PREEMPT Fri, 01 Oct 2021 19:03:20 +0000 x86_64 GNU/Linux

noisetorch --log

2021/10/06 19:17:31 Application starting. Version: 0.11.4 (archlinux)
2021/10/06 19:17:31 CAP_SYS_RESOURCE: true
2021/10/06 19:17:31 Checking if config needs to be initialized
2021/10/06 19:17:31 Resolved $XDG_CONFIG_HOME to '/home/pfych/.config'
2021/10/06 19:17:31 Wrote temp librnnoise to: /tmp/librnnoise-3795672139.so
2021/10/06 19:17:31 Resolved $XDG_CONFIG_HOME to '/home/pfych/.config'
2021/10/06 19:17:31 Audioserver package name: pulseaudio
2021/10/06 19:17:31 Audioserver package version: 15.0
2021/10/06 19:17:31 Detected PulseAudio
2021/10/06 19:17:31 couldn't parse server version, regexp didn't match version: 15.0
2021/10/06 19:17:31 Getting caps for: /usr/bin/noisetorch
2021/10/06 19:17:31 Audioserver package name: pulseaudio
2021/10/06 19:17:31 Audioserver package version: 15.0
2021/10/06 19:17:31 Detected PulseAudio
2021/10/06 19:17:31 couldn't parse server version, regexp didn't match version: 15.0
2021/10/06 19:17:31 Connected to audio server. Server name ''
2021/10/06 19:17:31 Output alsa_output.usb-SteelSeries_Arctis_Pro_Wireless-00.stereo-game, {Index:0 Name:alsa_output.usb-SteelSeries_Arctis_Pro_Wireless-00.stereo-game Description:Arctis Pro Wireless Game SampleSpec:{Format:3 Channels:2 Rate:44100} ChannelMap:[1 2] ModuleIndex:8 Cvolume:[65536 65536] Muted:false MonitorSourceIndex:0 MonitorSourceName:alsa_output.usb-SteelSeries_Arctis_Pro_Wireless-00.stereo-game.monitor Latency:44274 Driver:module-alsa-card.c Flags:183 PropList:map[alsa.card:3 alsa.card_name:Arctis Pro Wireless alsa.class:generic alsa.device:1 alsa.driver_name:snd_usb_audio alsa.id:USB Audio alsa.long_card_name:SteelSeries Arctis Pro Wireless at usb-0000:0d:00.3-4.3, full speed alsa.name:USB Audio #1 alsa.resolution_bits:16 alsa.subclass:generic-mix alsa.subdevice:0 alsa.subdevice_name:subdevice #0 device.access_mode:mmap+timer device.api:alsa device.buffering.buffer_size:352800 device.buffering.fragment_size:176400 device.bus:usb device.bus_path:pci-0000:0d:00.3-usb-0:4.3:1.0 device.class:sound device.description:Arctis Pro Wireless Game device.icon_name:audio-card-usb device.product.id:1294 device.product.name:Arctis Pro Wireless device.profile.description:Game device.profile.name:stereo-game device.serial:SteelSeries_Arctis_Pro_Wireless device.string:hw:3,1,0 device.vendor.id:1038 device.vendor.name:SteelSeries ApS module-udev-detect.discovered:1 sysfs.path:/devices/pci0000:00/0000:00:08.1/0000:0d:00.3/usb5/5-4/5-4.3/5-4.3:1.0/sound/card3 udev.id:usb-SteelSeries_Arctis_Pro_Wireless-00] RequestedLatency:26000 BaseVolume:65536 SinkState:0 NVolumeSteps:65537 CardIndex:2 Ports:[{Name:usb-gaming-headset-output-stereo Description:Headphones Pririty:0 Available:0}] ActivePortName:usb-gaming-headset-output-stereo Formats:[{Encoding:1 PropList:map[]}]}

Restarting both programs usually resolves the issue after a couple tries.

pfych avatar Oct 06 '21 08:10 pfych

can you post a screenshot of the GUI?

lawl avatar Oct 06 '21 08:10 lawl

iamge

pfych avatar Oct 06 '21 09:10 pfych

This all looks perfectly normal to me. Though it's the second weird issue in connection with discord, see: #173

lawl avatar Oct 06 '21 18:10 lawl

i had an issue connecting to discord after using wireplumber

Taza53 avatar Oct 30 '21 11:10 Taza53

@Taza53 If you're using WirePlumber, a related issue has been created there, which you might want to look at: https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/115

machitgarha avatar Nov 23 '21 09:11 machitgarha

I began having this issue as well, before it was working really well. What's odd is that listening to it using the local "mic test" feature sounds fine to me.

devmattrick avatar Jan 12 '22 06:01 devmattrick

Checking https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/115, this bug has been fixed upstream. Closing.

TheDukeofErl avatar Oct 10 '23 02:10 TheDukeofErl

Checking https://gitlab.freedesktop.org/pipewire/wireplumber/-/issues/115, this bug has been fixed upstream. Closing.

Nice find

AXDOOMER avatar Oct 10 '23 03:10 AXDOOMER