<?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=4608&amp;type=rss" rel="self" type="application/rss+xml" />
		<title><![CDATA[Dev1 Galaxy Forum / [SOLVED] Back and Pipewire]]></title>
		<link>https://dev1galaxy.org/viewtopic.php?id=4608</link>
		<description><![CDATA[The most recent posts in [SOLVED] Back and Pipewire.]]></description>
		<lastBuildDate>Thu, 28 Oct 2021 06:18:50 +0000</lastBuildDate>
		<generator>FluxBB</generator>
		<item>
			<title><![CDATA[Re: [SOLVED] Back and Pipewire]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32459#p32459</link>
			<description><![CDATA[<div class="quotebox"><cite>kiwi wrote:</cite><blockquote><div><p>Which is why I tried the debian instructions, twice.</p><p>No go on a clean system.</p></div></blockquote></div><p>That&#039;s funny because the OpenSUSE Build Service has just managed to build some Debian bullseye packages for pipewire-pulse in a freshly-spun VM:</p><p><a href="https://software.opensuse.org//download.html?project=home%3AHead_on_a_Stick%3ADevuan%3Apipewire-pulse&amp;package=pipewire-pulse" rel="nofollow">https://software.opensuse.org//download … wire-pulse</a></p><p>You should post your method and errors if you want help building those packages locally ;-)</p><div class="quotebox"><cite>kiwi wrote:</cite><blockquote><div><p>What issues would you expect there @Head_on_a_Stick?</p></div></blockquote></div><p>People will point at you and laugh for using <span class="bbc">make install</span> instead of creating a package. And files in system paths that the package manager doesn&#039;t know about are generally a bad idea (IMO).</p>]]></description>
			<author><![CDATA[dummy@example.com (Head_on_a_Stick)]]></author>
			<pubDate>Thu, 28 Oct 2021 06:18:50 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32459#p32459</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Back and Pipewire]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32458#p32458</link>
			<description><![CDATA[<p>What issues would you expect there @Head_on_a_Stick?</p>]]></description>
			<author><![CDATA[dummy@example.com (kiwi)]]></author>
			<pubDate>Thu, 28 Oct 2021 01:08:04 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32458#p32458</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Back and Pipewire]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32455#p32455</link>
			<description><![CDATA[<p>Alternative update procedure.&#160; &#160;I found the backporting instructions failed me so instead updated only one package from Testing.&#160; As Head_on_a_Stick pointed out there is a risk as testing and stable diverge of updating packages that break your system.&#160; An alternative is to compile the current pipewire release.</p><p><a href="https://gitlab.freedesktop.org/pipewire/pipewire/-/releases" rel="nofollow">https://gitlab.freedesktop.org/pipewire … -/releases</a></p><p>The basic instructions are at&#160; <a href="https://pipewire.org" rel="nofollow">https://pipewire.org</a> but you first probably need to install meson and ninja build tools and some dependencies.&#160; &#160;There is a list provided at <a href="https://www.linuxfromscratch.org/blfs/view/svn/multimedia/pipewire.html" rel="nofollow">https://www.linuxfromscratch.org/blfs/v … ewire.html</a>. Otherwise, simply follow the instructions below and install packages in response to progressing error messages.&#160; FWIW I installed the following (some of which may not have been needed):</p><p>meson libdbus-1-dev libeina1a libecore1 libdbus-c++-dev libao-dev libasound2-dev libeudev-dev <br />libudev-dev libogg-dev libflac-dev libgl1-mesa-dev libopus-dev libxfixes-dev libvorbis-dev </p><p><strong>**Back up your system**</strong> - I use fsarchiver to save my root and home partitions.</p><p>Install the current version of pipewire for your system.&#160; You will then overwrite it in this process.</p><p>Check your current pipewire version and paths with:<br /><strong>pipewire --version<br />whereis pipewire</strong></p><p>The paths should match the installation paths below.</p><p>Next clone the pipewire repository with <strong>git clone <a href="https://gitlab.freedesktop.org/pipewire/pipewire.git" rel="nofollow">https://gitlab.freedesktop.org/pipewire/pipewire.git</a></strong></p><p>Then <strong>cd pipewire</strong> and</p><p><strong>./autogen.sh --prefix=/usr</strong><br /><strong>make</strong><br /><strong>sudo make install</strong></p><p>This will install <strong>/usr/bin/pipewire /usr/share/pipewire /usr/share/man/man1/pipewire.1.gz</strong></p><p>Check version and paths again then follow the instructions to Disable PulseAudio in the post above.</p>]]></description>
			<author><![CDATA[dummy@example.com (kiwi)]]></author>
			<pubDate>Wed, 27 Oct 2021 21:59:22 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32455#p32455</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Back and Pipewire]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32454#p32454</link>
			<description><![CDATA[<p>Which is why I tried the debian instructions, twice.</p><p>No go on a clean system.</p><p>In this method you do get to choose what packages you upgrade.&#160; I guess I should add the recommendation that people back up their system first.</p><p>I have also since compiled the most recent version of pipewire and installed that taking pipewire up one point release described as maybe bug fixes.&#160; Once I resolve which dev packages were needed I might write up that approach as a recommendation.</p>]]></description>
			<author><![CDATA[dummy@example.com (kiwi)]]></author>
			<pubDate>Wed, 27 Oct 2021 21:25:37 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32454#p32454</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Back and Pipewire]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32453#p32453</link>
			<description><![CDATA[<div class="quotebox"><cite>kiwi wrote:</cite><blockquote><div><p># <strong>To update to the latest pipewire</strong></p><p><strong>sudoedit /etc/apt/sources.list</strong><br />&#160; to add the desired sources:<br />&#160; deb <a href="http://pkgmaster.devuan.org/merged/" rel="nofollow">http://pkgmaster.devuan.org/merged/</a> daedalus main non-free contrib</p><p><strong>sudo apt update<br />sudo apt install --upgrade pipewire*</strong></p><p>then comment out the daedalus source line and rerun <strong>sudo apt update</strong> to avoid<br />upgrading other files to daedalus.&#160; If, in future you wish to upgrade to a new release<br />of pipewire, repeat this step.</p></div></blockquote></div><p>^ This might have worked for you now but there is an increasing chance of this technique breaking a stable system as testing moves ahead. There is a chance that method has already broken your system if it pulled in any critical packages from testing, such as glibc (libc6).</p><p>EDIT: which is why I suggested backporting. Twice.</p>]]></description>
			<author><![CDATA[dummy@example.com (Head_on_a_Stick)]]></author>
			<pubDate>Wed, 27 Oct 2021 19:00:27 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32453#p32453</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Back and Pipewire]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32436#p32436</link>
			<description><![CDATA[<p>Thanks.&#160; Amended note to reflect the advice (done, I see thanks).</p><p>Also, if you use a window manager like dwm, adding the process starts to your window manager init may result in multiple copies of the process if you log off and on again. So I tried creating 3 supervised processes using runit.&#160; &#160;Good simple instructions for runit can be found in:</p><p><a href="http://kchard.github.io/runit-quickstart/" rel="nofollow">http://kchard.github.io/runit-quickstart/</a></p><p>If you use runsv then top is unable to differentiate the command names so I changed to ps with:</p><p><strong>watch -n 5 &#039;ps -ef | egrep &quot;pipewire|audac|vlc|pulse|alsa&quot; | grep -v grep&#039;</strong></p><p>Edit: for some reason, the runsv approach gave me problems including firefox &amp; vivaldi not picking up the pipewire-pulse interface.&#160; This might have been due to the changed process names.&#160; So instead I created a batch file that wouldn&#039;t create second instances of the programs if called twice. I called it from my dwm autostart and also bound it to an alias in case pipewire crashed for some reason.&#160; The file I used was:</p><div class="codebox"><pre><code>#!/bin/dash

if [ -z &quot;$(ps -ef | rg &#039;pipewire$&#039; | rg -v rg)&quot; ]; then
    /usr/bin/pipewire &amp;
fi
sleep 0.2
if [ -z &quot;$(ps -ef | rg &#039;pipewire-media-session&#039; | rg -v rg)&quot; ]; then
    /usr/bin/pipewire-media-session &amp;
fi
if [ -z &quot;$(ps -ef | rg &#039;pipewire-pulse&#039; | rg -v rg)&quot; ]; then
    /usr/bin/pipewire-pulse &amp;
fi
sleep 0.3
ps -ef | rg &quot;pipewire|audac|vlc|pulse|alsa&quot; | rg -v &quot;rg pi|_restart&quot;</code></pre></div>]]></description>
			<author><![CDATA[dummy@example.com (kiwi)]]></author>
			<pubDate>Wed, 27 Oct 2021 00:24:17 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32436#p32436</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Back and Pipewire]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32435#p32435</link>
			<description><![CDATA[<p>A quick note . . . it is advised not to use pkgmaster in <span class="bbc">sources.list</span> because it is the source that all mirrors sync with.&#160; Please use one of the many mirrors offered on <a href="https://www.devuan.org/get-devuan" rel="nofollow">https://www.devuan.org/get-devuan</a> instead.</p>]]></description>
			<author><![CDATA[dummy@example.com (golinux)]]></author>
			<pubDate>Tue, 26 Oct 2021 23:06:33 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32435#p32435</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Back and Pipewire]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32434#p32434</link>
			<description><![CDATA[<p>As a guide for anyone else intending to replace pulseaudio with pipewire <br />(low latency, low system load, poetfree):</p><p># <strong>To update to the latest pipewire</strong></p><p>Before upgrading packages from the testing release make sure that you <strong>back up<br />your system</strong> in case you update any critical packages like glibc and break your <br />system. I use fsarchiver and keep several copies of my partitions for future <br />recoveries or clean installs.</p><p><strong>sudoedit /etc/apt/sources.list</strong><br />&#160; to add the desired sources:<br />&#160; deb <a href="http://pkgmaster.devuan.org/merged/" rel="nofollow">http://pkgmaster.devuan.org/merged/</a> daedalus main non-free contrib</p><p><strong>sudo apt update<br />sudo apt install --upgrade pipewire*</strong></p><p>then comment out the daedalus source line and rerun <strong>sudo apt update</strong> to avoid<br />upgrading other files to daedalus.&#160; If, in future you wish to upgrade to a new release<br />of pipewire, repeat this step.</p><p># <strong>To Disable PulseAudio</strong></p><p>After installing pipewire I used this as a guide: <br />&#160; &#160; &#160; &#160;<a href="https://pipewire-debian.github.io/pipewire-debian/" rel="nofollow">https://pipewire-debian.github.io/pipewire-debian/</a></p><p>Replace <strong>autospawn = no</strong> with <strong>autospawn = yes</strong> in files in the following<br />paths.&#160; Often the file will be called client.conf:<br /><strong>~/.config/pulse/</strong><br /><strong>/etc/pulse/</strong><br /><strong>/etc/pulse/client.conf.d/</strong></p><p>and in if you have <strong>/etc/xdg/autostart/pulseaudio.desktop</strong> then add <strong>.bak</strong> as a<br />suffix to disable it.</p><p>Then<br /><strong>sudo pkill -9 pulseaudio</strong><br /><strong>sudo update-rc.d pulseaudio-enable-autospawn disable</strong><br /><strong>sudo pkill -9 pulseaudio<br /></strong><br />and reboot your system which should now run pipewire-pulse instead of<br />pulseaudio.&#160; Should you ever want it back, reverse the process.</p><p>To monitor behaviour of key processes I use:<br /><strong>watch -n 5 &#039;top -n 1 -b -d 20 | sed 4,5d | rg &quot;alsa|pulse|pipew|audac|vlc&quot;&#039;</strong></p><p>but you could substitute egrep for rg (ripgrep).</p>]]></description>
			<author><![CDATA[dummy@example.com (kiwi)]]></author>
			<pubDate>Tue, 26 Oct 2021 22:23:01 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32434#p32434</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Back and Pipewire]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32414#p32414</link>
			<description><![CDATA[<p>I had tested the <em><strong>easy</strong></em> backporting options and other than having to add a lot of extra files also had some problems with the build.&#160; But I take your point about security so I explored some more.</p><p>This strategy also worked.&#160; It has the disadvantage that you&#039;ll have to repeat it in future for newer versions of pipewire if you want them but it was simple.</p><p>Add a line to /etc/apt/sources.list</p><div class="codebox"><pre><code>deb http://pkgmaster.devuan.org/merged/ daedalus main non-free contrib</code></pre></div><p>then</p><div class="codebox"><pre><code>sudo apt update
sudo apt install --upgrade pipewire*</code></pre></div><p>then <strong>comment out the line &amp; update again</strong> so that you don&#039;t accidentally upgrade other packages to daedalus. </p><p>Then prevent pulseaudio loading and add 3 lines to your window manager startup or other startup file</p><div class="codebox"><pre><code>/usr/bin/pipewire &amp;
/usr/bin/pipewire-media-session &amp;
/usr/bin/pipewire-pulse &amp;</code></pre></div>]]></description>
			<author><![CDATA[dummy@example.com (kiwi)]]></author>
			<pubDate>Tue, 26 Oct 2021 03:53:05 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32414#p32414</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Back and Pipewire]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32405#p32405</link>
			<description><![CDATA[<p>Note that testing isn&#039;t covered by the security team. IMO backporting was the better option.</p>]]></description>
			<author><![CDATA[dummy@example.com (Head_on_a_Stick)]]></author>
			<pubDate>Mon, 25 Oct 2021 15:39:16 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32405#p32405</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Back and Pipewire]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32401#p32401</link>
			<description><![CDATA[<p>Thanks Head_on_a_Stick,</p><p>I experimented with a Daedalus Partition, enabled Pipewire and checked my main apps.&#160; Everything was good and didn&#039;t seem too bleeding edge so I&#039;ve saved my current image and switched up.&#160; &#160;I can always revert if I run into problems.</p><p>Now:</p><div class="codebox"><pre><code>System:    Host: home Kernel: 5.14.0-2-amd64 x86_64 bits: 64 Desktop: dwm 6.1
           Distro: Devuan GNU/Linux 5 (daedalus/ceres)</code></pre></div>]]></description>
			<author><![CDATA[dummy@example.com (kiwi)]]></author>
			<pubDate>Mon, 25 Oct 2021 11:56:07 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32401#p32401</guid>
		</item>
		<item>
			<title><![CDATA[Re: [SOLVED] Back and Pipewire]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32349#p32349</link>
			<description><![CDATA[<p>The pipewire-pulse package is only available from daedelus &amp; ceres: <a href="https://pkginfo.devuan.org/cgi-bin/policy-query.html?c=package&amp;q=pipewire-pulse&amp;x=submit" rel="nofollow">https://pkginfo.devuan.org/cgi-bin/poli … e&amp;x=submit</a></p><p>Perhaps try backporting it? <a href="https://wiki.debian.org/SimpleBackportCreation" rel="nofollow">https://wiki.debian.org/SimpleBackportCreation</a></p><p>EDIT: see also <a href="http://dev1galaxy.org/viewtopic.php?id=4447" rel="nofollow">http://dev1galaxy.org/viewtopic.php?id=4447</a></p>]]></description>
			<author><![CDATA[dummy@example.com (Head_on_a_Stick)]]></author>
			<pubDate>Sat, 23 Oct 2021 08:56:22 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32349#p32349</guid>
		</item>
		<item>
			<title><![CDATA[[SOLVED] Back and Pipewire]]></title>
			<link>https://dev1galaxy.org/viewtopic.php?pid=32345#p32345</link>
			<description><![CDATA[<p>After 8 months of exploring other distros and window managers I&#039;m back.&#160; &#160;This time I&#039;ve installed chimaera with runit and dwm (base install was LXQt).&#160; Hassle free and Devuan gives me the best visual latency I&#039;ve seen (0.7 ms on xterm <a href="https://lwn.net/Articles/751763/" rel="nofollow">https://lwn.net/Articles/751763/</a>)</p><div class="codebox"><pre><code>System:    Host: home Kernel: 5.10.0-9-amd64 x86_64 bits: 64 Desktop: dwm 6.1
           Distro: Devuan GNU/Linux 4 (chimaera)
CPU:       Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 2200 MHz min/max: 2200/3600 MHz
Graphics:  Device-1: NVIDIA GP108 [GeForce GT 1030] driver: nvidia v: 460.91.03
           Display: x11 server: X.Org 1.20.11 driver: loaded: nvidia
           unloaded: fbdev,modesetting,nouveau,vesa resolution: 1: 1920x1080~60Hz 2: 1920x1080~60Hz
           OpenGL: renderer: GeForce GT 1030/PCIe/SSE2 v: 4.6.0 NVIDIA 460.91.03
Drives:    Local Storage: total: 2.84 TiB used: 1.84 TiB (64.7%)
Info:      Processes: 290 Uptime: 2h 44m Memory: 15.64 GiB used: 4.09 GiB (26.1%) Shell: Bash
           inxi: 3.3.01

X11 version number: 11.0 X.Org version: 1.20.11
wine : wine-6.0.1</code></pre></div><p>I&#039;ve got one problem now.&#160; I would like to use pipewire instead of pulseaudio and can&#039;t find instructions anywhere that I can make work.&#160; Is anyone aware of a guide to pipewire conversion likely to work in a Devuan / runit environment.&#160; No biggie if not - I&#039;m happy to be back to Devuan.</p>]]></description>
			<author><![CDATA[dummy@example.com (kiwi)]]></author>
			<pubDate>Sat, 23 Oct 2021 03:01:28 +0000</pubDate>
			<guid>https://dev1galaxy.org/viewtopic.php?pid=32345#p32345</guid>
		</item>
	</channel>
</rss>
