23 Sep
2005
23 Sep
'05
5:28 p.m.
Hello again,
I just answered question (2) about jack.udp when I realized that
recv.c is #included in jack.udp.c (and itself includes packet.c).
(I teach a graduate course on digital audio development, and this
just made it onto the list of "don't ever program like this.")
Perhaps some more background would be helpful. I started to look at
this after someone on the CLAM list mentioned the remote socket
streaming protocol we use in the CREATE Signal Library (CSL, see
http://www.create.ucsb.edu/CSL). We are currently discussing moving
from UDP to TCP, and I'm interested in actual user experience with
jack.udp. I notice that the server and client both fail and exit at
the first sign of trouble (like out-of-sequence packets).
There was some network traffic a couple of years ago about this. Is
anyone using this regularly?
Is anyone interested in collaborating on a common sample streaming
protocol (possibly based on a somewhat simplified version of SDIF or
the SC3 protocol)?
stp
--
Stephen Travis Pope -- http://create.ucsb.edu/~stp
Center for Research in Electronic Art Technology, University of
California, Santa Barbara
Really—I don't know what the meaning or purpose of life is.
But it looks exactly as if something were meant by it. — C.
G. Jung
Begin forwarded message:
From: Stephen Travis Pope <stp(a)create.ucsb.edu>
Date: September 23, 2005 12:10:15 PM PDT
To: "The Linux Audio Developers' Mailing List" <linux-audio-
dev(a)music.columbia.edu>gt;, jackit-devel(a)lists.sourceforge.net
Cc: Stephen Pope <stp(a)create.ucsb.edu>
Subject: (1) Jack -- busted? (2) jack.udp -- busted? (3) jack-osx
-- binary-only?
Helo all,
(1) I'm new to jack (but a competent programmer). It appears that
the cvs repository is missing the top-level configuration file.
Following the instructions from the download page, I do a clean cvs
checkout on a Linux machine, cd to the jack directory, and execute
./autogen.sh
This fails saying
/usr/bin/m4: configure.in: No such file or directory
configure.ac: 218: required file `config/ltmain.sh' not found
Am I missing something?
(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?
(3) I know that there's a binary distribution of the Mac OSX
release, and have it installed; does anyone know where there's a
source distribution?
stp
...any assistance greatly appreciated...
--
Stephen Travis Pope -- http://create.ucsb.edu/~stp
Center for Research in Electronic Art Technology, University of
California, Santa Barbara
Really—I don't know what the meaning or purpose of life is.
But it looks exactly as if something were meant by it. — C.
G. Jung