On Sat, 21 Nov 2020, Neal Gompa wrote:
On Sat, Nov 21, 2020 at 3:53 PM James Szinger <jszinger@xxxxxxxxx> wrote:
On Sat, 21 Nov 2020 19:47:30 -0000
"Tom Seewald" <tseewald@xxxxxxxxx> wrote:
> Things like bluetooth support, audio for flatpak applications, and
> the new pulse server were just added in the last month or so and
> there are issues with stability and audio playback (look at the issue
> tracker [1]), for example HSP is still marked as WIP [2]. It seems
> premature to commit to this change before the core features have been
> stabilized and more testing has been done. Audio is an area where
> users really have no tolerance for it misbehaving. Pushing a change
> like this too early can create a negative perception of the project
> which is something we should try to avoid (within reason).
According to the FAQ
`https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/FAQ`
Is PipeWire ready yet?
It is getting ready for broader testing.
There’s also
`https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Limitations-in-0.3`
Upstream says it is not ready!
Linux has had a large number of audio systems (OSS, ALSA, ESD,
pulseaudio, and probably some I’ve forgotten), and almost as many
painful transitions from one to the next. Since then audio has become
a vital part of the computer desktop experience. Please make this
less painful and don’t make this the default until it is ready and
tested.
The upstream developer of PipeWire is the one who submitted this
Change proposal. Before this proposal was submitted, he talked to us
in the Workstation WG about it and stated that he's confident that
PipeWire is in good shape for Fedora 34 and provides a straightforward
way to fall back to legacy PulseAudio as needed.
I spent about three weeks trying to live with pipewire in
October/November and encountered a lot of issues, most of them were
already reported. The most important one is instability of conference
calls with Google Meet in both Firefox and Chrome and inability to share
more than a single browser page window on Wayland. The pipewire and its
portal are stating everything is ok but the content is simply not
streaming out.
Also, constant change of the audio inputs and outputs, like arbitrarily
switching the defaults for mic between USB devices, thunderbolt-based
dock and the built-in one on Thinkpad attached to the dock, is making it
very hard to accept it is a stable and predictable software.
These are the ones that really turned me away from using pipewire on
F33. I tried twice: first with F32, then F33 and it is simply not ready
for even basic office use case with a laptop in dock and multiple
monitors with audio outputs.
This is just one evidence point, of course, and highly personal, but I
do not see how pipewire could become a default with the current quality.
Shipped in parallel, with easy to switch ways, sure.
--
/ Alexander Bokovoy
Sr. Principal Software Engineer
Security / Identity Management Engineering
Red Hat Limited, Finland
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
