[OSC_dev] SYNoscopy (or something like it)

[Gaspard Bucher]

I know of a midi message format (type tag "m" in oscpack) that just
wraps midi messages (4 bytes: port / status / data1 / data2) in OSC.
The "status" thing implements a mixture of the type of message (4bits)
and the channel (4bits). Details can be found here
(http://www.planetoftunes.com/sequence/messages.html). If you just
need MIDI over OSC, I think it's a good idea to use this format.

For a "standard" on where to send the midi information and things like
this, we are working on a minimal protocol that should ease
connections between applications (automatic or user based). Some of
the work can be found on http://rubyk.org/en/oscit (minimal protocol,
zeroconf) and another part is at http://openmediacontrol.wetpaint.com/
(media application control). These researches should finally merge
when we have implementations to test and discuss about.

Hope that helps,

Gaspard

On Mon, Jan 26, 2009 at 6:08 PM, Jeff Glatt <jgglatt at roadrunner.com> wrote:
> I'm planning on writing a developer library that implements some sort
> of OSC-based "standard" that replaces MIDI. As someone previously
> mentioned, you currently can't use OSC for anything but a proprietary
> protocol because there are no standardized set of messages (like
> MIDI's Note-On, Note-Off, Program Change, Controller, etc, messages).
>
> So, I was taking a look at this SYNoscopy specification (because what
> I'd need to do is what this specification proposes). First of all, is
> there any device/software currently implementing/using this particular
> spec? Secondly, since there are aspects of the spec that I think could
> be changed for the better (ie, make it easier, and more efficient, to
> actually implement in software), I'm wondering where is the best place
> to discuss them. There is a message board on the SYNoscopy site, but
> it has only 1 message that looks to be dating back to 2007. Is that
> board active? There looks to be some other site where people leave
> comments, but the formatting makes it very difficult to follow, and
> without any reply threading, it's really hard to determine who is
> commenting on what.
>
> Is this list better for discussing a full OSC replacement for MIDI?
> _______________________________________________
> OSC_dev mailing list
> OSC_dev at create.ucsb.edu
> http://lists.create.ucsb.edu/mailman/listinfo/osc_dev
>
>