Re: [Jack-Devel] netjack2 device discovery

PrevNext  Index
DateMon, 03 Sep 2012 17:58:03 +0200
From Stéphane Letz <[hidden] at grame dot fr>
ToLeonardo Gabrielli <[hidden] at univpm dot it>
Cc[hidden] at lists dot jackaudio dot org
In-Reply-ToLeonardo Gabrielli Re: [Jack-Devel] netjack2 device discovery
Look at JackNetXXX kind of code in jack2/common/ (excluding JackNetOneDriver which netone stuff)

Stéphane 

Le 3 sept. 2012 à 17:36, Leonardo Gabrielli a écrit :

> Stéphane, Thank you very much,
> 
> I'm now reading the readme included in the git repository. Where is this implemented in code? From a brief browsing through jack2/common/ I couldn't easily find where this initial "handshake" is performed.
> Best regards
> 
> Leonardo
> 
> 
> On 09/03/2012 04:34 PM, Stéphane Letz wrote:
>> It is a complete ad-hoc mechanism with a simple connection protocol : the master module (server side) uses a multi-cast address, and listen on it. Slaves  when starting, send a "Available" packet on this address, then server send back a "parameters" packet, then slave use the "parameters" packet to configure itself and establish the real audio connection.
>> 
>> Stéphane
>> 
>> 
>> Le 3 sept. 2012 à 15:57, Leonardo Gabrielli a écrit :
>> 
>>> Dear all,
>>> on jackaudio.org it is said that netjack2 implements a device discovery through the network. How is this performed? How is it
>>> practically obtained when invoking netjack? I couldn't find information about that on the internet, not even in this wiki http://trac.jackaudio.org/wiki/WalkThrough/User/NetJack2
>>> Regards
>>> 
>>> Leonardo
>>> 
>>> 
>>> Jack-Devel mailing list
>>> [hidden]
>>> http://lists.jackaudio.org/listinfo.cgi/jack-devel-jackaudio.org
>> 
>>      
> 
PrevNext  Index

1346687892.21812_0.ltw:2,a <1A24777A-82B5-41E3-995F-41EC9CAD1BEB at grame dot fr>