Linux

55288 readers

1938 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 6 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

How can we combine two audio recording inputs (mics) into one audio input source in Manjaro? (sh.itjust.works)

submitted 1 day ago by Robochocobo@sh.itjust.works to c/linux@lemmy.ml

25 comments fedilink hide all child comments

My partner and I are running Manjaro and very new to it. Trying to switch as much as possible over to daily use with Manjaro. We have pipewire, not pulseaudio

We record multiple times a week on OBS, and my partner and I are in the same room. We have two mics side by side both inputs going into my PC. Linux, and therefore OBS, are recognizing the two mic inputs separately as you might expect.

OBS can set up both of these separate inputs, but the issue is we're having significant problems with echo and the noise suppression/noise gates are not sufficient.

This was not an issue on windows, where we used Voicemeeter to combine our inputs into one mic for OBS. I am looking to emulate that on Linux to see if it solves our problems.

We have tried a mic merge sink, but it creates an OUTPUT device, not an input device.

you are viewing a single comment's thread
view the rest of the comments

[–] iAmTheTot@sh.itjust.works 0 points 1 day ago* (last edited 1 day ago) (1 children)

Voicemeteer also seems to be a mystery to y’all.

I don't appreciate your condescending tone, tbh. If you are not interested in helping us, you can stop replying.

Voicemeteer was taking our two mics and turning them into a single source that we could then feed to Discord and OBS. That should be it. I'm not completely sure it wasn't applying some other kind of filters, but I don't think it was, that's not what it's supposed to do. So let's say we have Mic Source 1 and Mic Source 2. Voicemeteer took the input from both of those and combined them into Combined Source. We then pointed OBS and Discord to use Combined Source. That's all we're trying to achieve on Linux right now.

Krisp is a feature of Discord. It is available on Linux. We have used this post to accomplish what we want to do with Discord, but this solution does not work for OBS. On Discord, others on call do not report hearing this echo effect. It only appears in OBS recording when we use Mic Source 1 and Mic Source 2. I am not convinced that Krisp is a factor here, as we have tested with it off, but I felt it was worth mentioning. It seems to have confused the situation though.

[–] LandedGentry@lemmy.zip 2 points 1 day ago* (last edited 1 day ago)

It’s not condescending - you have said in multiple comments that it may be doing more than you realize, which means it is a mystery to you. I am being clinical and focused about this, not condescending. I am actually talking to you as if you know what I am talking about. If youwould like me to change my tone that is fine, but I’m in the business of trying to help people solve audio problems. Too much handholding generally leads to confusion.

I’m not completely sure it wasn’t applying other kinds of filters

Again, you keep saying you don’t fully know what it was doing. So it behooves you to look it up. This is not me being condescending or patronizing, this is me telling you what you need to do after you literally said you don’t know what it was or was not doing. You need to isolate every single thing you were doing before, every single thing you are doing now, and understand how each step was/is impacting your audio. This is troubleshooting 101. Until you do that, nobody can help you. Unless you want to completely depend on luck or start from scratch.

You came here looking for technical answers, I have been doing nothing but offering you technical solutions. We are clearly missing information, whether you know it or not, and I’m doing the best with what I have. I’m sorry this is frustrating for you, I have been there many many times and I get it. But I am not your enemy. I am someone with almost 20 years of audio production experience trying to assist. For free.