Thank you, Ben. Good point. Mark On Fri, Jun 28, 2024 at 5:20 AM Ben Koenig <[email protected]> wrote:
> Pipewire has a pulseaudio compatiblity layer (pipewire-pulse) that > masquerades as a pulseaudio daemon, allowing applications to talk to it via > libpulse client libraries. If you suspect a problem in how pulseaudio is > handling the input/output streams, you can try switching over to the > daemon, and retest your application without any changes. > > > This might not be super helpful for developing an app, but I switched to > the pipewire daemon on my desktop and from a usage perspective, nothing > changes. Applications that are written for pulseaudio will talk to the > pipewire-pulse daemon without any issues. It seems stable in terms of > overall functionality. > > -Ben > > On Thursday, June 27th, 2024 at 4:38 PM, Mark Allyn < > [email protected]> wrote: > > > Folks; > > > > I am working on a sound analyzer for a museum exhibit. (Spark Museum in > > Bellingham, Washington) It will display the sound waves (like an > > oscilloscope) and the spectrum. > > > > I am performing this on Ubuntu 22.04 (Jammy). > > > > I tried to use pulse audio, but I notice that it runs free for about 1 > > second, then it pauses as if > > it's suspending or catching up it's buffer. I made inquiries on reddit > and > > I was told not to use pulse but to use pipewire. > > > > What has been your experience while either using pipewire's API or the > > pulse API under pipewire? > > > > Thank you > > > > Mark Allyn >
