1. Forum
  2. Usenet
  3. LINUX.GENTOO.USER

  • [gentoo-user] Re: Pipewire not a dependency?

    From Nikos Chantziaras@21:1/5 to Michael on Thu Sep 29 16:20:01 2022
    On 28/09/2022 13:57, Michael wrote:
    I'm trying to understand why one laptop with Plasma which had pulseaudio removed, won't bring in pipewire as a dependency. I have set USE="- screencast", because I don't need/want this functionality, as I have done on other systems which nevertheless have had pipewire brought in as a dependency.

    Probably some other package pulls it in directly, independent of the
    screencast USE flag. For example media-sound/easyeffects.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael@21:1/5 to All on Sat Oct 1 15:08:40 2022
    On Thursday, 29 September 2022 15:11:02 BST Nikos Chantziaras wrote:
    On 28/09/2022 13:57, Michael wrote:
    I'm trying to understand why one laptop with Plasma which had pulseaudio removed, won't bring in pipewire as a dependency. I have set USE="- screencast", because I don't need/want this functionality, as I have done on other systems which nevertheless have had pipewire brought in as a dependency.
    Probably some other package pulls it in directly, independent of the screencast USE flag. For example media-sound/easyeffects.

    I just looked and a pipewire(d) system has only a few additional audio applications, spek, vidcutter, easytag, none of which seem to bring in pipewire. I think I'll have to install it manually on the system which
    doesn't bring it in as some dependency. Somehow I was under the impression it comes with Plasma these days, but perhaps I have stripped down this Plasma/kde installation too much.
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmM4SegACgkQseqq9sKV ZxmxwBAAkF6iwjtMa5nr16yVU3zeAO68ehiH+YpTP2a0TbFdvY5cUCuXq92DvXdp xmUMe9DW0m4ac/D4/x9vihoWS8IrOwGa2pDQvImNks8x4Wl/TvS+6aRe3RNrUbXQ vVntaN9FyYrePs1k2kSQbHW9INFTJZl3mHPSO3HWktFS1HrA6kzfJ8DuCzBZZCGS Vnpccqj0P+rDeeOUYrKgo8sALO0EGXuaCn4JQm/rIKd0jzQ+Qa+TXqs0bAyOJO6v 6wdhdY8txYGm1UPutzdthrZoz/nXS85KfuwbWxTOz7PH/2c3PVBV/wHo1ldt12G3 Ugny/YKhVFWY2nH24orr0gUcTrzpWO1ZyM9LW6R8VtW/2UcStTx+4C7+UG7Sxso8 9l0+hsow5pYtM5OhMhQyTyhdqA4chl7w2iuLQ/syLzxLOUq4kNnyAfhjn4esmlyk EUykDwe0+Bg0cGIyb38onnKWuGbIpgPghUCxFF2XfGtqahTMWRL2TyhPykvkvSKi 9CSdbxk2sba3WDZHIXZ4MCe01mYHi3lx0A67PYWNLA9YKiwB16Cd+fENZlmjWQQU qog9W2Cq690j3ReKpDn1QJEq5o4SPvsxPxUnGhNGeU0pAQu7DLm6815iLQffMB39 oQ0Fuu5miEU3fa0GP96YbmA2UV6cL4zrQIX/NYfyu+N76ZkDCDM=
    =TUAm
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Peter Humphrey@21:1/5 to All on Sat Oct 1 17:00:01 2022
    On Saturday, 1 October 2022 15:08:40 BST Michael wrote:
    On Thursday, 29 September 2022 15:11:02 BST Nikos Chantziaras wrote:
    On 28/09/2022 13:57, Michael wrote:
    I'm trying to understand why one laptop with Plasma which had
    pulseaudio
    removed, won't bring in pipewire as a dependency. I have set USE="- screencast", because I don't need/want this functionality, as I have
    done
    on other systems which nevertheless have had pipewire brought in as a dependency.

    Probably some other package pulls it in directly, independent of the screencast USE flag. For example media-sound/easyeffects.

    I just looked and a pipewire(d) system has only a few additional audio applications, spek, vidcutter, easytag, none of which seem to bring in pipewire. I think I'll have to install it manually on the system which doesn't bring it in as some dependency. Somehow I was under the impression it comes with Plasma these days, but perhaps I have stripped down this Plasma/kde installation too much.

    I have no pipewire on this fairly standard Plasma box.

    --
    Regards,
    Peter.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mark Knecht@21:1/5 to [email protected] on Sat Oct 1 17:00:01 2022
    On Sat, Oct 1, 2022 at 7:51 AM Peter Humphrey <[email protected]> wrote:

    On Saturday, 1 October 2022 15:08:40 BST Michael wrote:
    On Thursday, 29 September 2022 15:11:02 BST Nikos Chantziaras wrote:
    On 28/09/2022 13:57, Michael wrote:
    I'm trying to understand why one laptop with Plasma which had
    pulseaudio
    removed, won't bring in pipewire as a dependency. I have set USE="- screencast", because I don't need/want this functionality, as I have done
    on other systems which nevertheless have had pipewire brought in as
    a
    dependency.

    Probably some other package pulls it in directly, independent of the screencast USE flag. For example media-sound/easyeffects.

    I just looked and a pipewire(d) system has only a few additional audio applications, spek, vidcutter, easytag, none of which seem to bring in pipewire. I think I'll have to install it manually on the system which doesn't bring it in as some dependency. Somehow I was under the
    impression
    it comes with Plasma these days, but perhaps I have stripped down this Plasma/kde installation too much.

    I have no pipewire on this fairly standard Plasma box.


    I believe that pipewire, as far as KDE users are concerned, is a
    distro choice about when to use it.

    My Kubuntu boxes started using it recently. I had no issues and
    didn't need to change any settings for any application that makes
    use of sound.

    YMMV,
    Mark

    <div dir="ltr"><br><br>On Sat, Oct 1, 2022 at 7:51 AM Peter Humphrey &lt;<a href="mailto:[email protected]">[email protected]</a>&gt; wrote:<br>&gt;<br>&gt; On Saturday, 1 October 2022 15:08:40 BST Michael wrote:<br>&gt; &gt; On Thursday, 29
    September 2022 15:11:02 BST Nikos Chantziaras wrote:<br>&gt; &gt; &gt; On 28/09/2022 13:57, Michael wrote:<br>&gt; &gt; &gt; &gt; I&#39;m trying to understand why one laptop with Plasma which had<br>&gt; pulseaudio<br>&gt; &gt; &gt; &gt; removed, won&#39;
    t bring in pipewire as a dependency.  I have set USE=&quot;-<br>&gt; &gt; &gt; &gt; screencast&quot;, because I don&#39;t need/want this functionality, as I have<br>&gt; &gt; &gt; &gt; done<br>&gt; &gt; &gt; &gt; on other systems which nevertheless have
    had pipewire brought in as a<br>&gt; &gt; &gt; &gt; dependency.<br>&gt; &gt; &gt;<br>&gt; &gt; &gt; Probably some other package pulls it in directly, independent of the<br>&gt; &gt; &gt; screencast USE flag. For example media-sound/easyeffects.<br>&gt; &
    gt;<br>&gt; &gt; I just looked and a pipewire(d) system has only a few additional audio<br>&gt; &gt; applications, spek, vidcutter, easytag, none of which seem to bring in<br>&gt; &gt; pipewire.  I think I&#39;ll have to install it manually on the
    system which<br>&gt; &gt; doesn&#39;t bring it in as some dependency.  Somehow I was under the impression<br>&gt; &gt; it comes with Plasma these days, but perhaps I have stripped down this<br>&gt; &gt; Plasma/kde installation too much.<br>&gt;<br>&gt;
    I have no pipewire on this fairly standard Plasma box.<br>&gt;<br><br><div>I believe that pipewire, as far as KDE users are concerned, is a </div><div>distro choice about when to use it.</div><div><br></div><div>My Kubuntu boxes started using it
    recently. I had no issues and </div><div>didn&#39;t need to change any settings for any application that makes </div><div>use of sound.</div><div><br></div><div>YMMV,</div><div>Mark</div></div>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael@21:1/5 to All on Sat Oct 1 17:56:40 2022
    On Saturday, 1 October 2022 15:57:03 BST Mark Knecht wrote:
    On Sat, Oct 1, 2022 at 7:51 AM Peter Humphrey <[email protected]> wrote:
    On Saturday, 1 October 2022 15:08:40 BST Michael wrote:
    On Thursday, 29 September 2022 15:11:02 BST Nikos Chantziaras wrote:
    On 28/09/2022 13:57, Michael wrote:
    I'm trying to understand why one laptop with Plasma which had

    pulseaudio

    removed, won't bring in pipewire as a dependency. I have set USE="- screencast", because I don't need/want this functionality, as I have done
    on other systems which nevertheless have had pipewire brought in as

    a

    dependency.

    Probably some other package pulls it in directly, independent of the screencast USE flag. For example media-sound/easyeffects.

    I just looked and a pipewire(d) system has only a few additional audio applications, spek, vidcutter, easytag, none of which seem to bring in pipewire. I think I'll have to install it manually on the system which doesn't bring it in as some dependency. Somehow I was under the

    impression

    it comes with Plasma these days, but perhaps I have stripped down this Plasma/kde installation too much.

    I have no pipewire on this fairly standard Plasma box.

    I believe that pipewire, as far as KDE users are concerned, is a
    distro choice about when to use it.

    My Kubuntu boxes started using it recently. I had no issues and
    didn't need to change any settings for any application that makes
    use of sound.

    YMMV,
    Mark

    Thank you all for your responses. It could be some Plasma/KDE USE flag which differs between my systems causing this. Without spending a lot of time I wouldn't know for sure TBH.

    Anyway, I ventured into pipewire because I wanted to see if Skype would work without pulseaudio and in this system it won't. After I manually installed pipewire Skype won't access the microphone. :-(

    Re-enabling pulseaudio wants to rebuild some 30 packages including
    qtwebengine. That's an overnight job on this old laptop.
    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmM4cUgACgkQseqq9sKV ZxkJcw//YXsbCBDs5mxoTLEIgXQM5nBtlkdLpQGEPOxAZSHe2LGqmmEmm3s91Vc2 nJtPCRDjV7wQWGN2XUN1+G8UtU0AzRSloOc2gWcYCbyblAnUZphDCf8lHNtLDnY9 jJduJPdqwbR5CM/jnuEvgFrZIpDwqynzMW/+RLBcxn1xXNCqaNyqKT9zJwtpUO9E rIzC7FY1VXLIXZ4oISK5cBU02qzffvDYj10FHvWtry97mE2y/lYTphaUNssHy/BM QUZLWE6K3nPVvvjwq4j8DkZ6VnJN5G0wIhJW2po6FXa2Kpi2uh12GrBwj0xOOYuy eE7FZN1wrBU2h6JH5i4rRl22g9cd8WBTuoDXnoa/VnhZ6i+DX8kMQNwVrEkcGhfY 73iHfPOi+4XQhbcSY/QV0tmNX7SgwXGYT4ON8uf6ss7A5yW5Pc+0+jhanhnC/yNP SbLjZGrPzXLFszxZx/flD/fOsnop1lx6cQ+q+BpPtXI9nJIryR5wx32A6iodjtNd GD0Is5yA7wJYVtoM0OQWHvzlXReu8Pvh8J/p0DeaR981NTlSWMtYissO6hfxz6qQ 9xCYM5DXNvqOWsXcM0dpUgveaPtKrToe48G7v4BeD0pDf0pUul81wY2lLzmJxwv2 lYNpHvTEUs5xghS7R59fsy7bNwAtGXQUKLNi1cfWZvTGdDxJu/g=
    =BFfQ
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Wol@21:1/5 to Michael on Sat Oct 1 19:20:01 2022
    On 01/10/2022 17:56, Michael wrote:
    Anyway, I ventured into pipewire because I wanted to see if Skype would work without pulseaudio and in this system it won't. After I manually installed pipewire Skype won't access the microphone. 🙁

    I've got some vague feeling that pipewire is designed to happily sit
    under pulseaudio. The design aim was to replace both Jack and pulseaudio
    but it basically just presents a sound device to the layers above, so
    just like you can stack block devices for disk access, you can stack
    jack, pulseaudio and pipewire for sound.

    The big difference between a sound stack and a block stack is that a
    block stack is asynchronous and latency is (relatively) unimportant. In
    a sound stack some applications *demand* synchronicity, and latency is everything. Jack is extremely latency sensitive, pulseaudio buffers and
    doesn't care, and pipewire is intended to satisfy both.

    So the intent was clearly to install pipewire underneath a working
    pulseaudio, and just move applications across as and when.

    Cheers,
    Wol

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Daniel Sonck@21:1/5 to All on Sat Oct 1 20:40:01 2022
    This is a multi-part message in MIME format.

    On zaterdag 1 oktober 2022 19:11:19 CEST Wol wrote:
    On 01/10/2022 17:56, Michael wrote:
    Anyway, I ventured into pipewire because I wanted to see if Skype would work without pulseaudio and in this system it won't. After I manually installed pipewire Skype won't access the microphone. 🙁

    I've got some vague feeling that pipewire is designed to happily sit
    under pulseaudio. The design aim was to replace both Jack and pulseaudio
    but it basically just presents a sound device to the layers above, so
    just like you can stack block devices for disk access, you can stack
    jack, pulseaudio and pipewire for sound.
    Well, it is actually designed as a drop-in replacement and won't present audio devices in the
    sense pulseaudio wants to receive it. I guess it would theoretically be possible to use
    pulseaudio's jack sink to talk to pipewire, but pipewire has the full pulseaudio interface for
    pulseaudio applications.

    The big difference between a sound stack and a block stack is that a
    block stack is asynchronous and latency is (relatively) unimportant. In
    a sound stack some applications *demand* synchronicity, and latency is everything. Jack is extremely latency sensitive, pulseaudio buffers and doesn't care, and pipewire is intended to satisfy both.

    So the intent was clearly to install pipewire underneath a working pulseaudio, and just move applications across as and when.
    This was never an intent, pipewire was intended as an pulseaudio implementation by itself. So
    it doesn't need (and likely is incompatible running together with) pulseaudio in order to
    support pulseaudio clients. But it does need to be configured as such.

    Cheers,
    Wol

    Regards,

    Daniel

    <html>
    <head>
    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
    </head>
    <body><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">On zaterdag 1 oktober 2022 19:11:19 CEST Wol wrote:</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; On 01/10/2022 17:56, Michael wrote:</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; &gt; Anyway, I ventured into pipewire because I wanted to see if Skype would</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; &gt; work without pulseaudio and in this system it won't.&nbsp; After I manually</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; &gt; installed pipewire Skype won't access the microphone.&nbsp; 🙁</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; </p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; I've got some vague feeling that pipewire is designed to happily sit</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; under pulseaudio. The design aim was to replace both Jack and pulseaudio</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; but it basically just presents a sound device to the layers above, so</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; just like you can stack block devices for disk access, you can stack</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; jack, pulseaudio and pipewire for sound.</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Well, it is actually designed as a drop-in replacement and won't present audio devices in the sense pulseaudio wants to receive it. I guess it would theoretically be possible to use
    pulseaudio's jack sink to talk to pipewire, but pipewire has the full pulseaudio interface for pulseaudio applications.</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; </p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; The big difference between a sound stack and a block stack is that a</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; block stack is asynchronous and latency is (relatively) unimportant. In</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; a sound stack some applications *demand* synchronicity, and latency is</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; everything. Jack is extremely latency sensitive, pulseaudio buffers and</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; doesn't care, and pipewire is intended to satisfy both.</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; </p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; So the intent was clearly to install pipewire underneath a working</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; pulseaudio, and just move applications across as and when.</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">This was never an intent, pipewire was intended as an pulseaudio implementation by itself. So it doesn't need (and likely is incompatible running together with) pulseaudio in order to
    support pulseaudio clients. But it does need to be configured as such.</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; </p> <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; Cheers,</p>
    <p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">&gt; Wol</p>
    <br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Regards,</p>
    <br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Daniel</p>
    </body>
    </html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael@21:1/5 to All on Sat Oct 1 19:29:17 2022
    On Saturday, 1 October 2022 18:11:19 BST Wol wrote:
    On 01/10/2022 17:56, Michael wrote:
    Anyway, I ventured into pipewire because I wanted to see if Skype would work without pulseaudio and in this system it won't. After I manually installed pipewire Skype won't access the microphone. 🙁

    I've got some vague feeling that pipewire is designed to happily sit
    under pulseaudio. The design aim was to replace both Jack and pulseaudio
    but it basically just presents a sound device to the layers above, so
    just like you can stack block devices for disk access, you can stack
    jack, pulseaudio and pipewire for sound.

    The big difference between a sound stack and a block stack is that a
    block stack is asynchronous and latency is (relatively) unimportant. In
    a sound stack some applications *demand* synchronicity, and latency is everything. Jack is extremely latency sensitive, pulseaudio buffers and doesn't care, and pipewire is intended to satisfy both.

    So the intent was clearly to install pipewire underneath a working pulseaudio, and just move applications across as and when.

    Cheers,
    Wol

    My very limited understanding is pipewire is meant to replace pulseaudio and jack, rather than become part of an audio/video stack:

    https://docs.pipewire.org/page_overview.html

    I think applications will gradually be coded to work with pipewire, until then suitable pipewire plugins would be required. Perhaps for Skype to work today I will also have to enable pulseaudio, at which point it will not need pipewire itself. The strange thing is audio playback works great with pipewire, it's the microphone which does not appear to be capturing anything and causes Skype to disconnect. :-/

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmM4hv0ACgkQseqq9sKV ZxmU1xAA6Ks2krCyUfpz1Qn+/G8r/SNuEc2bIZbucCSDrOPJMru7W6kUT6o7Qjb9 a+PFDH67ALIAFzMUYmBUJoCK8PfXb9EfL96fJWos/n0YLk0Z3fRtQP5hKvNGHC3I 7Sh5ZMs8I8RMQjecouK+U+aDXE5wfRgLtn+rs26l7OdGj4SkdaUPYlTy9dGtORSv Q1i2hx0DrKzqd9TWagfW/lJFg6V85LBUFsag69tp94JdRPvheU8x6b2Pac1yq3eN wRI6HM+pKYIYB8ZOpiYwPbF1y/kxRM+j/+O3wCnmcW00nC3MUnkeaN88fxLrntOf mHV3+p9DBAS0zYRM8q+W4SQkp1CtYiEMYX7UvCp9umC2Nu+H2b4mkAYNnyON1gi0 HI13605smXDNgPCbo5sWV6xYvQfmnS15maci7NtjScRSU39akSU1Rcv//IM9Mz2s AfgqI9BftACCT0GXSrbFMldqwwhjtl9GuKD7shqa3jv3Qji/eWfYqJPtdmEq66Ns XQS1D6SuxTXpnPfHi/8j4bAMgNc/7M5GOxIVXwleR5+fPYvKOVkGXKz+SmSczP9n d39Y+3vfbkpO0CGtXmpz+oMP2UWmVRDUY2uK8goMqmH4MiYDZqUYLZZmK9O8dYR1 VaATG1NgyitbL8zIIwBG7Ccwqb0jORzd9QEiHEHwUU8w9zx0OJg=
    =U8LI
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Nikos Chantziaras@21:1/5 to Michael on Sun Oct 2 13:00:01 2022
    On 01/10/2022 19:56, Michael wrote:
    Anyway, I ventured into pipewire because I wanted to see if Skype would work without pulseaudio and in this system it won't. After I manually installed pipewire Skype won't access the microphone. :-(

    Maybe Skype uses ALSA? It's best to enable the "pipewire-alsa" USE flag
    on pipewire and disable the "pulseaudio" flag on alsa-plugins:

    media-video/pipewire: pipewire-alsa
    media-plugins/alsa-plugins: -pulseaudio

    This replaces pulseaudio's ALSA plugin with pipewire's. Skype might work
    with this.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)