Re: Keyboard Controller Keys vs Voices (Joseph Malloch)

[werteplus]

As an aside, I find there is a weird obsession with MIDI-style control
in this discussion - everyone keeps talking about "keys" and
"velocity" etc. As a contrary example, many of the "source devices" we
use with the mapping tools (gestural controllers in this case) are
capable of sending 50-100 parameters *at the same time*, many of which
are continuous. I think creating genuinely useful tools for OSC
mapping requires thinking outside the MIDI-box :)

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

yes, i'm obsessed with midi. or better said: i'm obsessed of thinking how osc could replace midi completely.

with midi gear, you go in a shop, buy a synth & a controller, connect them and play. ha! now do that with osc.
how should companies ever produce gear with only osc support when they know there's no minimum standard interface they can use and the end user will need a 100+ pages user manual how to set up his gear to work as expected.

a "note on/off" message would be such a minimum requirement among some other things, at least in my opinion.

there's where device classes (+ version numbers) with according standard name spaces; (or a class for a group of parameters) would get handy. the controller sees the destiny and its class and says "hey, i know how to talk to you" and then it autolinks all/some of its parameters to that destiny. when there's only one fitting destiny, it could get mapped instantly and when there are more, it could ask the user (or use the history of its last connection).

i don't want to limit the possibilities of osc either, and those device classes could just be an addition. a destiny could also have several classes + some unclassified parameters.

maybe it's too early.

greetings,
fabb

_______________________________________________
OSC_dev mailing list
OSC_dev@...
http://lists.create.ucsb.edu/mailman/listinfo/osc_dev

[Stephen Sinclair]

On Tue, Jan 20, 2009 at 3:07 AM,  <werteplus@...> wrote:

>> As an aside, I find there is a weird obsession with MIDI-style control
>> in this discussion - everyone keeps talking about "keys" and
>> "velocity" etc. As a contrary example, many of the "source devices" we
>> use with the mapping tools (gestural controllers in this case) are
>> capable of sending 50-100 parameters *at the same time*, many of which
>> are continuous. I think creating genuinely useful tools for OSC
>> mapping requires thinking outside the MIDI-box :)
>>
>> Joseph Malloch
>> Input Devices and Music Interaction Laboratory
>> Schulich School of Music - McGill University
>> email: joseph.malloch@...
>> web: http://www.music.mcgill.ca/~mallochj
>
> yes, i'm obsessed with midi. or better said: i'm obsessed of thinking how
> osc could replace midi completely.
>
> with midi gear, you go in a shop, buy a synth & a controller, connect them
> and play. ha! now do that with osc.
> how should companies ever produce gear with only osc support when they know
> there's no minimum standard interface they can use and the end user will
> need a 100+ pages user manual how to set up his gear to work as expected.
>
> a "note on/off" message would be such a minimum requirement among some other
> things, at least in my opinion.
>
> there's where device classes (+ version numbers) with according standard
> name spaces; (or a class for a group of parameters) would get handy. the
> controller sees the destiny and its class and says "hey, i know how to talk
> to you" and then it autolinks all/some of its parameters to that destiny.
> when there's only one fitting destiny, it could get mapped instantly and
> when there are more, it could ask the user (or use the history of its last
> connection).
>
> i don't want to limit the possibilities of osc either, and those device
> classes could just be an addition. a destiny could also have several classes
> + some unclassified parameters.
>
> maybe it's too early.

I was going to point out that there is information on the OSC web site
about wrapping MIDI inside OSC, but I just checked it to discover that
2 of the 3 links on that page are broken and the third is re-directed
and seems to contain little information about MIDI->OSC as advertised:

http://opensoundcontrol.org/wrapping-other-protocols-inside-osc


Steve
_______________________________________________
OSC_dev mailing list
OSC_dev@...
http://lists.create.ucsb.edu/mailman/listinfo/osc_dev