Re: Adjusting Pipewire Jack Buffer Size

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 21 Feb 2024 at 11:06, Fons Adriaensen <fons@xxxxxxxxxxxxxx> wrote:
>
> On Wed, Feb 21, 2024 at 02:03:41AM +0000, MS lists wrote:
>
> > I just use:
> > PIPEWIRE_LATENCY=“128/48000” <your app>
>
> Does that mean that each Jack app can have its own buffer
> size and sample rate ? That completely destroys Jack's
> process model - that there is no buffering and hence delay
> between clients.
>

No, All clients always have the same buffer size. PIPEWIRE_LATENCY is only
a suggestion, the buffer size of the graph (and all clients) will be changed
when allowed and possible.

PIPEWIRE_QUANTUM=128/48000 is less of a suggestion and forces the
graph (again for all clients) to the quantum and sample rate, as if jack_bufsize
and (the would be nice but doesn't exist) jack_samplerate were called before
the client is started.

Wim

> Ciao,
>
> --
> FA
>
> _______________________________________________
> Linux-audio-user mailing list -- linux-audio-user@xxxxxxxxxxxxxxxxxxxx
> To unsubscribe send an email to linux-audio-user-leave@xxxxxxxxxxxxxxxxxxxx
_______________________________________________
Linux-audio-user mailing list -- linux-audio-user@xxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to linux-audio-user-leave@xxxxxxxxxxxxxxxxxxxx




[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux