Announcement
Collapse
No announcement yet.
Red Hat Formally Rolls Out Pipewire For Being The "Video Equivalent of PulseAudio"
Collapse
X
-
Originally posted by dwagner View PostIf pipewire is meant to be useful, I sure hope it is nothing like pulseaudio. On every system that I need audio to work at, pulseaudio is the first component I remove, using ALSA directly, instead.
Pulseaudio had no issues on anything I've used OpenSUSE or Linux Mint Debian on in the last 3 years.
."User A to use audio device X, while user B uses audio device Y on the same computer at the same time"..Last edited by starshipeleven; 20 September 2017, 03:15 AM.
- Likes 2
Comment
-
How come there are so many completely clueless trolls on here complaining about progress in Linux? Pulseaudio and systemd are both major wins for Linux as a platform, retards who have not written a single line of code or sent a single bug report should just be quiet.
- Likes 9
Comment
-
Haha, it is the Current Year and troll still hate systemd and pulseaudio. I never had a problem with these since a couple if years already. Idk, maybe switch from your crappy hardware with badly supported audio drivers.
"Anticompetitive". No, it is as competitive as you get. If you don't like it then continue using shell scripts. Can't blame distributions they choose superior system. Same goes for pulseaudio.
Shout out to red had devs. Keep up the good work, the silent 99% majority supports your efforts in making Linux superior platform that it already is.
- Likes 2
Comment
-
Originally posted by starshipeleven View PostUnless you are building an audio workstation I don't see what issues PA is giving you.
Pulseaudio had no issues on anything I've used OpenSUSE or Linux Mint Debian on in the last 3 years.
.Pulseaudio works by default on a per-user basis, so that should as easy as changing pulseaudio per-user files in their home directories.
- Likes 1
Comment
-
Originally posted by duby229 View Post
And your experiences are yours. On Gentoo PA just simply pauses the audio by itself for completely unexplainable reasons. There has been no input on it, no advice, no solution. It's been this way since at least 3 years. Plus there's the multiple seconds of latency that is completely unavoidable. That also has had no input, no advice and no solution. It those two major bugs that make it unusable for -me-. It's plainly obvious how experiences can differ.
- Likes 3
Comment
-
Originally posted by duby229 View PostAnd your experiences are yours. On Gentoo PA just simply pauses the audio by itself for completely unexplainable reasons. There has been no input on it, no advice, no solution. It's been this way since at least 3 years. Plus there's the multiple seconds of latency that is completely unavoidable. That also has had no input, no advice and no solution. It those two major bugs that make it unusable for -me-. It's plainly obvious how experiences can differ.
Same as Ubuntu that for some reason manages to have their KDE boot in 1 minute on a SSD and use a ton more RAM than normal.
Comment
-
Originally posted by arokh View PostWhere's the bug report? Never seen this on my machines, sounds more like a Gentoo specific issue. Due to use flags, masks and lots of other factors not one Gentoo box is the same either I guess. If it's reproducible on Gentoo and nobody was able to debug it in 3 years then I'd say that sounds to me like the Gentoo community is dead.
- Likes 3
Comment
-
Originally posted by arokh View Post
Where's the bug report? Never seen this on my machines, sounds more like a Gentoo specific issue. Due to use flags, masks and lots of other factors not one Gentoo box is the same either I guess. If it's reproducible on Gentoo and nobody was able to debug it in 3 years then I'd say that sounds to me like the Gentoo community is dead.
Check this out. https://bugs.launchpad.net/ubuntu/+source/pulseaudio
Many, many many of those bug rep[orts are directly related to the audio outputs pausing for completely unknown reasons. Where the solution is to simply open up pavucontrol and unpuase the output. It's obviously a long standing upstream bug.
And I'm reasonably sure these bugs are directly related, but I don't know enough.
Last edited by duby229; 20 September 2017, 11:00 AM.
Comment
Comment