System Audio bleeding into Mic Input

Support Audio
, ,
1

System Information:

  • hardware: Asus F16 with core 5 210 and 4050
  • OS: Manjaro Linux (GNOME)
  • Audio Server: PipeWire (pipewire-pulse, wireplumber)
  • Hardware: Havit Fuxi-H3 Headset (via 3.5mm TRRS Combo Jack)
  • Audio Codec: Realtek ALC256

The Problem:
I am experiencing a persistent audio leakage (crosstalk) issue where system audio is being captured as microphone input. This happens across various applications (e.g., Discord, WhatsApp Web).

Key Observations (The “Selective” Behavior):
The issue exhibits a specific behavior: audio originating from inside the application itself (e.g., a YouTube video played inside a browser tab while in a Discord call) is not leaked, likely due to internal WebRTC echo cancellation. However, whenever I play audio from an external application (like a standalone music player), that audio immediately leaks into my mic input.

Troubleshooting already performed:

  • pavucontrol: Confirmed no “Monitor” sources are selected for input. The recording apps are pointed directly to the Headset Microphone.
  • alsamixer: Verified all channels. There are no “Loopback” or “Stereo Mix” options enabled, and Mic Boost is set to minimum.
  • Setup: Verified that the headset is correctly recognized as an Analog Stereo Duplex device in GNOME.

What I am looking for:
I suspect this is an impedance/crosstalk issue at the hardware/driver level common to the ALC256 codec. I am reaching out to see if anyone has faced this exact “selective” leakage scenario before:

  1. Has anyone successfully mitigated this specific ALC256 crosstalk issue on Manjaro/Arch using modprobe parameters or specific pin-mapping overrides?
  2. Since this seems to be a hardware-level bleed that bypasses standard software settings, has anyone implemented a global “set-and-forget” echo cancellation in PipeWire that successfully subtracts system output from all input streams?

I have ruled out basic GUI misconfigurations (alsamixer/pavucontrol), so I am specifically looking for kernel-level or advanced PipeWire/WirePlumber configurations to resolve this.

Any insights or recommended model= overrides for the ALC256 would be greatly appreciated.

wpctl status 
> wpctl status
PipeWire 'pipewire-0' [1.6.5, gabrigas@cicada2106, cookie:2520646804]
 └─ Clients:
        32. WirePlumber                         [1.6.5, gabrigas@cicada2106, pid:4175]
        37. pipewire                            [1.6.5, gabrigas@cicada2106, pid:4177]
        38. GNOME Volume Control Media Keys     [1.6.5, gabrigas@cicada2106, pid:3993]
        47. WirePlumber [export]                [1.6.5, gabrigas@cicada2106, pid:4175]
        69. gnome-shell                         [1.6.5, gabrigas@cicada2106, pid:3852]
        70. GNOME Shell Volume Control          [1.6.5, gabrigas@cicada2106, pid:3852]
        73. xdg-desktop-portal                  [1.6.5, gabrigas@cicada2106, pid:4190]
        74. Brave input                         [1.6.5, gabrigas@cicada2106, pid:7342]
        75. Mutter                              [1.6.5, gabrigas@cicada2106, pid:3852]
        76. WEBRTC VoiceEngine                  [1.6.5, gabrigas@cicada2106, pid:9049]
        77. WEBRTC VoiceEngine                  [1.6.5, gabrigas@cicada2106, pid:9049]
        78. Chromium input                      [1.6.5, gabrigas@cicada2106, pid:9119]
        90. Chromium input                      [1.6.5, gabrigas@cicada2106, pid:12556]
        93. GNOME Settings                      [1.6.5, gabrigas@cicada2106, pid:12606]
       117. GNOME Settings                      [1.6.5, gabrigas@cicada2106, pid:12606]
       154. wpctl                               [1.6.5, gabrigas@cicada2106, pid:14955]
       162. Brave                               [1.6.5, gabrigas@cicada2106, pid:7342]

