[OSC_dev] newby osc address question

Joseph Malloch joseph.malloch at mcgill.ca
Fri Oct 17 00:15:48 PDT 2008


Gaspard,

You could have a look at Remy Muller's oscbonjour:

http://recherche.ircam.fr/equipes/temps-reel/movement/muller/index.php?entry=entry060616-173626

And also the OSC-based mapping system we built in the IDMIL - we use a
multicast bus to handle instance registration and other administrative
traffic, after which messages can be sent peer-to-peer using the
instance name instead of IP and port. We only have a Max/MSP
implementation working currently, but the ICMC and LNCS papers linked
on the webpage might be interesting for you:

http://www.idmil.org/software/mappingtools

Joe

Joseph Malloch
Input Devices and Music Interaction Laboratory
Schulich School of Music - McGill University
email: joseph.malloch at mcgill.ca
web: http://www.music.mcgill.ca/~mallochj



On Fri, Oct 17, 2008 at 2:57 AM, Gaspard Bucher <gaspard at teti.ch> wrote:
> I understand, so this means the mapping to the first target (if I want
> them to be on different networks) has to be done inside the app
> sending osc messages.
>
> This means I should transform the message "/venus/met" to [send "/met"
> to host "venus"] and find my own way to get the IP for "venus".
>
> Is this correct ?
>
> Gaspard
>>
>>
>> Gaspard Bucher wrote:
>>> Hello !
>>>
>>> I am going to use osc for the communication protocol between the UI
>>> and  processor for rubyk (an open source patcher written in C++).
>>>
>>> Design ideas: http://rubyk.org/65
>>>
>>> My question:
>>>
>>> I would like to address the different objects inside rubyk instances
>>> (processors) through urls like:
>>>
>>> "/[instance name]/[object name]"
>>>
>>> For example a metronome object named 'met' running inside rubyk
>>> instance "venus" with IP 1.2.3.4 would be addressed as
>>>
>>> "/venus/met"
>>>
>>> This means the actual IP address of "venus" must be automatically
>>> discovered or set by the user (if it's not on the same LAN).
>>>
>>> Is this a misunderstanding of osc addresses ?
>>>
>>
>> Yes - the OSC address has nothing to do with the IP address. They are
>> completely separate things.
>>
>>> Should it be more "/1.2.3.4/venus/met" ?
>>>
>> No
>>
>> You will need to have your app that sends the OSC message send an OSC
>> message to 1.2.3.4 or the broadcast IP address on a particular port.
>> You will need to have 1.2.3.4 monitor that port and look for messages
>> with OSC address of /venus/met
>>
>> --
>> Dr Angelo Fraietta
>> A.Eng, A.Mus.A, BA(Hons), Ph.D.
>>
>> PO Box 859
>> Hamilton NSW 2303
>>
>> Home Page
>>
>>
>> http://www.smartcontroller.com.au/
>>
>> There are those who seek knowledge for the sake of knowledge - that is
>> CURIOSITY
>> There are those who seek knowledge to be known by others - that is
>> VANITY
>> There are those who seek knowledge in order to serve - that is LOVE
>>     Bernard of Clairvaux (1090 - 1153)
>>
>> _______________________________________________
>> OSC_dev mailing list
>> OSC_dev at create.ucsb.edu
>> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev
>
> _______________________________________________
> OSC_dev mailing list
> OSC_dev at create.ucsb.edu
> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev
>


More information about the OSC_dev mailing list