1 Aug
2008
1 Aug
'08
10:29 p.m.
any ideas as to how long before we can hear any info on this thing you
are working on? will it be compatible with jack? or is it possible to
expand netjackmp to allow communication between arbitrary nodes
without sending the audio signals to the master node and back out
again? i thought it was possible to do this with the netjackmp
implementation but as i said i don't know much on the actual technical
abilities of it.
porl
2008/8/2 Fons Adriaensen <fons(a)kokkinizita.net>et>:
On Sat, Aug 02, 2008 at 01:02:07AM +1000, porl sheean
wrote:
if there was an open standard for this sort of
thing that we could
implement in software and interface directly with jack etc then it
would make my idea redundant.... i would love to see such a thing
though :)
I'm working on such a thing, or at least a variation of it.
what does netjack (or netjackmp) lack compared to
these
implementations? i'm still not entirely sure of netjack's
synchronising abilities for instance.
Netjack AFAIK is point-to-point, while cobranet is more of
an 'audio bus' where all nodes can talk to each other in
any combination as long as their is enough capacity.
It has a controller node where you request bandwidth, and
which provides timing information for the data you want to
send, relative to the periodic sync packet is sends itself.
Everything is planned to avoid collisions on the network.
Links can be broadcast or point to point.
Ciao,
--
FA
Laboratorio di Acustica ed Elettroacustica
Parma, Italia
O tu, che porte, correndo si ?
E guerra e morte !