Horrible mic feedback loop.

seth · 2022-05-18 15:52:45

But this is w/ both mics off - do you have some sound artifacts at this point?
alsamixer operates on the pipewire device - stop the pipewire-pulse.service and/or use "alsamixer -c2"

pvpmartins · 2022-05-22 05:03:39

Strange. I can’t find pipewire-audio unit on systemctl while on multi-user.target.

pvpmartins · 2022-05-22 05:16:08

Here's alsamixer -c2

https://i.imgur.com/Pbn4NcQ.png

pvpmartins · 2022-05-22 05:17:59

pvpmartins wrote:

Strange. I can’t find pipewire-audio unit on systemctl while on multi-user.target.

nor on graphical.target

seth · 2022-05-22 05:33:11

pvpmartins wrote:

Here's alsamixer -c2
https://i.imgur.com/Pbn4NcQ.png

That's the proper card. Now play w/ the mic settings until you get or get rid of the artifacts.

https://wiki.archlinux.org/title/PipeWire#Installation wrote:

Pipewire uses systemd/User for management of the server and automatic socket activation.

pvpmartins · 2022-05-25 04:37:33

seth wrote:

pvpmartins wrote:
Here's alsamixer -c2
https://i.imgur.com/Pbn4NcQ.png
That's the proper card. Now play w/ the mic settings until you get or get rid of the artifacts.
https://wiki.archlinux.org/title/PipeWire#Installation wrote:
Pipewire uses systemd/User for management of the server and automatic socket activation.

Am I suppose to do it on multi-user.target?

pvpmartins · 2022-05-25 05:19:16

I've downloaded qpwgraph... here's a screenshot of my system:

https://i.imgur.com/AAYTD9J.png

seth · 2022-05-25 05:22:17

Yes - that was the point of the last 15 posts…
Edit:

Am I suppose to do it on multi-user.target?

Last edited by seth (2022-05-25 05:55:26)

seth · 2022-05-25 05:52:34

What does that have to do with anything?
It's now twenty posts and you've not stated whether the issue exists on the multi-user.target and whether you can trigger it w/ some mixer setting - for all we know this could be a bug in discord ffs.

Edit:

I've downloaded qpwgraph... here's a screenshot of my system:

Last edited by seth (2022-05-25 05:55:44)

pvpmartins · 2022-05-25 14:11:55

well... I will just reinstall arch. Thank you

pvpmartins · 2022-05-25 14:17:56

I don't know to how verify the sound without an app like discord, OBS... Since on multi-user.target I can't access those, I don't know how to verify any sound artifact while I'm on it.
That's also something you have not explained to me. How am I suppose to check the sound while on multi-user.target?

Last edited by pvpmartins (2022-05-25 14:22:01)

seth · 2022-05-25 14:40:50

Yes. I. Have.
Open the alsamixer on the card and start enabling the microphones and boosters and see at which point and if you get the audible artifact.

But at least you (hopefully…) accidentally established that this isn't something permanent but depending on you using some electron implemention (I guess, since discord and OBS are both "implemented" as wrappers around chromium)

pvpmartins · 2022-05-25 15:20:56

So each time I change any parameter on alsamixer, i should boot the machine on GUI right after? That's what sounds weird to me.
You see? I don't know how to check the sound without those apps I mentioned.

Last edited by pvpmartins (2022-05-25 15:22:32)

pvpmartins · 2022-05-25 15:24:54

seth wrote:

Yes. I. Have.
Open the alsamixer on the card and start enabling the microphones and boosters and see at which point and if you get the audible artifact.
But at least you (hopefully…) accidentally established that this isn't something permanent but depending on you using some electron implemention (I guess, since discord and OBS are both "implemented" as wrappers around chromium)

You got it wrong. It IS permanent. I also got on that google meet, and anywhere I got mic and speakers on

Last edited by pvpmartins (2022-05-25 15:27:43)

pvpmartins · 2022-05-25 15:32:33

seth wrote:

You don't need to "test the sound".
Again: are there any audio artifacts in the basic condition of the multi-user.target?
If not: run "alsamixer" and activate the mic(s) and there boosters and possibly also other input/output devices there until the artifact shows up.
Alternatively post
amixer -c2
pactl list sources
pactl list source-outputs
*while* "testing" the sound causes the artifact.
Information that you gather while the artifacts aren't present are worthless.

You said this to me... I don't know how to procedure after I'm in alsamixer in multi-user.target. Ok, I understand that I can change some parameters like rear mic boost, levels... but so what??? no matter how I change those, it doesn't solve my problem.

How could I know if I have any sound artifact in the basic condition of the multi.user.target?

What do you mean by sound artifact? Noise, hum... Right?

seth · 2022-05-25 16:12:13

no matter how I change those, it doesn't solve my problem.

They're not supposed to "solve" anything but reveal the cause.

How could I know if I have any sound artifact in the basic condition of the multi.user.target?

Is there a permanent "horrible mic feedback" in that situation?

progandy · 2022-05-25 16:26:30

