8 May
2022
8 May
'22
8:30 a.m.
On Sunday 08 May 2022 01:23:12 deloptes wrote:
Nick Koretsky wrote:
I didn't do anything with it. My default is simply no action, to leave things
unchanged from the previous state. I copied over settings from my desktop
computer (which was running Devuan Beowulf 32-bit) to this new laptop
(running Devuan Chimaera 64-bit). I made no other changes.
Moreover, my settings sometimes would change (it seems) from one reboot to the
next, even though I had done nothing. Sometimes everything would run fine on
alsa alone, without pulse; then I would need pulse; then alsa wouldn't work
at all; then some things worked only with pulse, others only with alsa; then,
the last straw, no sound at all in any videos.
It is because it hasn't been working right that I now must resort to these
command-line tricks. Otherwise I wouldn't bother.
Bill
Erm... My post explain how to run pulse alongside
with alsa without them
conflicting and breaking thing. It only do something if pulse is running.
If pulse is running, but you get no sound in default-to-pulse apps, then
you probably put wrong device name in module-alsa-sink/source lines.
Pls post output of aplay -l and aplay -L
I am using only standard configuration on the desktop with systemd+pulse
I had no issue ever. I wonder why you are messing up with configurations
and making things worse.
A user should usually not do anything in command line and although I am
experienced user I avoid this and I think because of this I have no issues.