From: alexm0n@gmail.com
On Thu, 16 Jan 2025 19:49:35 -0000 (UTC), Rich wrote:
> Marco Moock wrote:
>> On 16.01.2025 13:45 Uhr root wrote:
>>
>>> As far as pulseaudio, I can get sound on the machine I am writing now.
>>> I only ventured into pulseaudio in hopes that it might solve the sound
>>> problem on the other machine. After 5 hours I know I never want
>>> anything to do with pulseaudio, or as I believe its relative systemd.
>>
>> Alsa has several restrictions. IIRC only one sound output to one
>> device, so they can block each other. I use Pulseaudio and it works
>> fine.
>
> ALSA has no such restriction.
>
> Some hardware has that restriction, in which case unless one configures
> Alsa to do mixing in the driver, multiple simultaneous outputs will
> block each other.
>
> But on hardware that provides a hardware mixer, ALSA will not block
> simultaneous outputs, they just get mixed together.
https://knowyourmeme.com/memes/ackchyually-actually-guy
It's pretty easy to verify, but instead you provided nothing of value lol
For example:
https://wiki.flightgear.org/Linux_software_audio_mixing_with_FlightGear
Reading and following the "Audio mixing what?" section, in particular.
The point is moot though. I'd recommend against him configuring ALSA any
further other than reverting what he's done. It's not going to be
beneficial in the long run if asound.conf gets overwritten when running
slackpkg, or he moves hardware around and none of his custom shortcuts
with random parameters work anymore, etc. Unless you'll be here to help,
of course. :)
In all likelihood he just has to revert the changes to asound.conf and
then set the default output device in pavucontrol.. and remove the command
line parameters from mpv, chrome, et al.
--- SoupGate-DOS v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
