<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<atom:link href="https://dev1galaxy.org/extern.php?action=feed&amp;tid=7427&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / ALSA: Dogmatism and Empiriokritizismus]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=7427</link>
		<description><![CDATA[The most recent posts in ALSA: Dogmatism and Empiriokritizismus.]]></description>
		<lastBuildDate>Fri, 26 Sep 2025 00:30:24 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: ALSA: Dogmatism and Empiriokritizismus]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=58243#p58243</link>
			<description><![CDATA[<p>It was about a technical problem how to toggle ALSA configs with a script.</p><p>The main principle of ALSA design is a sort of &quot;hot-plug&quot;.<br />Today, you do not need to reload ALSA, if you change <strong>.asoundrc</strong><br />Though a media player may (or may not) need to be re-started.</p><p>It is self-evident. If you don&#039;t believe, read Gentoo Wiki and try proposed tests.</p><div class="quotebox"><blockquote><div><p><strong>Gentoo Wiki:</strong><br />Use of <span class="bbc">~/.asoundrc</span> is <strong>immediate</strong> and as long as you are not forcing the use of specific devices in any applications, they either will require a restart <strong>or will begin working immediately.</strong> One of the best tests is to run Chrome, go to YouTube, open a terminal, run mplayer with an audio or video file and see that you do not get an error about audio (such an error might be &#039;Device or resource busy&#039;). <br />_https://wiki.gentoo.org/wiki/ALSA#Sound_card_only_available_for_one_application</p></div></blockquote></div><p>The problem is that ALSA is poorly documented, and, therefore, one has to use the method of trial and error to find the correct solution. However, what is correct today might be wrong tomorrow.</p><p>To foresee changes in the &quot;advanced sound system&quot;, one may need &quot;a deeper level of understanding of ALSA&quot;, or a sort of esoteric knowledge for navigating uncertainty.</p><p>ALSA in user space is a sort of software mixer with plugins, such as <strong>dmix</strong>, <strong>dsnoop</strong>, and the like. Many years ago, ALSA was so buggy that it was necessary to reload ALSA to enable changes in <strong>.asoundrc</strong>. Today, to enable <strong>dmix</strong> or other plugin in <strong>.asoundrc</strong>, you do not need to reload ALSA.</p><p>In 2008, it was necessary to reload ALSA to enable dmix. This problem was fixed in 2009 (or 2010) in a new version of ALSA. In 2010, Ubuntu users were advised to recompile ALSA to fix sound problems, although it was enough to remove pulseaudio. In 2010, Ubuntu users asked questions like this: &quot;Could I remove ALSA, and use PulseAudio instead?&quot; </p><div class="quotebox"><blockquote><div><p><strong>Linux Mint Forums</strong><br />_https://forums.linuxmint.com/viewtopic.php?t=179838</p><p><strong>Remove ALSA, install Pulseaudio</strong></p><p>Post by H.Remedy » Tue Oct 07, 2014 9:13 am</p><p>Can someone please give terminal commands for fully removing ALSA and installing Pulseaudio? :?</p></div></blockquote></div><p>It is very logical: <br />1. If pulseaudio is much better than ALSA, it is reasonable to remove ALSA and install pulseaudio.<br />2. If pulseaudio needs ALSA to work, it cannot be better than ALSA, and, perhaps, is not needed.<br />3. If ALSA can work without pulseaudio, it might be reasonable to remove pulseaudio as an unnecessary fifth wheel.</p><div class="quotebox"><blockquote><div><p>If ALSA is buggy and ill-designed, and the resamplers are crappy, any sort of pulseaudio is doomed to fail, for it is a castle built on sand. It is obvious, but not evident.</p></div></blockquote></div><p>Today, many &quot;computer scientists&quot; firmly believe that Fedora Linux has PipeWire instead of ALSA. It is impossible to convince them that they have ALSA installed and working in their Linux system, because they do not want to know what ALSA is, and how it looks like. They have the gift of faith in the sense that they do not trust their senses and their ability to think. They have a special, extraordinary trust in PipeWire&#039;s promises and a sort of &quot;supernatural ability to believe in the unseen and to act on spiritual truths despite physical evidence to the contrary&quot;. </p><div class="quotebox"><blockquote><div><p>...some audio applications keep the ALSA PCM device open, even when they are not actively streaming any audio, and so it is necessary to close each application before any other can use the device...<br /><span style="color: green"><strong>ALSA provides a solution to this for hardware cards with the &quot;dmix&quot; plugin.</strong></span> That plugin allows multiple open connections, mixes the streams together, then sends the result as a single stream to the hardware device. <br />_https://github-wiki-see.page/m/Arkq/bluez-alsa/wiki/Using-bluealsa-with-dmix</p></div></blockquote></div><p><span style="color: green"><span class="bbu"><strong>dmix</strong> is needed to make ALSA usable.</span> </span></p><div class="quotebox"><blockquote><div><p>When <span style="color: blue">#Software mixing <strong>[dmix]</strong></span> is enabled, ALSA is forced to resample everything to the same frequency (48 kHz by default when supported). By default, it will try to use the speexrate converter to do so, and fallback to low-quality linear interpolation if it is not available. Thus, <span style="color: blue"><strong>if you are getting poor sound quality due to bad resampling,</strong></span> the problem can be solved by simply installing the alsa-plugins package. <br />_https://wiki.archlinux.org/title/Advanced_Linux_Sound_Architecture#High_quality_resampling</p></div></blockquote></div><p>The speexrate converter is also crappy.</p><p>In 2008, Ubuntu was infected with PulseAudio which was a replacement for <strong>dmix</strong> and ESD. PulseAudio was very advanced, but buggy and unusable. ESD was not so buggy. It was usable, and, therefore, it was deprecated. However, it was still&#160; available, and the standard solution for sound problems was to remove PulseAudio and install ESD. The best solution for sound problems was to remove both ALSA and PulseAudio, compile OSS4 and install it.</p><p>NOTE: ESD was created, because <strong>dmix</strong> was buggy and unusable. ESD was buggy, but usable. When most bugs were fixed, it was deprecated (in 2008).</p><div class="quotebox"><blockquote><div><p>[In 2007] the <strong>Enlightened Sound Daemon</strong> (ESD or EsounD) was the sound server for Enlightenment and GNOME. Esound is a small sound daemon for both Linux and UNIX. ESD was created to provide a consistent and simple interface to the audio device, so applications do not need to have different driver support written per architecture. It was also designed to enhance capabilities of audio devices such as allowing more than one application to share an open device. ESD accomplishes these things while remaining transparent to the application, meaning that the application developer can simply provide ESD support and let it do the rest. On top of this, the API is designed to be very similar to the current audio device API, making it easy to port to ESD.<br />ESD will mix the simultaneous audio output of multiple running programs, and output the resulting stream to the sound card.<br />_https://en.wikipedia.org/wiki/Enlightened_Sound_Daemon</p></div></blockquote></div><p>ESD was mostly using ALSA&#039;s built-in OSS emulation (alsa-oss: snd-pcm-oss and snd-seq-oss) which performed much better than native ALSA in 2008. The emulation provided a more stable solution for applications still using the Open Sound System (OSSv.3) API.</p><div class="quotebox"><blockquote><div><p>Horrible sound quality with <strong>dmix</strong> is caused by its poor resampling algorithm which produces noticeable audio distortions.</p></div></blockquote></div><p>In 2008, <strong>dmix</strong> was extremely buggy (and ALSA resamplers have always been crappy). The sound quality was really horrible with <strong>dmix</strong>. This problem was fixed in 2010 with the fftrate ALSA plugin (and with ALSA update).</p><p>ALSA was designed as a universal solution to all problems, but it was so buggy that it was decided to create pulseaudio as a truly advanced solution to all problems. Pipewire was created for a similar reason.</p><p>Today ALSA is not so buggy and even usable, if it is correctly configured.</p>]]></description>
			<author><![CDATA[dummy@example.com (igorzwx)]]></author>
			<pubDate>Fri, 26 Sep 2025 00:30:24 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=58243#p58243</guid>
		</item>
		<item>
			<title><![CDATA[Re: ALSA: Dogmatism and Empiriokritizismus]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=58242#p58242</link>
			<description><![CDATA[<p>I&#039;m not sure what you take issue with... perhaps just that documentation on the web is old?</p><p>Otherwise I think one of the confusing aspects of ALSA configuration changes is that in general any program that use the audio system will end up loading an instantiating a configuration structure internally only once, when it starts. Therefore, such programs need restart after a change to the configuration source files, which include the user&#039;s <span class="bbc">.asoundrc</span> file.</p><p>Though, a program may of course have been made to reload the configuration, and in that case such a program will do so as programmed and then rebuild the internal configuration structure from that on file.</p><p>I would suggest that old and bad documentation can only be remedied by writing new and better documentation; grumbling about what&#039;s existing and discussing it&#039;s badness is just waste of time.</p>]]></description>
			<author><![CDATA[dummy@example.com (ralph.ronnquist)]]></author>
			<pubDate>Fri, 26 Sep 2025 00:16:37 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=58242#p58242</guid>
		</item>
		<item>
			<title><![CDATA[Re: ALSA: Dogmatism and Empiriokritizismus]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=58241#p58241</link>
			<description><![CDATA[<p>Could we keep to technical discussions please.</p>]]></description>
			<author><![CDATA[dummy@example.com (ralph.ronnquist)]]></author>
			<pubDate>Thu, 25 Sep 2025 23:57:49 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=58241#p58241</guid>
		</item>
		<item>
			<title><![CDATA[Re: ALSA: Dogmatism and Empiriokritizismus]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=58240#p58240</link>
			<description><![CDATA[<p>Off your meds again Igor?</p>]]></description>
			<author><![CDATA[dummy@example.com (greenjeans)]]></author>
			<pubDate>Thu, 25 Sep 2025 23:37:05 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=58240#p58240</guid>
		</item>
		<item>
			<title><![CDATA[ALSA: Dogmatism and Empiriokritizismus]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=58239#p58239</link>
			<description><![CDATA[<p><strong>The official ALSA documentation is here:</strong> _https://www.alsa-project.org/wiki/Asoundrc</p><div class="quotebox"><blockquote><div><p><strong>ALSA: <span style="color: blue">Outdated</span> documentation</strong><br />_https://alsa.opensrc.org/Asoundrc#Changing_things</p><p><strong>Asoundrc: Changing things</strong></p><p>Most programs require a restart to reread .asoundrc or asound.conf! This includes desktop environment audio daemons, such as PulseAudio. For most changes to .asoundrc you will need to restart the sound server (ie. sudo /etc/init.d/alsa-utils restart) for the changes to take effect.</p></div></blockquote></div><p>This chapter was deprecated and removed from the official ALSA documentation about 15 years ago (or more). However, the true believers still believe that it is necessary to reload ALSA &quot;for the changes [in .asoundrc] to take effect&quot;.</p><div class="quotebox"><blockquote><div><p>If you see a &quot;buffalo&quot; sign on an elephant&#039;s cage, do not trust your eyes.<br />Kozma Prutkov, <em>Fruits of Reflection</em> (1853-1854)</p></div></blockquote></div><p>To believe in a dogma, one should not trust his senses and his ability to think.</p><p>EDIT:</p><div class="quotebox"><cite>greenjeans wrote:</cite><blockquote><div><p>2025-09-22 15:51:04<br />I think I would start by making a super simple <span style="color: red"><strong>.asoundrc</strong></span> and going from there...</p><p>If that works, a simple script that offers a dialog where you choose either 0, 1, or 2, and it seds the change and <strong><span style="color: red">re-starts alsa</span></strong>, would allow you to change during session.<br />_https://dev1galaxy.org/viewtopic.php?pid=58157#p58157</p></div></blockquote></div><div class="quotebox"><cite>ralph.ronnquist wrote:</cite><blockquote><div><p>Yes, and one thing that is confusing with ALSA is that programs typically loads the sound configuration only once, early during startup. Therefore such a change to the configuration only takes effect for programs that are started after the change.</p><p>There is a way to make a configuration have a dynamic part, to be automatically reloaded upon every sink (or source) creation instead, but then we are entering a deeper level of understanding of ALSA configuration structure and elements which most people rather wish to avoid.</p></div></blockquote></div><p>It is so &quot;technical&quot;, that it is almost incomprehensible.</p>]]></description>
			<author><![CDATA[dummy@example.com (igorzwx)]]></author>
			<pubDate>Thu, 25 Sep 2025 23:01:56 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=58239#p58239</guid>
		</item>
	</channel>
</rss>
