[OSC_dev] Managing different osc implementations

[Jamie Bullock]

On 20 Feb 2009, at 20:25, Sciss wrote:

> stupid question: why would you want to try to do in SuperCollider
> exactly what you do in Max/MSP? these system are so fundamentally
> different that i cannot imagine why i would need the same  
> addressing...
>

I was only using Max/MSP and SC as examples. The point is that there  
is functionality that is common to the range of Music-N derived  
languages for multimedia/audio programming, and libIntegra provides a  
way to define and address this functionality in a standardised way. It  
also provides a means to wrap functionality that is not common between  
environments and to spread module collections between environments so  
we can take advantages of their unique strengths.

SpectralDelay   <- standard module
|
SpecialEsotericSC3SpectralDelay <- inherits the interface of  
SpectralDelay but adds some special attributes unique to SC3.

The point is to standardise *representation* not to standardise usage  
or functionality.

Jamie


>
> Am 20.02.2009 um 18:13 schrieb Jamie Bullock:
>
>>
>> On 20 Feb 2009, at 14:56, Mr.SpOOn wrote:
>>
>>> Jamie Bullock wrote:
>>>> I suggest you have a look at our documentation:
>>>>
>>>> http://www.integralive.org/dokuwiki/doku.php/screencasts
>>>> http://www.integralive.org/dokuwiki/doku.php/
>>>
>>> I watched the screencasts and took a look at the slides. This  
>>> seems a
>>> really great project. And my idea is not original at all.
>>>
>>> Is it still active?
>>
>> Yes, it's very much active in fact 'round 2' of the project will be
>> starting in March.
>>
>>> What are the real difficulties in "bridging" other
>>> applications other than PD and Max/MSP ?
>>>
>>
>> There aren't any specific difficulties, it's just a matter of time.
>>
>>>
>>> Damian Stewart wrote:
>>>> every application that uses OSC implements the protocol in the same
>>>> way
>>>
>>> Reading this it seems to me that it should be an easy task.  
>>> Obviously
>>> I'm wrong, but I don't understand why.
>>>
>>> What am I missing?
>>
>> You're not missing anything. Except possibly that there are several
>> approaches being referred to here. I would call what Damien is
>> referring to as an 'ad hoc' approach. You simply define your OSC
>> addresses as needed on your OSC server(s) and send messages to those
>> addresses on the server from a given client. Simple!
>>
>> However, there are a number of approaches emerging: openmediacontrol;
>> oscit; Integra static methods; oscqs, which support a degree of
>> service discovery. In addition, the idea behind libIntegra is that  
>> you
>> could load a module in SuperCollider then load the same module in  
>> Max/
>> MSP and be *guaranteed* that it will have not only the same OSC
>> address space, but the same parameter ranges and units. It does this
>> by providing an abstraction layer between the client and the target
>> environment. It seemed to me that this was what your original  
>> question
>> was getting at, but maybe I'm wrong.
>>
>> Jamie
>>
>>
>> _______________________________________________
>> 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