According to This Posting, I had written that hypothetically, it might make some sense for me to set up ‘
JACK‘ as the back-end, by which ‘
PulseAudio‘ sends its sound output, full-time. As opposed to the notion not making sense, to allow a few scripts to do so temporarily, that are being run by the ‘
Well there is still a reason, why this might not be so. Doing so would be consistent, with setting up a Debian system completely according to our own preferences, and then if something does not work, we are up to our own devices to fix it.
My laptop ‘Klystron’ is a Kanotix / Spitfire system, which is also Debian-based, but in which the exact configuration has been done for me, by the Kanotix team, from their Live Disk (which can actually be written onto a USB-Key). This means that there is an advantage to me, in keeping certain configuration details conform to what the Kanotix people prescribed. If I did run into trouble with it, they would have some chance of maybe suggesting solutions, but only on the assumption that mine is still functioning within their parameters.
The way those parameters are, the current back-end to the
PulseAudio sound server is displayed in the GUI as being “
gstreamer“, and yet good compatibility with all things
ALSA is maintained…
If I was to reconfigure my computers completely, for example because I wanted to change them to use the ‘
GNOME desktop manager’ for instance, instead of ‘
KDE‘, then the Kanotix team would say ‘Sorry, we are not familiar with the details of your system anymore. Therefore, we cannot help you.’
Yet, more generally, Debian allows deep changes to a configuration.