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

Eric Dantan Rzewnicki rzewnickie at rfa.org
Fri Sep 23 19:41:22 UTC 2005


On Fri, Sep 23, 2005 at 12:28:00PM -0700, Stephen Travis Pope wrote:
> 
> 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)?

There is definitely interest. See this recent thread from the LAU list:

http://lalists.stanford.edu/lau/2005/09/0376.html

-- 
Eric Dantan Rzewnicki  |  Systems Administrator
Technical Operations Division  |  Radio Free Asia
2025 M Street, NW  |  Washington, DC 20036  |  202-530-4900
CONFIDENTIAL COMMUNICATION
This e-mail message is intended only for the use of the addressee and
may contain information that is privileged and confidential. Any 
unauthorized dissemination, distribution, or copying is strictly 
prohibited. If you receive this transmission in error, please contact
network at rfa.org.



More information about the Linux-audio-dev mailing list