I want to control a handful of Eventide Factor boxes. First, I call up the preset, then I can send the other parameters. If I understand correctly, MTP processes all translators in parallel whenever possible. The devices buffer the incoming events, but I need to ensure that no parameters arrive before the preset is called. Perhaps it would be wise to introduce a time window anyway. Is it best to specify a delay for each output action, or is there another way to delay a group of translators within an MTP preset?
Hi, most outgoing actions have an option to add a delay. I assume your issue is whether a given Eventide box is ready to receive the new MIDI message when you switch presets.
I’m not sure how Bome MIDI Translator Pro would know to wait unless you just add a delay, however if the Eventide box responds to a given action with a MIDI message, then you could trigger that incoming MIDI mesage from Eventime to signal Bome MIDI Translator Pro thatthe Eventide box is ready to receive parameters.
In general there is an order to how messages are sent. See page 113 of the user manual.
The exception might be timers and perform actions where they happen more asyncronously. If calling perform in rules, then you can pass a delay argument to the perform translator and have it use that argument to delay the outgoing action. You could also do that with parameters in timers, starting with Bome MIDI Translator Pro version 1.9.2.
Maybe if you show an illustration of when this becomes problematic, I can provide further assistance
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
I have read these parts of the manual, although I did not fully understand them. At the moment, we are talking about the initial setup of devices. All translators have incoming ‘on activation of this preset’. For each device, a Program Change is sent first, followed by a handful of parameters. However, I’m not sure whether MTP really runs through all translators in sequence from top to bottom within a setup, even if no incoming actions change the timing, because there are practically none.
You can see what I mean at a glance in the screenshot:
The grouping makes editing clearer, because I have such a Preset for each piece of music, a “song”, if you want. At the beginning of each Translator group, the device’s program number is called up, followed by the activated parameter Translators. If this were done from top to bottom, I wouldn’t have to care about timing. But I’m not sure if that is how it works. That’s why I gave each Translator except the Program Changes an outgoing delay of 1 second. Time is not an issue, but order is.
Initially, I wanted to send the Program Changes first, then pause, and then send all the parameters. But I couldn’t find anything that said ‘now please do nothing for 50 ms’. I don’t have to wait for the loading time of the devices, but the Program Changes have to be sent first for each device.
(The screenshot above is a prototype; in the final version, the presets will have approximately twice as many translators. And I may separate the “on activation” translators from the relatively few playing-related ones at the bottom, so that I can disable the setup after execution.)