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.
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.
On Thursday, 29 September 2022 15:11:02 BST Nikos Chantziaras wrote:pulseaudio
On 28/09/2022 13:57, Michael wrote:
I'm trying to understand why one laptop with Plasma which had
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.
On Saturday, 1 October 2022 15:08:40 BST Michael wrote:a
On Thursday, 29 September 2022 15:11:02 BST Nikos Chantziaras wrote:pulseaudio
On 28/09/2022 13:57, Michael wrote:
I'm trying to understand why one laptop with Plasma which had
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
impressiondependency.
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
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.
On Sat, Oct 1, 2022 at 7:51 AM Peter Humphrey <peter@prh.myzen.co.uk> 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
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. 🙁
On 01/10/2022 17:56, Michael wrote:Well, it is actually designed as a drop-in replacement and won't present audio devices in the
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 aThis was never an intent, pipewire was intended as an pulseaudio implementation by itself. So
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
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
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. :-(
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 303 |
Nodes: | 16 (3 / 13) |
Uptime: | 86:49:44 |
Calls: | 6,811 |
Calls today: | 3 |
Files: | 12,328 |
Messages: | 5,401,758 |