From: Mark Knecht <markknecht@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] ALSA wizard...
Date: Sat, 25 Apr 2020 06:19:09 -0700 [thread overview]
Message-ID: <CAK2H+eey3PWpirHanSP0jSiqfFadmSoemCOD0PkEKACJm6Wzpg@mail.gmail.com> (raw)
In-Reply-To: <CAKpSnpLvLb-p2UzSGHU14sEVyQxi5HoH1hk0K+xD15Vs-aAa6w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3302 bytes --]
<SNIP>
> > >
https://www.amazon.de/dp/B00EK1OTZC/ref=pe_3044161_189395811_TE_SCE_dp_1
> >
> > OK, that device is pretty simple. If you set this device as the default
Alsa device can you get simple audio, from YouTube for example, out through
the headphone jack? We know the mic input works. If both of those work then
what does discord do?
>
> I'm lost here. The headphone jack in the interface is just a monitor.
> I don't think there's any connection with the headphone jack in the
> motherboard? (I can't test it anyway with my headphones---different
> jack sizes)
>
I understand the jack size difference. Your MB jack is 3.5mm, the headphone
jack on the Behringer is 1/4". All the headphones I've purchased for years
came with an adapter to plug into 1/4" jack but if your didn't they can be
purchased at Amazon or general stereo/TV type stores. (Best Buy as an
example in the U.S.) Search for "3.5mm to 1/4 adapter".
I'll explain the headphone monitor function in a moment. You are correct
that the headphone jack on the Behringer has nothing to do with the
headphone jack on the computer. The Behringer is a complete sound card with
2 inputs and 2 output at the end of a USB cable. It has phono jack outputs
on the back which would allow you to hook it to your stereo inputs to hear
computer audio. In that sense it's no different than a CD player or tape
deck. To use the outputs on the back would simply come down to telling
Linux I want to use the Behringer USB device as my sound card and all sound
would be router there. Once the audio is correctly going to your stereo you
should also hear the audio over the headphone jack.
The monitor function associated with the headphones is different on cards
like this. Notice that the switch says "Direct Monitor". Imagine that I am
recording a song. I already have some of it recorded, say drums, bass and
piano. Now I want to record vocals so (wearing headphones so I can hear
what I'm supposed to sing along with) I sing into the microphone but there
is latency in the system. The vocal gets converted to digital by an
internal A/D converter, sent down the USB cable, routed to the recording
application - in Linux lets say that's Ardour. Ardour records it onto disk
but it also sends my vocal back to the Behringer so I hear myself in the
headphones. The probably is that my vocal is delayed by 25mS or more. It
sounds out of time and I'm confused. It sounds like an echo.
Look at the diagram here to see what I'm trying to explain:
https://manual.ardour.org/synchronization/latency-and-latency-compensation/
Direct monitoring changes the signal path in the picture on the Ardour
page. It still sends my vocal down the USB cable and Ardour still records
it but it __ALSO__ sends my vocal __DIRECTLY__ from the mic to the
headphones skipping the whole digital path in the picture. There is no
delay. I hear myself in time with the music. It feels natural and I perform
my part of the song brilliantly and go on to make millions of dollars.
(Well, maybe...)
Direct monitoring probably won't matter i your application because the
real-time nature of what you're speaking won't be effected very much and
probably discord or zoom won't send it back out to the card, but only send
it to the people you are meeting with.
Hope this helps,
Mark
[-- Attachment #2: Type: text/html, Size: 3887 bytes --]
next prev parent reply other threads:[~2020-04-25 13:19 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 21:57 [gentoo-user] ALSA wizard Jorge Almeida
2020-04-23 0:42 ` Mark Knecht
2020-04-23 7:03 ` Jorge Almeida
2020-04-23 13:37 ` Mark Knecht
2020-04-23 18:50 ` Jorge Almeida
2020-04-23 8:19 ` Michael
2020-04-23 9:46 ` Jorge Almeida
2020-04-23 16:53 ` Michael
2020-04-23 19:01 ` Jorge Almeida
2020-04-23 20:10 ` Mark Knecht
2020-04-23 21:01 ` Jorge Almeida
2020-04-23 20:38 ` Matt Connell (Gmail)
2020-04-23 21:07 ` Jorge Almeida
2020-04-23 21:27 ` Matt Connell (Gmail)
2020-04-24 10:38 ` Michael
2020-04-24 11:13 ` Jorge Almeida
2020-04-24 13:05 ` Michael
2020-04-24 13:35 ` Jorge Almeida
2020-04-24 16:26 ` Mark Knecht
2020-04-24 17:03 ` Jorge Almeida
2020-04-24 17:10 ` Mark Knecht
2020-04-24 17:20 ` Jorge Almeida
2020-04-24 18:07 ` Mark Knecht
2020-04-24 22:22 ` Jorge Almeida
2020-04-24 22:46 ` Mark Knecht
2020-04-24 23:16 ` Jorge Almeida
2020-04-25 0:18 ` Mark Knecht
2020-04-25 8:08 ` Jorge Almeida
2020-04-25 13:19 ` Mark Knecht [this message]
2020-04-25 21:38 ` Jorge Almeida
2020-04-25 23:15 ` Mark Knecht
2020-04-26 0:07 ` Jorge Almeida
2020-04-26 12:30 ` Jorge Almeida
2020-04-26 16:58 ` Mark Knecht
2020-04-26 19:08 ` Jorge Almeida
2020-04-26 19:28 ` problems with slack and zoom: Was: " Jack
2020-04-26 22:22 ` Jorge Almeida
2020-04-26 23:03 ` Jack
2020-04-26 23:42 ` Jorge Almeida
2020-04-27 15:26 ` Jack
2020-04-27 16:47 ` Jorge Almeida
2020-04-27 18:17 ` Jack
2020-04-28 10:32 ` [gentoo-user] Re: problems with slack and zoom: Was: " Nuno Silva
2020-04-28 11:09 ` Jorge Almeida
2020-04-28 11:56 ` Michael
2020-04-28 12:02 ` Jorge Almeida
2020-04-26 19:34 ` [gentoo-user] " Mark Knecht
2020-04-26 20:05 ` Jorge Almeida
2020-04-26 20:23 ` Mark Knecht
2020-04-26 20:49 ` Jorge Almeida
2020-04-26 21:26 ` Mark Knecht
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=CAK2H+eey3PWpirHanSP0jSiqfFadmSoemCOD0PkEKACJm6Wzpg@mail.gmail.com \
--to=markknecht@gmail.com \
--cc=gentoo-user@lists.gentoo.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