Re: JACK rtprio=60, PipeWire rtprio=88: Why?

2024-02-15 Thread Wim Taymans
I think the main reason is that I was not aware of this policy and so we chose some random numbers. The parameters are configurable at build time and I can add these limits. Wim On Wed, Feb 14, 2024 at 7:30 PM Runiq via devel < devel@lists.fedoraproject.org> wrote: > Hey, > > I intend to pull

Re: Orphaned packages looking for new maintainers

2022-02-08 Thread Wim Taymans
reamer1-plugins-baseorphan, uraeus, wtaymans1 > weeks > > > ago > > > gstreamer1-plugins-goodorphan, uraeus, wtaymans1 > weeks > > > ago > > > > How did the gstreamer1 stack end up orphaned? Pretty much the entire

Re: pipewire memory usage

2021-12-14 Thread Wim Taymans
I can get it as high as that too but then it stays there and doesn't really grow anymore so it does not seem like it's leaking. Maybe it's the way things are done, there is a lot of ldopen and memfd/mmap. Wim On Mon, Dec 13, 2021 at 11:42 PM Dominique Martinet wrote: > Wim Taymans wrote on

Re: pipewire memory usage

2021-12-13 Thread Wim Taymans
There was a leak in 0.3.40 that could explain this, see https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/1840 Upcoming 0.3.41 will have this fixed. At least I can't reproduce this anymore with the test you posted below. Wim On Sun, Dec 12, 2021 at 12:49 PM Dominique Martinet wrote: >

Re: F35 Change: Switch to WirePlumber as the PipeWire session manage (late Self-Contained Change proposal)

2021-07-20 Thread Wim Taymans
Also, I forgot to change the status to ReadyForWrangler so it has been in limbo for a while. But meanwhile, we've been busy moving the parts into f35 for testing. Next step is to check all of the stuff we added to the old session manager and make sure we don't cause regressions. I'll update the

Re: PA module support in PipeWire

2021-02-23 Thread Wim Taymans
On Tue, Feb 23, 2021 at 3:13 PM Neal Gompa wrote: > On Tue, Feb 23, 2021 at 8:16 AM Kevin Kofler via devel > wrote: > > > > Lóránt Perger wrote: > > > I suppose I should have looked a bit more into this before opening this > > > thread, but oh well, no use crying over spilled milk. I looked

Re: Fedora 34 Change: Route all Audio to PipeWire (System-Wide Change)

2020-12-15 Thread Wim Taymans
Hi, > In particular I'm worried alsa programs will stop working. There is a pipewire-alsa package to support alsa programs > Shouldn't the alsa-plugins-pulseaudio also be compatible with pipewire's > pulseaudio implementation? It is but then you go through an extra layer of emulation, it's

Re: Fedora 34 Change: Route all Audio to PipeWire (System-Wide Change)

2020-11-25 Thread Wim Taymans
So, the current sentiment is: * provide an easy way to test in f33, either copr or with regular packages. - rawhide is a not a good place to get good testing anyway * encourage people to test. Provide instructions on how to do this and how to leave feedback. * Carry this over to f34,

Re: Fedora 34 Change: Route all Audio to PipeWire (System-Wide Change)

2020-11-25 Thread Wim Taymans
Hi all, First of all, thanks for the comments, keep them coming. We have seen these concerns many times before with big infrastructure changes like pulseaudio or wayland or systemd. I think they are necessary to keep our feet on the ground and not get carried away by our pipe dreams (pun

libvpx 1.3.0 ABI break

2014-03-13 Thread Wim Taymans
Hi all, libvpx-1.3.0 unexpectedly broke ABI without updating the .so name. See more info here https://bugzilla.redhat.com/show_bug.cgi?id=1068664 I'm rebuilding the gstreamer 0.10 and 1.0 packages now but there are more packages depending on libvpx. Wim