23 Sep
2005
23 Sep
'05
6:23 p.m.
Hi,
On Friday 23 Sep 2005 21:35, Eric Dantan Rzewnicki wrote:
On Fri, Sep 23, 2005 at 12:10:15PM -0700, Stephen
Travis Pope wrote:
Distributing jack interests me, but sadly I have no time to dive deeper at the
moment.
Jackudp had a sibling called udpsync (not sure about the source heritage)
which, instead of connecting two jacks through the client-interface (which is
prone to sync problems) drives the "slave" through the backend. It does
work, but is by no means finished.
Don't know if it's of interest, the latest sources are here anyway:
http://sourceforge.net/projects/netjack
Regards,
Robert
--
http://spamatica.se/musicsite/
(2) My actual interest is in looking into the
jack-udp protocol, and
I tried getting this all to work on a Mac a few days ago and actually
got much further, but it looks like file recv.c has problems since it
doesn't appear to include any definition if the jackudp_t data type
that it tries to declare in the first line of code; i.e., I get,
/Users/stp/Code/jack/jack.udp/recv.c:14: error: 'jackudp_t'
undeclared (first use in this function)
Does jack.udp work in general?
Is there any documentation of the actual protocol used?
Has anyone thought of using TCP instead of UDP?
Alban Peignier uses Rivendell with jack for radio broadcasts. As I
understand it he uses jack.udp to send the audio from the broadcast box
to a separate box that does encoding for web streaming. So, there is at
least one working use case.