Red Hat Formally Rolls Out Pipewire For Being The "Video Equivalent of PulseAudio"

[smitty3268]

Did you check the initial commit? There it's called PulseVideo later it was Pinos and now Pipewire.
https://github.com/PipeWire/pipewire...116bb2cfeaa322
https://blogs.gnome.org/uraeus/2015/...g-pulse-video/

PulseVideo sounds vaguely pornographic.

[ssokolow]

I already did, you just refuse to look at them. I posted a link to Ubuntu's bug tracker where Pulseaudio bugs are tracked, and also two upstream bug reports. Look at them please.

Why not just repost them? Not everybody wants to go searching back for the specific post in question, while you already know it because you wrote it.

Also, keep in mind that it is legitimate to ask for the same exact symptoms only. As someone who's written code and tracked down bugs, I know all too well how broken the default human "these probably have the same root cause" intuition is when dealing with something other than a concrete, greppable error message.

(And, trust me, I feel your pain. When Lubuntu randomly decided to switch my default ALSA audio output to an HDMI->DVI cable one morning, and I couldn't figure out how to reset it, it took a lot of tweaking to get PulseAudio to play nicely with my PlayOnLinux and various Linux-native games like FTL, rather than randomly switching to or from garbled audio. I finally ended up having to combine the tsched hack, which wastes CPU, with PULSE_LATENCY_MSEC=60.)

[duby229]

Why not just repost them? Not everybody wants to go searching back for the specific post in question, while you already know it because you wrote it.

Also, keep in mind that it is legitimate to ask for the same exact symptoms only. As someone who's written code and tracked down bugs, I know all too well how broken the default human "these probably have the same root cause" intuition is when dealing with something other than a concrete, greppable error message.

(And, trust me, I feel your pain. When Lubuntu randomly decided to switch my default ALSA audio output to an HDMI->DVI cable one morning, and I couldn't figure out how to reset it, it took a lot of tweaking to get PulseAudio to play nicely with my PlayOnLinux and various Linux-native games like FTL, rather than randomly switching to or from garbled audio. I finally ended up having to combine the tsched hack, which wastes CPU, with PULSE_LATENCY_MSEC=60.)

Don't remind me One of my biggest pet peeves is runtime bugs with no error messages anywhere. I believe the root cause for that is because PA devs believe it's perfect and so the result is its logging characteristics don't capture common problems.

[Hi-Angel]

Did you check the initial commit? There it's called PulseVideo later it was Pinos and now Pipewire.
https://github.com/PipeWire/pipewire...116bb2cfeaa322
https://blogs.gnome.org/uraeus/2015/...g-pulse-video/

To be more precise, it's the quote:

Why the name Pinos?
The code name for the project was PulseVideo, but to avoid confusion with the PulseAudio project and avoid people making to many assumptions based on the name we decided to follow in the tradition of Wayland and Weston and take inspiration from local place names related to the creator. So since Wim lives in Pinos de Alhaurin close to Malaga in Spain we decided to call the project Pinos. Pinos is the word for pines in Spanish

Well, it's hard to confuse PulseAudio with PulseVideo, you can't even rhyme them. So they just made assumptions about others' assumptions, and threw away a rational name basing on that. They should've asked me — I have a major experience in guessing others' assumptions, and it never works :Ь

[Hi-Angel]

Did you check the initial commit? There it's called PulseVideo later it was Pinos and now Pipewire.
https://github.com/PipeWire/pipewire...116bb2cfeaa322
https://blogs.gnome.org/uraeus/2015/...g-pulse-video/

To be more precise, it's the quote:

Why the name Pinos?
The code name for the project was PulseVideo, but to avoid confusion with the PulseAudio project and avoid people making to many assumptions based on the name we decided to follow in the tradition of Wayland and Weston and take inspiration from local place names related to the creator. So since Wim lives in Pinos de Alhaurin close to Malaga in Spain we decided to call the project Pinos. Pinos is the word for pines in Spanish

Well, it's hard to confuse PulseAudio with PulseVideo, you can't even rhyme them. So they just made assumptions about others' assumptions, and threw away a rational name basing on that. They should've asked me — I have a major experience in guessing others' assumptions, and it never works :Ь

On the other hand now that I think about it, there is a rational reason to not name it PulseVideo, although they don't mention it. It's that "PulseVideo" implies having PulseAudio around, as if they collaborate. However PipeWire might replace PulseAudio in the future.

[starshipeleven]

I already did, you just refuse to look at them. I posted a link to Ubuntu's bug tracker where Pulseaudio bugs are tracked, and also two upstream bug reports. Look at them please.

Already looked, neither is "links to the bug reports specifically talking about your bugs", please post links to the bug reports specifically talking about your bugs.

[starshipeleven]

Don't remind me One of my biggest pet peeves is runtime bugs with no error messages anywhere. I believe the root cause for that is because PA devs believe it's perfect and so the result is its logging characteristics don't capture common problems.

in most programs you need to enable verbose (debug) logging, because otherwise they would spam your logs with debug stuff for no reason. Pulseaudio is no different.

[duby229]

in most programs you need to enable verbose (debug) logging, because otherwise they would spam your logs with debug stuff for no reason. Pulseaudio is no different.

This is someones log of this exact problem I described. As you can see there is no indication of it anywhere in there.

https://pastebin.com/kHykvjyp

[starshipeleven]

This is someones log of this exact problem I described. As you can see there is no indication of it anywhere in there.
https://pastebin.com/kHykvjyp

What told you that this is a "log of the exact problem you described" if there is "no indication of it anywhere in there" and there is no other description of the issue itself in that pastebin?

[duby229]

What told you that this is a "log of the exact problem you described" if there is "no indication of it anywhere in there" and there is no other description of the issue itself in that pastebin?

There are hundreds (or dozens at least) of these exact same bugs on Ubuntu's bug tracker which I already linked to.