From: Mark Knecht <markknecht@gmail.com>
To: Gentoo User <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] ALSA wizard...
Date: Fri, 24 Apr 2020 10:10:57 -0700 [thread overview]
Message-ID: <CAK2H+ecPrgQCXzBSYDX39OiZbxLx+4QerdigB2JYvGcRQpkOow@mail.gmail.com> (raw)
In-Reply-To: <CAKpSnpLNU=SRqnxL=8uT8rE9AMpvRPwbCu3FPT1G01Mtmu=3tQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]
On Fri, Apr 24, 2020 at 10:04 AM Jorge Almeida <jjalmeida@gmail.com> wrote:
>
> On Fri, Apr 24, 2020 at 5:27 PM Mark Knecht <markknecht@gmail.com> wrote:
> >
> >
> >
>
> > If it's true that discord is so picky then I wonder if there would
be some value in testing your virtual sound card with some other app to
ensure that at least the basic Alsa needs are being met?
> >
> > https://www.ubuntupit.com/top-20-best-linux-video-conferencing-software/
> >
> Sure, I'll keep looking, but discord seems to come with the best
> features, barring the small detail of being linux-hostile. For
> example, jitsi (the 1st in that list) only supports Chrome and
> Firefox, excluding MacOS users who are not willing to install one of
> these...
>
I __ONLY__ meant for testing purposes. I understand discord is the result
we are working toward. Right now I don't know what the root cause of the
failure is so testing some other app and discovering it works would tell us
the virtual card does what you need in full-duplex real-time mode. However
if we cannot make any app work correctly then we have to work more in the
virtual card part.
Just an idea,
Mark
[-- Attachment #2: Type: text/html, Size: 1539 bytes --]
next prev parent reply other threads:[~2020-04-24 17:11 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 [this message]
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
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+ecPrgQCXzBSYDX39OiZbxLx+4QerdigB2JYvGcRQpkOow@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