Standardized namespace '/SYN/' for communication between controllers, synths and hosts

[masta_fabi]

Hello!
 
I had some thoughts about killing MIDI and transferring all the functions to OSC while upgrading and expanding them.
 
I introduced a standardized namespace within OSC, '/SYN/', which holds all necessary methods for communication between controllers, hosts and synths.
 
Here's my proposal:
 
http://stud3.tuwien.ac.at/~e0725639/OSC-SYN.txt
 
Still in beta stage, but I hope to get vast feedback.
 
Greetings
fabb
--
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
_______________________________________________
OSC_dev mailing list
OSC_dev@...
http://www.create.ucsb.edu/mailman/listinfo/osc_dev

[Joe Malloch]

Some parts of this message have been removed. Learn more about Nabble's security policy.

Fabb,

As I see it, your proposal does not make enough use of the biggest advantages that OSC provides over MIDI, including the ability to use strong semantics in variable names, real units, and floating point numbers

Unlike MIDI, OSC addresses can (and should) make sense - for example, instead of "/SYN/IDx/Vx/P1, Fi", you could use something like "/synth/x/voice/x/aftertouch etc"

I'm not sure why you wish to represent notes in a range of 0 - 2147483647... if anything, this is more confusing than remembering MIDI note values, and since no human would be able to hear any note between 1073741779 and 1073741899, it "wastes" 99.9999% of your range representing pitches that are inaudible. Why not use floating point to represent either frequency (Hz) or "MIDInote" with fractional values?

OSC also lets us remove weird offsets, for example, why not use something like "/pan/stereo 0." for centre?

I recommend checking out the Jamoma project for discussion of ranges and units: http://sourceforge.net/projects/jamoma/

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

On 9/20/07, masta_fabi@... <masta_fabi@...> wrote:

Hello!

I had some thoughts about killing MIDI and transferring all the functions to OSC while upgrading and expanding them.

I introduced a standardized namespace within OSC, '/SYN/', which holds all necessary methods for communication between controllers, hosts and synths.

Here's my proposal:

http://stud3.tuwien.ac.at/~e0725639/OSC-SYN.txt

Still in beta stage, but I hope to get vast feedback.

Greetings
fabb
--
Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten
Browser-Versionen downloaden: http://www.gmx.net/de/go/browser
_______________________________________________
OSC_dev mailing list
OSC_dev@...
http://www.create.ucsb.edu/mailman/listinfo/osc_dev

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

[Jamie Bullock]

Hi Fabb,

On Wed, 2007-10-03 at 10:10 -0400, Joseph Malloch wrote:

> I recommend checking out the Jamoma project for discussion of ranges
> and units: http://sourceforge.net/projects/jamoma/
>

Also the OCCAM MIDI address space:
http://www.mat.ucsb.edu/~c.ramakr/illposed/occam.html

And the Integra Yamaha DX7 address space (which includes MIDI
addresses):

http://www.integralive.org/development/resources/?fid=23

Since OSC has a built-in data type for for RAW MIDI (although not all
implementations support it), I agree with Joe that it seems slightly
pointless to devise an OSC MIDI namespace that isn't human readable.

Jamie

--
www.postlude.co.uk

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