I want to use MIDI Translator Pro to send out a chain of MIDI messages (with a little delay between them) when a specific MIDI note is send by a hardware controller (DJ context).
I have made 3x Presets. 2x of them work just fine… so I think I basically understood how to do this.
With the 3rd I have the problem that 2x MIDI messages of the 9x in total are not outputted… they are simply missing (their Translators seem to not be performed at all).
Since I did everything exactly like with the other Translators… I have trouble understanding this and could not find a mistake I did or a reason why this is happening.
Could this be a bug?
My file is attached.
The problem is with the Preset “Scratch Doubling”
There the Translators:
“Mute Stems Left Deck” (Note 3-83)
“Serato Sync ON Left Deck” (Note 3-81)
are not being performed. Same is happening in the eqal programm for the right deck:
You seem to have ‘Stop Processing’ checked on most translators. This means that after they execute, the MIDI Translator Engine will not continue and will start again from the beginning. Most of the time, this should be unchecked.
The User Manual page 113 shows how the processing flow happens within Bome MIDI Translator Pro.
You seem to be accepting MIDI messages from all devices and sending them to all devices. It is best to target which MIDI devices are meant to trigger the transkator and where to target MIDI output instead of blasting all devices with all outgoing MIDI messages.
For more information about device selection, see this tutorial.
I suspect the first issue is what you are facing, however it is hard to tell with the various cascading perform actions, what the initial trigger is that you want to use to fire these two translators (2.5 and 2.7)
It also looks like you might have the wrong rule on 2.5 which is calling ‘Serato Link On Right Deck’. I suspect you want ‘Serato Link on Left Deck’.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
@SteveC thank you for your reply. Your view, on the situation I described, gave me helpful insight and I was able to understand the internal processing better, after I looked up the processing flow chart in the manual.
Shortly after I was able to track down the root of the problem. I had a translator with the same name in another preset (which was processed earlier in the processing flow), which caused the problem. After I renamed all existing translators with unique names (they all have the preset name in it now, so even if they do the same… the name is different now).