[linux-audio-dev] Re: [Jackit-devel] Re: (1) Jack -- busted? (2) jack.udp -- busted? (3) jack-osx -- binary-only?

[Stéphane Letz]

Le 23 sept. 05 à 21:28, Stephen Travis Pope a écrit :

>
> 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
>
>

There is a JackRTP project on source forge that was developed at  
IRCAM. I don't know exactly the status of the project right now, but  
it seems stopped.

http://sourceforge.net/projects/jackrtp

Regards

Stephane Letz