While booted to multi-user.target you should be able to record your microphone with e.g. "arecord" to an audio file, then listen to it.
Some commands are here: https://wiki.archlinux.org/title/Advanc … hone_input

If pulseaudio or pipewire is running you can also try "parecord".

Last edited by progandy (2022-05-25 16:27:52)

pvpmartins · 2022-05-25 19:04:31

progandy wrote:

While booted to multi-user.target you should be able to record your microphone with e.g. "arecord" to an audio file, then listen to it.
Some commands are here: https://wiki.archlinux.org/title/Advanc … hone_input
If pulseaudio or pipewire is running you can also try "parecord".

Thank you very much.

pvpmartins · 2022-05-25 19:08:05

Is there a permanent "horrible mic feedback" in that situation?

That's the thing. I don't know. But progandy did finally explain how to do it.

Do you understand my issue now??

Last edited by pvpmartins (2022-05-25 19:11:12)

seth · 2022-05-25 19:24:50

What do you mean "you don't know" - is the "feedback" (we'll put that into quotes) not audible across the speakers? It only show up in recordings??

progandy · 2022-05-25 19:35:11

Edit: Sorry, wrong thread.
I'm not sure, but maybe the microphone is disabled when nothing is trying to record?

Last edited by progandy (2022-05-25 19:37:35)

seth · 2022-05-25 20:01:56

That's why he shall enable the microphone(s, there're two…) from alsamixer - if the artifacts only show up in sound recordings (let alone from specific clients) it's rather not a feedback loop and could be simply sonme encoder artifact.
(Except if PA/pipewire ends up redirecting some output into the mic but not the speakers, which, yeah: don't use pipewire… but we'll at least know where to look and where not)

pvpmartins · 2022-05-26 03:48:44

when I am on multi-user.target and enter alsamixer -c2, I don't know how to proceed. Once I'm on the multi-user.target I DON'T KNOW HOW TO CHECK THE SOUND.

That is the whole point right?? you want me there so there aint any other potential service to cofound the root error. Ok. But now then what do I do? Just messing around with alsamixer without any sound return doesn't seem to help.

Man, how can you not understand what I am telling you?!

Last edited by pvpmartins (2022-05-26 04:03:02)

seth · 2022-05-26 05:20:04

You can use the mixer w/ the keyboard. "m" toggles mute, up & down in/decrease volume, F3/4 select playback and recording devices and escape quits.
You check the sound w/ your ears - except:
Please clarify whether the "horrible mic feedback" only appears in the discord recording or whether you can actually hear that immediately.

Edit: a "horrible mic feedback" is caused by the sound input feeding into the output and from there back into the input - just activating a microphone input would in the worst of cases immediately cause this noise.

Last edited by seth (2022-05-26 05:23:18)

pvpmartins · 2022-05-28 20:01:27

seth wrote:

You check the sound w/ your ears.

Ohh... My bad. Is this package on the AUR?

seth wrote:

Please clarify whether the "horrible mic feedback" only appears in the discord recording or whether you can actually hear that immediately.

I can hear it immediately. or should I say anyone who is in a call with me.

Last edited by pvpmartins (2022-05-28 20:06:48)

Arch Linux

#26 2022-05-18 15:52:45

Re: Horrible mic feedback loop.

#27 2022-05-22 05:03:39

Re: Horrible mic feedback loop.

#28 2022-05-22 05:16:08

Re: Horrible mic feedback loop.

#29 2022-05-22 05:17:59

Re: Horrible mic feedback loop.

#30 2022-05-22 05:33:11

Re: Horrible mic feedback loop.

#31 2022-05-25 04:37:33

Re: Horrible mic feedback loop.

#32 2022-05-25 05:19:16

Re: Horrible mic feedback loop.

#33 2022-05-25 05:22:17

Re: Horrible mic feedback loop.

#34 2022-05-25 05:52:34

Re: Horrible mic feedback loop.

#35 2022-05-25 14:11:55

Re: Horrible mic feedback loop.

#36 2022-05-25 14:17:56

Re: Horrible mic feedback loop.

#37 2022-05-25 14:40:50

Re: Horrible mic feedback loop.

#38 2022-05-25 15:20:56

Re: Horrible mic feedback loop.

#39 2022-05-25 15:24:54

Re: Horrible mic feedback loop.

#40 2022-05-25 15:32:33

Re: Horrible mic feedback loop.

#41 2022-05-25 16:12:13

Re: Horrible mic feedback loop.

#42 2022-05-25 16:26:30

Re: Horrible mic feedback loop.

#43 2022-05-25 19:04:31

Re: Horrible mic feedback loop.

#44 2022-05-25 19:08:05

Re: Horrible mic feedback loop.

#45 2022-05-25 19:24:50

Re: Horrible mic feedback loop.

#46 2022-05-25 19:35:11

Re: Horrible mic feedback loop.

#47 2022-05-25 20:01:56

Re: Horrible mic feedback loop.

#48 2022-05-26 03:48:44

Re: Horrible mic feedback loop.

#49 2022-05-26 05:20:04

Re: Horrible mic feedback loop.

#50 2022-05-28 20:01:27

Re: Horrible mic feedback loop.

Board footer