From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 15CF3138350 for ; Sat, 25 Apr 2020 23:16:11 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id CCD47E08F4; Sat, 25 Apr 2020 23:16:03 +0000 (UTC) Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 827E2E08DA for ; Sat, 25 Apr 2020 23:16:03 +0000 (UTC) Received: by mail-qt1-x830.google.com with SMTP id x8so11223638qtp.13 for ; Sat, 25 Apr 2020 16:16:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=bK8BdWd1cZZfR3OYhbXEGAhgUpGMcN57tUqnIBc15xY=; b=veDLd3/waj4AKvKyZyTbjfTH8JTly/dVFcCvurWZ3ocK2JX17w13YOAWiJ/LLLRtKy O49Vo9mBA5DVArk1lTuK2YvcKq2RjhjaAGhk0cLnPS506fxyBI+bSCgX5HNMvk1g9lG4 OoZGKBuKFOqsey9wTXaD98abI6ryaBzizKZy1IMVenQoWXcNNVIH6KYqFfsl0DPMIcRp k4fnevvf1Yk+A1zDFOvV+498SMJJVpW8v5+AnWjGdr3FobEZpmDZBP7Hg1EzOyw72jxq OKN1QEv+u0WVPxnw9/nJ9FHnFaGW0ZmXJ0CmRQifbSMEZtqNb4lE0nGjQ6Tji6nEOxFk rzmQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=bK8BdWd1cZZfR3OYhbXEGAhgUpGMcN57tUqnIBc15xY=; b=Ss2BNvNWbKqRzA5u72oEC/20R0SykIkHcCchSFuKX6osEIK3Lp8bk+qiLmA7pReG3Y N02UChhVpAerhQTXRjm2xrUnROk1qxhXt5KhZjErefZFQNPovOpLO05HlgATVRz6FNSI pji14Sh8A6O37CYyHXzb2wsi6JavNr1P5V3Kg9+G7O9yF8uKLYXWzEoXGXYjK8vw2pzA d5/A7Jmfahk7suYqztH+frO8B57AO5rbYROAR+IBn2aAgzZrnlH4jgPrLNgsQ1iLtaDH Tz93dSwRupzZIzrGFSF391q3j9rkJiOF2/bu4IcoiMXvdb8WnnsuzldCgonNdBL0s0II 9AcQ== X-Gm-Message-State: AGi0PuY1zORcPeN4JC6OFwAz+gXg+QOsrh8qlwCdV5tZT63ojeao+DcX uG7JLyQSQQNl87Sk5P+6aJf2VZ/orNuUb+/DBQbfUm+i07c= X-Google-Smtp-Source: APiQypIJhEh1FCs0vSc/rltHjT0+OMUVhsrrjREamX3Qc9F4ztmoZJb3X0XuKemTPpeq89z+NYlMGzjSRZjmQYO1oJo= X-Received: by 2002:ac8:7606:: with SMTP id t6mr15535613qtq.331.1587856562293; Sat, 25 Apr 2020 16:16:02 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 References: <3298791.iIbC2pHGDl@lenovo.localdomain> <1840287.usQuhbGJ8B@lenovo.localdomain> In-Reply-To: From: Mark Knecht Date: Sat, 25 Apr 2020 16:15:50 -0700 Message-ID: Subject: Re: [gentoo-user] ALSA wizard... To: Gentoo User Content-Type: multipart/alternative; boundary="0000000000005990e005a425aaf1" X-Archives-Salt: 2634934a-eea7-426d-8e09-21d3f8e17a7c X-Archives-Hash: c59b64475304a5b6785979e8fe31112a --0000000000005990e005a425aaf1 Content-Type: text/plain; charset="UTF-8" > One word: AHA! (It makes a lot of difference, knowing what one is doing!) > This is the explanation the interface should come with, or at least > they should have a site with a simple diagram. > > Yes, I can hear sound with the headphones connected to the headphone > out in the interface, as well as with the headphones connected to the > RCA output, via an amplifier. (I modified .asoundrc to make the USB > card the default; not a permanent solution but manageable) > > I had understood the purpose of the direct monitor, but I thought > wrongly that the headphone output had no other purpose by itself. > > OK, I tried both discord and slack with this setup. I can't hear the > other side. The other side can hear me on slack, not on discord. > You sound happier in this post. I hope we're making headway. Could you post back a view of things at this point? ls /proc/asound cat /proc/asound/cards cat /proc/asound/devices cat /proc/asound/hwdep cat /proc/asound/pcm If you run alsamixer what card is it showing you when you first go in? Not knowing these applications I'm at a distance trying to make suitable suggestions. I'm fairly sure you won't like the next one... How do you feel about building Alsa as modules instead of building it into the kernel? When using modules you can blacklist other sound cards (the MB audio stuff for instance) and you get a little more visibility into what's is at least loaded. That way we could, at least as a test, run your setup as a USB only system. If at that point you can record mix audio in something like Audacity and play Audacity and Youtube through the Behringer then, I would think, we would have determined that this is an application issue. While it shouldn't matter I assume you tried slack and discord with direct monitoring turned off and on? I would expect that off is the right way for an application like these but it makes sense to at least press the button to see if it changes anything. I'm really intrigued to see if we can figure this out. - Mark --0000000000005990e005a425aaf1 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


> One word: AHA! (It makes a lot of difference,= knowing what one is doing!)
> This is the explanation the interface = should come with, or at least
> they should have a site with a simple= diagram.
>
> Yes, I can hear sound with the headphones connect= ed to the headphone
> out in the interface, as well as with the headp= hones connected to the
> RCA output, via an amplifier. (I modified .a= soundrc to make the USB
> card the default; not a permanent solution = but manageable)
>
> I had understood the purpose of the direct = monitor, but I thought
> wrongly that the headphone output had no oth= er purpose by itself.
>
> OK, I tried both discord and slack wi= th this setup. I can't hear the
> other side. The other side can = hear me on slack, not on discord.
>

You sound happier in= this post. I hope we're making headway. Could you post back a view of = things at this point?

ls /proc/asound
<= div>
cat /proc/asound/cards
cat /proc/asound= /devices
cat /proc/asound/hwdep
cat /pr= oc/asound/pcm

If you r= un alsamixer what card is it showing you when you first go in?
Not knowing these applications I'm at a distance trying to= make suitable suggestions. I'm fairly sure you won't like the next= one...

How do you feel about building Alsa as mod= ules instead of building it into the kernel? When using modules you can bla= cklist other sound cards (the MB audio stuff for instance) and you get a li= ttle more visibility into what's is at least loaded. That way we could,= at least as a test, run your setup as a USB only system. If at that point = you can record mix audio in something like Audacity and play Audacity and Y= outube through the Behringer then, I would think, we would have determined = that this is an application issue.

While it shoul= dn't matter I assume you tried slack and discord with direct monitoring= turned off and on? I would expect that off is the right way for an applica= tion like these but it makes sense to at least press the button to see if i= t changes anything.

I'm really intrigued to se= e if we can figure this out.

- Mark
--0000000000005990e005a425aaf1--