| 1 |
On Sun, Jun 22, 2014 at 12:53 PM, Mick <michaelkintzios@×××××.com> wrote: |
| 2 |
> The skype website says that alsa is no longer supported without pulseaudio in |
| 3 |
> their freshly cut Microsoft-owned code. Why is then the pulseaudio flag |
| 4 |
> provided in portage, if without audio skype would lose its core functionality |
| 5 |
> - i.e. making voice calls? I guess someone may only use it for IM chat, but |
| 6 |
> that I would think is an edge use case. |
| 7 |
|
| 8 |
I imagine that is the answer. If they give the option to disable it, |
| 9 |
then Gentoo is likely to provide it, since we live for edge use cases. |
| 10 |
:) |
| 11 |
|
| 12 |
> |
| 13 |
> it seems awfully complicated to me, for something which for my purposes would |
| 14 |
> be just a new 'alsamixer'. :p |
| 15 |
|
| 16 |
It certainly is. One of these days I'll get around to migrating to |
| 17 |
it. For the simple case of one sound device with one application |
| 18 |
playing at a time alsa works just fine. Where it breaks down is when |
| 19 |
you have three sound devices and four applications using them, and you |
| 20 |
want to plug in a USB headset and have it just "do the right thing." |
| 21 |
That isn't all that uncommon a scenario on the desktop (I use a USB |
| 22 |
headset for work on a Windows laptop all the time). Once you build |
| 23 |
all the framework to make that work, then it makes sense to just use |
| 24 |
it for everything, which is why Pulseaudio has basically taken over |
| 25 |
the Linux desktop. |
| 26 |
|
| 27 |
Rich |
Archives