LinuxMusicians

I think we can conclude that the timer based scheduling doesn't work reliably enough for pro audio macOS CoreAudio (and CoreMIDI) begs to differ. The concept certainly works very well on Linux as well for some hardware, not so much for other hardware. My behringer works very reliably with a 32 samp...

Do you have a rough idea as to when we might see that change? Are we talking about 2 or more years away, or are we talking about less than a year? I'm just looking for a rough timeline (nothing to hold you to). I'm wrapping up netjack2 support, I added ffado support and a jackdbus module... After t...

Thank you Wim for popping in!!! But it's more than: "You want the lowest possible latency with as little xruns as possible, I think we all understand the requirement..." It's being able to maintain that lowest possible latency with as little xruns as possible under a proper DAW workload. ...

I'm not going to be using Pipewire any time soon, in the same way that Wayland is the new thing but I still use X11. Another negative is that x42 expressed his reservations. That's not a good sign to me. But ... a lot can happen before version 1.0. Yeah. Pipewire could even become the nail in the c...

It doesn't matter whether you do this conversion in the server, or in client-linked code, It's the fact that it is being done at all. JACK does not allow clients to choose their own rate and depth. They must conform to the server settings. Uh? so you say that when a client, say mpv, wants to play a...

Pipewire's audio processing is a completely different codebase than Jack's. The former isn't designed to prioritize low latency. It prioritizes the mixing of various formats, sync audio to video, and a simpler, generic API for ordinary desktop apps. Folks who expect it to yield the same performance...