14 Sep
2017
14 Sep
'17
8:24 p.m.
JACK's "DSP load" measurement generally cannot go above 80% before issues
happen on almost all systems and platforms.
if the buffer size is 10msec, then the total time for JACK to execute its
own code and all clients needs to be below about 8msec.
On Thu, Sep 14, 2017 at 1:56 PM, benravin <ben.alex(a)outlook.com> wrote:
> JACK has
no requirements other than that you can run your process()
callback without
blocking, every time.
How much buffering needs to exist to make sure that can happen depends
hugely on what the non-RT part of things is doing. For comparison, when the
non-RT part does disk i/o, you need to be ready for potentially several
seconds of delay in refilling (or emptying) buffers. If the disk i/o
wasn't there, the buffering requirements would be much smaller.
I don't have any disk I/O operations, I receive data from a USB dongle at a
constant rate.
If I have 'N' clients running, then the time I can spend on each callback
for processing is
= (audio_buffer_period - ( process_time * N ) )
Is that correct ?
-ben
--
Sent from: http://linux-audio.4202.n7.nabble.com/linux-audio-dev-
f58952.html
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
https://lists.linuxaudio.org/listinfo/linux-audio-dev