Audio
 ├─ Devices:
 │      48. AD107 High Definition Audio Controller [alsa]
 │      50. Built-in Audio                      [alsa]
 │  
 ├─ Sinks:
 │  *   45. Built-in Audio Analog Stereo        [vol: 0.68]
 │  
 ├─ Sources:
 │  *   44. Built-in Audio Analog Stereo        [vol: 0.42]
 │  
 ├─ Filters:
 │  
 └─ Streams:
       163. Brave                                                       
            164. output_FL       > ALC256 Analog:playback_FL	[active]
            165. output_FR       > ALC256 Analog:playback_FR	[active]
Settings
 └─ Default Configured Devices:
         0. Audio/Sink    bluez_output.00_09_24_56_09_A5.1
         1. Audio/Source  alsa_input.pci-0000_00_1f.3.analog-stereo
2

Please post more information about audio devices detected in ALSA

sudo alsa-info.sh --upload

User manual for Fuxi-H3 Headset states it can be connected using either:

  • 2.4GHz Wireless Mode (for PC/Laptop/PlayStation)
  • Bluetooth Mode (for Mobile Devices/Laptops with Bluetooth)
  • 3.5mm Wired Mode (for Consoles/Devices with 3.5mm Jack)
    microphone functionality may vary by device.
  • USB-C Wired Mode (for PC/Laptop)

The headset jack might be using a different wiring standard to the laptop jack
Understanding 3.5mm headset compatibility: CTIA vs OMTP standards | Inbertec
this might be resolved by using an adaptor to swap two of the TRRS connections,
or use the USB wired connection that is unlikely to have a similar crosstalk problem.

1 Like
3

Thank you for the guidance. Here is the requested ALSA information:

https://alsa-project.org/db/?f=30b1e97ae360e722c9f8ec9266b330b7261c7fc2

Regarding the 3.5mm connection, I am going to test the headset using the USB-C wired connection as you recommended to rule out any potential wiring or crosstalk issues. I will report back once I have tested that configuration.

1 Like
4

Sorry, but we need the whole link, otherwise it’s useless.

As you probably can’t yet post full links, as a new member, you could post the URL enclosed with backticks, so it looks like this: link to site.

When you have been more active on the Forum, you will be able to post links, etc. directly. :wink:

5

ALSA data for ASUS TUF Gaming F16 FX607VUR_FX607VU shows there are 2 jack-retask overrides in place for both audio devices

!!PCI Soundcards installed in the system
!!--------------------------------------

0000:00:1f.3 Audio device: Intel Corporation Raptor Lake-P/U/H cAVS

0000:01:00.1 Audio device: NVIDIA Corporation AD107 High Definition Audio Controller 

!!ALSA/HDA dmesg
!!--------------

[    5.940587] snd_hda_intel 0000:00:1f.3: Applying patch firmware 'hda-jack-retask.fw'

[    5.943170] snd_hda_intel 0000:01:00.1: Applying patch firmware 'hda-jack-retask.fw'

I suggest you remove these unless they have been added for a specific known reason:

  1. Run hdajackretask with root privileges: sudo hdajackackretask

  2. Click Remove boot override for both audio devices

  3. Shutdown and restart system after a short delay (cold-boot)

  4. Run sudo alsa-info.sh --upload again to check overrides are no longer present

6

I’ve seen similar behavior caused by monitor audio, USB headsets, or virtual audio devices being selected as inputs without realizing it. It might be worth double-checking the active input source in PulseAudio/PipeWire and testing with a different headset or mic to rule out hardware-related crosstalk.

7

Original post includes data from wpctl showing pipewire-pulse default sink and source:

Settings
 └─ Default Configured Devices:
         0. Audio/Sink    bluez_output.00_09_24_56_09_A5.1
         1. Audio/Source  alsa_input.pci-0000_00_1f.3.analog-stereo