[OSC_dev] OSC replacement for MIDI
Jeff Glatt
jgglatt at roadrunner.com
Fri Jan 30 23:46:29 PST 2009
>i'd recommend 4 ways to get every need covered
4 different ways to do the same thing? You don't happen to be
a government employee, fabb?
But seriously... too complicated. There's no reason to make every
single product handle 4 possible formats that may be thrown at it, and
to translate every single one to the one it wants. I chose the one
common denominator -- the most efficient, most versatile, and most
basic. (And the one that allows any tuning, completely transparently).
Frequency. (Although I'd be just fine with "period" instead. Instead).
If you don't like frequency, then you just translate it... once. You don't
have to worry about also translating 2 additional formats you don't want
either. And you don't have to try to figure out what someone else wants
when you generate a message. Everyone gets the same thing. You don't
have to say "Device 1, do you want a cent offset? No? You want a note
number? Ok. Device 2 do you want a scala ratio? No? You want a
frequency? Ok, hold on, I have to take this cent offset I just received, and
convert it to the scala ratio I want. Oh damn. Someone just threw a note
number at me. I've got to translate... Oh hell, who's the wise guy who just
gave me a frequency? I forget -- who ordered the pastrami on rye? And
who has the salad with low fat dressing?. Oh the hell with this. I always
wanted to be dancer instead.".
As you'll note, I also jettisoned all of the other "If T, this means it's
this
format, but if F, this means it's the same thing in some other format"
stuff you had in your original proposal. It needed to be more uniform
as a standard.
Everyone gets the same thing. That's what a standard is at its core.
More information about the OSC_dev
mailing list