From: GitHub issues - edited <github@alsa-project.org>
To: alsa-devel@alsa-project.org
Subject: MPG X570S EDGE MAX WIFI compatibility
Date: Fri, 26 Aug 2022 21:45:43 +0200 (CEST) [thread overview]
Message-ID: <20220826194543.E8EC2F80431@alsa1.perex.cz> (raw)
In-Reply-To: <1661543137567871094-webhooks-bot@alsa-project.org>
alsa-project/alsa-ucm-conf issue #172 was edited from yhojann-cl:
Please, add `0db0:151f` to `realtek-alc4080` chip compatibility in MPG X570S EDGE MAX WIFI motherboard:
```
$ lsusb | grep 0db0
Bus 001 Device 003: ID 0db0:151f Micro Star International USB Audio
```
In `ucm2/USB-Audio/USB-Audio.conf` add `151f` to regex of `0db0`:
```
Regex "USB((0b05:(1996|1a2[07]))|(0db0:(1feb|419c|a073|151f)))"
```
My Motherboard is MSI X570S and output audio works fine but:
- Motherboard microphone plug is not work.
- Frontal microphone plug is not work.
- When change output from gnome settings to hdmi audio does not work, the audio continues to play in the plug and not in the monitor.
- When I change the input or output from digital to analog or sinput it does not change at all.
- The strangest thing is that the microphone input captures the audio that is heard in the system as if it were the output, audacious records the audio from the desktop when it tries to monitor the microphone.
- When plugging or unplugging the microphone, the system detects this change and tries to change the audio input automatically, but it does not capture the microphone and the desktop continues to be heard.
- When plug headphone in frontal plug the gnome setting change automaticaly to the headphone item, but the sound play in speakers, not in headphone.
- On Audacity when capture Alsa + `USB Audio: #2 (hw: 1,2)` works fine!, but can not set on gnome settings.
My alsa data: http://alsa-project.org/db/?f=df4d1f6c126260eabc5f159e64cff37efa064a38
Issue URL : https://github.com/alsa-project/alsa-ucm-conf/issues/172
Repository URL: https://github.com/alsa-project/alsa-ucm-conf
next parent reply other threads:[~2022-08-26 19:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1661543137567871094-webhooks-bot@alsa-project.org>
2022-08-26 19:45 ` GitHub issues - edited [this message]
[not found] <1661543756558514118-webhooks-bot@alsa-project.org>
2022-08-26 19:56 ` MPG X570S EDGE MAX WIFI compatibility GitHub issues - edited
[not found] <1661543211363966942-webhooks-bot@alsa-project.org>
2022-08-26 19:46 ` GitHub issues - edited
[not found] <1661543095703939915-webhooks-bot@alsa-project.org>
2022-08-26 19:45 ` GitHub issues - edited
[not found] <1655526261252573967-webhooks-bot@alsa-project.org>
2022-06-18 4:24 ` GitHub issues - edited
[not found] <1655525231867194891-webhooks-bot@alsa-project.org>
2022-06-18 4:07 ` GitHub issues - opened
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220826194543.E8EC2F80431@alsa1.perex.cz \
--to=github@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox