25 Sep
2005
25 Sep
'05
9:49 a.m.
Hi,
On Sunday 25 Sep 2005 05:43, Stephen Travis Pope wrote:
Netjack sounds interesting, but the SourceForge site
has no code and
no forum postings.
Perhaps this is a case of starting a project by claiming the spot on
SourceForge...
The code is there, but it's only in cvs, there are unfortunately no releases
made on that site yet (says a little about the lack of maturity).
As for the technical merits I see that the discussion has been more about the
transport mechanism and this project hasn't really touched on that subject
yet. To keep it simple the data is sent via udp with floats directly.
For lowlatency, CPU-hungry, work the interesting bit is that there is a master
jack-server that drive all slave jack-servers, thus working around the sync
issues.
A drawback of this is that its only (easily) allowed to connect an actual
soundcard to the master jack-server, the others are best suited for various
processing tasks (Outboard effects, softsynths).
Regards,
Robert
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: Robert Jonsson <rj(a)spamatica.se>
> Date: September 23, 2005 1:23:28 PM PDT
> To: linux-audio-dev(a)music.columbia.edu
> Cc: Stephen Travis Pope <stp(a)create.ucsb.edu>du>, jackit-
> devel(a)lists.sourceforge.net
> Subject: Re: [linux-audio-dev] Re: [Jackit-devel] (1) Jack --
> busted? (2) jack.udp -- busted? (3) jack-osx -- binary-only?
>
>
> 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:
>>> (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.
>
> 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/
--
http://spamatica.se/musicsite/