Paul Davis wrote:
> with jackd, they would be serialized so that they
execute one after the
> other. which core they run on is up to the operating
system for the most
> part.
>
> with jackdmp, it would depend how they were connected.
if it looked
> like:
>
> jaminA -----+
> jaminB -----+
> +----- ardour
> jaminC -----+
> jaminD -----+
>
> then jackdmp can run the 4 jamin instances in parallel.
how many will
> execute at one time depends on the number of cores.
which cores is again
> up to the operating system.
>
> if they looked like:
>
> jaminA -> jaminB -> jaminC -> jaminD ->
ardour
>
> then again, jackdmp can't parallelize. this is an
unlikely setup, of
> course, but this might not be:
>
> zyn -> freqtweak -> sooperlooper -> ardour
-> aella
>
>
>> If not (which I believe is the case anyway) what is
the purpose of
>> developing jackdmp if we do not have any
substantial advantages of using
>> it on the most jack intensive application around
(ardour)?
>>
>
> the point of jackdmp is not to parallelize the
internals of a client.
> its to parallelize at the jack level - clients - when
the connections
> between clients make that possible,
>
> --p
>
>
>
>
Thanks for the thorough description... I'll look out to the
jackdmp
release then!
Quentin
------------------------------------------------------------
-------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and
take
control of your XML. No limits. Just data. Click to get it
now.
http://sourcefor
ge.net/powerbar/db2/
_______________________________________________
Jackit-devel mailing list
Jackit-devel lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jackit-dev
el
|
