Midi OSC

Hello everyone!
My idea is to use Bome to pass MIDI <> OSC.
But first of all I want to tell you that I am really new to this software. I come from Osculator !.
My question or request is if someone could explain to me (with a simple example) how to understand the process.

I have read the whole manual and I have not found anything about it.

For example:
A) Where I put the destination server and  Receive?

I think you should create two Present’s, one output and one input

B) where I enter the destination statement; e.g.  /layer1 /clip1 /connect

These answers would be very useful to me to understand the operation of this software

thx a lot
Marked as spam
Posted by (Q&A Forum: 1, Answers: 1)
June 26, 2017 9:07 am
Private answer

Thanks and I’ll try!

A question; Where do I assign the ip / port (in & out)?

Thx a lot


I see it a bit confusing!!!!! 😉


Marked as spam
Posted by (Q&A Forum: 1, Answers: 1)
June 27, 2017 7:24 am
I would imagine the input IP address would be the IP address of the host computer running MT Pro. You could set up the device as whatever midi input device/port that you want within MT Pro. Probably Bome Virtual Port 1. The output port would be the actual midi device on your computer you are controlling. If it is an application then you have to go one deeper and set up a virtual midi output port and then set that up as your input port in your application. I’m really not that familiar with how OSCillator works. and how to expose IP ports to it. MT Pro by itself would not do this.
( at June 27, 2017 4:01 pm)

I believe you need an application on the host that can act as an OSC client. Bome MT Pro software currently does not do this. I would suggest searching more on OSC on this site and maybe you can find someone that has an OSC client loaded that converts network OSC messages to OSC sysex messages which can then be converted by Bome to mide cc’s etc. I’ll poke around as well.

( at June 27, 2017 7:16 pm)

Bome is working on OSC support and I believe they showed a prototype at NAMM in January. No word on when it will be released however. Reaper has OSC support so you could probably use that as an OSC Server of sorts. I also saw references to PureData amd Max/MSP. Once we get the OSC input into some sort of Midi Sysex format, then converting to Midi CC is pretty simple. I would ask about an estimated release date of MT Pro or Bomebox with OSC, but historically Bome does not pre-announce anything. We will see it when it is available.



Independent Bome Programming Specialist

Bome Q&A moderator

( at June 27, 2017 8:19 pm)

Thx Steve!!!
It is very good news that BOME has OSC in the future.
For now I will use Procesing and OSCP5.
Thank you so much

( at June 28, 2017 10:18 am)

Yes, in the meantime, I think I will experiment with Pure Datat (pd) and see if I can get it to listen for OSC and the forward on to a Bome Virtual Midi port. I just downloaded pd yesterday.

( at June 28, 2017 2:51 pm)
Private answer

My understanding is OSC does the following

  1. Take the OSC and convert from character (ASCII) data to Hex
  2. Convert it to Sysex by putting F0 at beginning and F7 at the end

So the resulting sysex for the above would be

F0 20 2F 6C 61 79 65 72 31 20 2F 63 6C 69 70 31 20 2F 63 6F 6E 6E 65 63 74 20 F7

where the first 20 hex  is the first space character befor the slash and the last 20 hex is the space after  the t in connect

This would be the input in  your case.

For the output, you could assign it a note,  a cc, or a preset with a given velocity(for note) or  value (for cc or PC).


To do the reverse you would need to construct your required OSC message converting to Sysex and have the midi message trigger the OSC (Syesex) output.


Hopefully this will get you on your way.





Independent Bome Programming Specialist


Bome Q&A moderator




Marked as spam
Posted by (Q&A Forum: 38, Answers: 3212)
June 26, 2017 3:34 pm