Re: OSC_dev Digest, Vol 45, Issue 1

[Langsam Wieder]

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

Joe,

Thanks for your reply. ATM I get to nothing (started studying, moved...). I didn't find the discussion at the jamoma project's site, can you give further directions or post a more specific link? Thanks.
I just used integers because they are faster to calculate with and there are no rounding errors when adding / subtracting. But maybe float would be better, who knows.
"/pan/stereo 0." for centre sounds good but then the negative values would have to be used for panning left. That's what I wanted to avoid, I wanted to use the positive side for absolute values and the whole range for relative changes to be able to access every point with a relative change.
Whatever, at the moment I have no time and will to keep on working on this. If you find something useful in it, take it, if not...
greetings
fabb
 

Message: 5
Date: Wed, 3 Oct 2007 10:10:22 -0400
From: "Joseph Malloch" <joseph.malloch@...>
Subject: Re: [OSC_dev] Standardized namespace '/SYN/' for
       communication   between controllers, synths and hosts
To: "Developer's list for the OpenSound Control (OSC) Protocol"
       < osc_dev@...>
Message-ID:
       <be2afad20710030710s65ae344cq3e181408ba2dcc2@...>
Content-Type: text/plain; charset="iso-8859-1"

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

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

[Robin Davies]

> From: L Wieder
> I just used integers because they are faster to calculate with and there
> are no rounding
> errors when adding / subtracting. But maybe float would be better, who
> knows.

But integers aren't faster to calculate with. No modern software synth uses
integer math. So any integer parameter is immediately going to get loaded
into the FPU, and then you have to add and multiply to scale it into useable
range.

As for rounding errors, if your pan range is 0 - 2147483647, what's the
center position value? Ooops. 1073741823.5. Looks like a rounding error to
me.

Surely, one of the major points of OSC is human friendlines. If machine
friendliness was the point, it would look a whole lot different.

MIDI is evil. Possibly one of the worst things that ever happened to
computer music. And integers are evil too. imho.


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

[IOhannes m zmoelnig]

hi.

i changed the subject.
"list digest, vol#x, issue #y" is only slightly better than "(no
subject)" imho.

L Wieder wrote:

> "/pan/stereo 0." for centre sounds good but then the negative values
> would have to be used for panning left. That's what I wanted to avoid, I
> wanted to use the positive side for absolute values and the whole range
> for relative changes to be able to access every point with a relative
> change.

hmm, do you mean a semantic disambiguation based on the range of a value?

why not use the whole range for relative changes AND the whole range for
absolute values.

just because values are absolute (non-relative), does not mean they have
to be absolute (as in abs(x))

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