Filter Out Stop Command That Is Carried with Program Change

Bome Products
1

Hi, I am trying to figure out how I can Achieve this.

I am using an RC-300 which can send program changes.

Along with the Program Change Command the RC-300 sends a Stop transport command.

I would like to filter this out however I use all the other Stop transport Commands that the RC-300 sends.

I only want the stop commands that are carried along with the program changes filtered out. The other stop commands need to stay as they are.

 

Is this possible with bome and if so how might I achieve this?

 

Thanks so much!

2

Yes, if you can turn on logging and send the exact data your RC-300 sends when sending program change with transport. Then provide me what the output looks like. I assume it send something like this:

C0 pp F0 7F qq 06 01 F7

Where pp is the program number, qq is the device ID and the string in bold is the Sysex for the MMC Stop Command.

If you use this as your input in a translator as raw MIDI and then output should just be

C0 pp

Then the rest of the message will be blocked but only when immediately following the program change.

Any other MMC stop command which is not part of the above pattern should go through untouched.

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

3

Hey Steve, i’ve attached a picture of bome using the midi capture function upon program change.


Attachments:
![](upload://aHCGbCnozSqxJarI3kDC2KhCW4A.jpeg)
4

Hmm, this doesn’t look like a Bome MIDI Pro translator log. I really need to see the raw hex code instead of the descriptions. Are you using something else other than Bome MIDI Translator Pro to capture the information?

5

Hey steve, this is from the capture midi function in a new translator profile in bome. I could get it from the event log ( probably what you need ) but because my looper sends clock it the program change hex disappears quickly drowning in clock code.

is there a way to view an extended history of the event log?

6

Yes, in the event log windows. Control-A will will select all test. Control-C will copy it to your clipboard and then you use Control-V to pasted it into a text file. Then save the text file and attach it as an answer (comments in this forum will not accept attachments).

If you are on Mac and not Windows replace Control with Command.

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

7

Hey Steve, this is what i get when I switch presets with only the MIDI In: toggled in the Log window. ( windows doesn’t have a text editor as far as i can tell esh. )

44: MIDI IN [USB2MIDI]: C0 04

It was preset 4 i switched to..
F8 fills up every line except when I change the preset.
45: MIDI IN [USB2MIDI]: F8
did it with my iConnect4+ interface too and just the device name is different

8

Aha, so you are not seeing the MMC Stop command, just the plain old MIDI stop command

 

You can try this and get back to me if it doesn’t work and as I also have another ID.

Assumption. Receiving on MIDI channel 1

Incoming Raw MIDI: C0 pp F8

Outgoing Raw MIDI : C0 pp

This will only work if timing is such that it immediately sends the stop command.

If there is a delay between the between the Program Change and the stop command it may not. In which case we can use logic to set a flag to ignore the first stop command after any program change.

 

Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz

9

Worked! thanks so much!

10

Great! Could you please marked as resolved?