| 1 |
On Sun, Apr 26, 2020 at 1:06 PM Jorge Almeida <jjalmeida@×××××.com> wrote: |
| 2 |
> |
| 3 |
> On Sun, Apr 26, 2020 at 8:34 PM Mark Knecht <markknecht@×××××.com> wrote: |
| 4 |
<SNIP> |
| 5 |
> > I'll investigate what I can do sending files by hand. However on the |
| 6 |
USB only machine all the internal sound card hardware is blacklisted so |
| 7 |
modules aren't loaded. I don't know that I want to upset the environment on |
| 8 |
that machine very much but a bit more about this at the bottom of this post. |
| 9 |
> > |
| 10 |
> No, please don't bother. I only mentioned because I thought you might |
| 11 |
> know it out of hand. I'll search documentation about pulseaudio, if I |
| 12 |
> can find it. It occurred to me that it would be an acceptable setup if |
| 13 |
> pulseaudio could be coaxed into managing just the USB card (as hw |
| 14 |
> card, not as virtual card) and leave the HD audio alone. I would use |
| 15 |
> the USB to voice chat and the MB card to everything else. (I would |
| 16 |
> have to buy another pair of headphones, but maybe headphones for |
| 17 |
> speech-only would not add too much clutter to the desk...) |
| 18 |
> |
| 19 |
|
| 20 |
Some reading I did about people having problems similar to yours with |
| 21 |
discord and zoom suggested that some of these aps are compiled to __only__ |
| 22 |
support pulseaudio and then they supply it if it's not already on the |
| 23 |
system. Even though you don't build it using a specific portage entry in |
| 24 |
your world file doesn't mean it's not on your system if it was buried in |
| 25 |
the zoom/discord code. |
| 26 |
|
| 27 |
1) Run 'pulseaudio' at the command line to check |
| 28 |
|
| 29 |
2) If it's there run pavucontrol at the command line to get started |
| 30 |
configuring it. pulseaudio can, on paper anyway, mix multiple audio signals |
| 31 |
on the fly and can (I think) send the mixed audio to multiple sound cards. |
| 32 |
|
| 33 |
Any 'real' pulseaudio build can be configured to not 'autospawn' via it's |
| 34 |
config files. That way people who don't want it, or think they don't, can |
| 35 |
have it on the system but run it only when they need it and shut it down |
| 36 |
when they don't. I did that for awhile. That sort of setup might be more |
| 37 |
acceptable for your needs and would allow you to build it and manage it |
| 38 |
yourself. I don't know. Something to consider. On Gentoo I wouldn't be |
| 39 |
fearful of building it and trying it out. Not sure what flags you'd want to |
| 40 |
enable or whether you'll end up in some sort of dependency hell as can |
| 41 |
happen with this sort of stuff on Gentoo. |
| 42 |
|
| 43 |
Cheers, |
| 44 |
Mark |
Archives