From: Jorge Almeida <jjalmeida@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] ALSA wizard...
Date: Sun, 26 Apr 2020 21:49:52 +0100 [thread overview]
Message-ID: <CAKpSnpL7tDfU3hQBzeXL7-fWP3rgXrjsPDDZoUhkUtGKZB7fEQ@mail.gmail.com> (raw)
In-Reply-To: <CAK2H+eeaJBxq7fQatvN0tn-kveu34SAk3E+3JykSM-AVwYDWTg@mail.gmail.com>
On Sun, Apr 26, 2020 at 9:23 PM Mark Knecht <markknecht@gmail.com> wrote:
>
>
>
> On Sun, Apr 26, 2020 at 1:06 PM Jorge Almeida <jjalmeida@gmail.com> wrote:
> >
> Some reading I did about people having problems similar to yours with discord and zoom suggested that some of these aps are compiled to __only__ support pulseaudio and then they supply it if it's not already on the system. Even though you don't build it using a specific portage entry in your world file doesn't mean it's not on your system if it was buried in the zoom/discord code.
Hummm... But then discord would not complain about not being able to
initialize audio?
>
> 1) Run 'pulseaudio' at the command line to check
There is no such thing (if it were hidden in some app it would not be
in the PATH, anyway)
And I regularly check what's cooking, with "ps axf".
> Any 'real' pulseaudio build can be configured to not 'autospawn' via it's config files. That way people who don't want it, or think they don't, can have it on the system but run it only when they need it and shut it down when they don't. I did that for awhile. That sort of setup might be more acceptable for your needs and would allow you to build it and manage it yourself. I don't know. Something to consider. On Gentoo I wouldn't be fearful of building it and trying it out. Not sure what flags you'd want to enable or whether you'll end up in some sort of dependency hell as can happen with this sort of stuff on Gentoo.
Yes, stuff to learn, if possible. (But dependency hell is a definite
possibility, not because Gentoo but due to the mindset that lurks
beneath pulseaudio & friends)
>
Cheers
Jorge
next prev parent reply other threads:[~2020-04-26 20:50 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
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 [this message]
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=CAKpSnpL7tDfU3hQBzeXL7-fWP3rgXrjsPDDZoUhkUtGKZB7fEQ@mail.gmail.com \
--to=jjalmeida@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