OSC integration

[joost.de.bot]

First of all, I’ve been using the Translater Pro for years with great pleasure.

Any news about OSC integration?
First, we had devices with just MIDI, then with MIDI and OSC, and now we also have devices with just OSC.

Has there been any progress in OSC integration?

[FlorianBome]

Hi, thank you for the nice words!
And sorry for the late reply. We are actually working on OSC support, but it (still) takes time. Current plan is to not integrate it into MIDi Translator Pro, but into Bome Network (and the BomeBox). OSC is a network protocol, so we think it’s a better fit.

Most discussion takes place here:

BomeBox upcoming OSC features

Hi @danny2, welcome to the Bome community And thank you for posting your interest in OSC. We at Bome have been talking about OSC support in the BomeBox for years (and even presented a running prototype), but finalizing it and making it universally useful for all relevant flavors of OSC, proved to be difficult. Now we’ve managed to develop and implement the necessary technology. We still need to integrate it into the BomeBox and create an editor for the Bome Network software. We…

You can click the bell icon to watch that topic for news.
Thanks!

[Newlin.Parker]

Quick Comment: Could not disagree more with that assessment. After looking at BomeNetwork and BomeBox(es), I can tell you that I have no use for any of that other functionality, but I have very specific needs for simply associating an incoming MIDI message to an outgoing OSC message in Midi Translator Pro, and this is the sense I get from reading others’ posts…

[FlorianBome]

Hi @Newlin.Parker , thank you for your comment. I do understand your disagreement. Our reasoning is mainly due to internal restrictions, which is not your concern…

On the other hand, I am persuaded that our implementation will address the needs of everyone who needs MIDI<->OSC translation. Some words of explanation (which, again, you may not find persuading… in the end, the product itself will speak for itself, I guess).

For us, integrating OSC translation into (any of) our products has been a long thought process. The issues we need to solve are:

1. OSC is widely open as a format with many different formats and conventions
2. OSC is a network protocol

Both do not fit well into MIDI Translator Pro’s (internal) architecture. I understand that from a user’s point of view, it seems so easy to add an Outgoing Action in MT Pro for OSC… But, either that would be very very limited, or we would have to revamp the entire internal architecture of MT Pro.

Conversely, the decision to integrate OSC-MIDI translation into Bome Network actually means that we do have a clear path towards implementation and release.

As a side note: Bome Network (BN) will become more and more a MIDI Router type of application, integrating different network protocols (Bome Network MIDI, Network MIDI 2.0, RTP-MIDI, OSC) and different types of MIDI processing (including running MT Pro projects). And many users already run BN alongside MT Pro, using virtual MIDI ports to connect them.

Last, but not least, the Bome Network architecture maps well onto the BomeBox, which will allow you to do all of the above without a computer. Maybe you don’t need that, but OSC is a top feature request of BomeBox users.