Hi,
JACK knows the internal execution order of calls to client process()
methods, and it could measure the time.
A new option for jackd, like --measure that will log the calls and times
for each cycle in a compact format (that could be further analysed).
So it would be possible to get more information on limits for specific
setups and JACK "ecosystem" situations independently of client caps.
If this this doesn't exist already in some way, making it could help in
your case too.
Greetings
Tom
On Fri, September 19, 2014 22:44, Will Godfrey wrote:
Just trying to get a clearer understand so hope these
aren't too
noob-ish.
If you have several processes wanting to send audio, does the callback go
to all of them at (essentially) the same time, or does Jack poll them?
If the former, is it the quickest to complete that gets processed first?
If the latter, does Jack maintain the same order (assuming none stop) or
might it change between buffers?
I've a few more questions but they depend on whether either of these
scenarios is correct!
--
Will J Godfrey
http://www.musically.me.uk
Say you have a poem and I have a tune.
Exchange them and we can both have a poem, a tune, and a song.
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev