Hi there,
Just a quick pre-sales question about Midi translator running on a bome box:
Is it possible to take the incoming midi clock BPM, reduce it by a specific number of BPM and output the resulting BPM to a specific computer connected via bome network midi ?
For example, the incoming BPM on the bomebox input port would be 120 BPM, midi translator should reduce this BPM by 4 and output 116 BPM to a specific computer on the bome network.
Is this possible?
Many thanks!
Hi @Toby
Unfortunately the precision of MT Pro is in milliseconds (whether on computer or BomeBox) so adjusting incoming MIDI clocks for exact BPM is not always possible. It is best to use a reliable adjustable BPM clock source that has the precision that you need and then in BomeBox set up a static MIDI route to the device you want to operate at that BPM.
Steve Caldwell
Bome Customer Care
Hi Steve, thanks for your answer.
Maybe I can give you a little more information about what Iām trying to achieve? I actually own two BomeBoxes (one on stage and one at our FOH mixer). The FOH Bome receives midi clock as well as midi patch changes and routes them to our stage equipment and also to Waves LV1 (software mixer) @ FOH which should run tempo-based effects. The problem is that for whatever reason, LV1 registers the incoming midi clock around 4-5 BPM faster than what itās actually receiving. Iāve notified Waves about this and they admit itās a bug, but seem to be taking their time to fix it.
In the meantime I had hoped I could somehow offset the incoming (correct) midi clock and feed it to LV1.
The reason I canāt globally adjust the midi clock from the source is that all other devices in the setup receive the clock correctly, itās only LV1 that needs adjusted midi clock.
Maybe you have a suggestion?
Many thanks,
Not unless Waves LV1 can do itās own internal MIDI clocking and maybe we send some sort of MIDI message to signal the Waves to resync itās internal clock.
This seems to be a pretty serious issue. I wish I had a better workaround. Maybe Waves can provide a workaround until this can get fixed?
Steve Caldwell
Bome Customer Care
You might look into the MIDI Hub.
It can generate itās own clock at a given BPM, Maybe you can use MT Pro or BomeBox to signal it to start and stop clock at a different BPM.
Steve Caldwell
Bome Customer Care
Thanks for putting me onto the MIDI Hub, it looks like an interesting device, which might work.
The LV1 bug is certainly a serious one. I hope waves fixes it soon.
The other idea I had was to use a USAMO (Expert Sleepers - USAMO) fed with the adjusted tempos from a spare audio channel on the Cymatic uTrack 24 which is driving the show (where the correct Midi clock is coming from). This midi signal could be fed directly into LV1 via a separate usb midi interface. I -think- I can select a second midi interface in LV1, have to check the manual.
One other question, can MT Pro remove or filter Midi Clock from a midi signal? If so, I could then replace the midi clock with the adjusted midi clock from the USAMO, keeping all other midi information from the original midi signal in tact.
Yes, it is quite easy to filter MIDI clock messages with a project file running on computer or BomeBox.
Just a single translator with clock in as the trigger and no outgoing action.
Steve Caldwell
Bome Customer Care
Ok, that sounds like it might work.
Unfortunately Waves replied and said they still arenāt sure when the bug will be fixed and couldnāt suggest any current work-around. Oh well, letās see.
Thanks a lot for your help Steve!
Of course,
You might want to ask Blokus if it would work for your use case for the MIDI Hub. They have a forum for this at blokus.io
Steve Caldwell
Bome Customer Care
So due to the delay, Iām sure yāall figured this out, but the way I worked around it was by mapping the tap tempo to Bome and then triggering it with MIDI messages from Ableton and having it give 4 beats anytime a tempo changes so itās not getting a constant tap tempo.
Hi Matt, thanks for replying! Can you give me some more specific instructions on how you did it? So youāre saying you send a Midi note or controller pulse every time there is a tempo change? And this is mapped to LV1ās tap tempo function?
Many thanks!
Yes, so from Ableton, make sure Sync is turned off on your MIDI output so itās not sending MIDI clock to LV1 and then what I did was have a simple MIDI note (I chose F#7) trigger in Bome to send over a Raw MIDI:
90 59 7F
90 59 00
That will trigger the tap tempo button. It locks in after 2 but I have for notes trigger at the start of a song. After that you can just drop that MIDI clip into any song you want tap tempo locked in.
On the LV1 side, I set up a Mackie Control surface and pointed it to the network I sent out from Bome.
Legendary!
Iām not using Ableton, and I use an external Midi clock generator, but I will use Bome Translator to remove the Midi clock before it hits LV1.
I will give it a shot an report back with my findings.
Hi Matt, I finally had a moment to try this out.
I managed to get it working when Bome Midi Translator is open on the same pc that is running LV1. But it only seems to work when I use the Midi Translator Virtual ports for both the output of the translator project and the input of the Mackie Control in LV1.
I created a virtual midi port called āTap Tempoā in Bome Network so that Iād have a dedicated midi input for it. The Mackie will select it, but when I load the project to the bomebox, the tap tempo is not triggered.
I also noticed that all my bomebox routing dissapears when I load the translator file into the bomebox. I thought those two things were different?
Any ideas?
Hi @Toby
When you load a project on BomeBox, MIDI routing of the BomeBox is overridden by the project file loaded. It is best to set up aliases in your project that pertain to the ports on your BomeBox with the routing that you desire (using MT Pro MIDI router) and then when the project is loaded on BomeBox, assign the aliases as you like for how you want routing on BomeBox.
Steve Caldwell
Bome Customer Care
Hey Steve,
Thanks for the help! I went into the MT Pro project and assigned the routing as you suggested, but Iām still not getting any MIDI coming into LV1. Iām a little stuck here.
I have MIDI being sent out of Logic into the Bomebox (āFOHā) which should then be translated into Raw midi Tap Tempo signals and received by the (virtual) Mackie Control in Waves LV1.
I created a virtual midi port for the Mackie in LV1 called āTap Tempoā, see some screen shots below:
I then did the routing in MT Pro:
With these settings in MT Pro:
I get no signals anywhere for some reason. I occasionally managed to get it working by keeping MT PRo running and changing the mackie ports to MT PRo Virtual, but that doesnāt seem solid and I should be able to achieve this on the bomebox standalone, right?
If you have any further guidance, that would be a big help. Iāve been at this for a few days nowā¦
Many thanks!
Hi,
What is the routing for your newly created āTap Tempā port on your computer?
When you create virtual ports with āUnlimited Named MIDI Ports,ā only the endpoints are created but there is no routing between the endpoints.
So in the Bome Network MIDI tool you need to set up a route that looks like this.
Then any MIDI going into āTap Tempo Virtual Inā coming from Bome MIDI Translator Pro will go to āTap Tempo Virtual Outā which is received by LV1.
For more information on how this works, see this post in Tips and Tricks.
Steve Caldwell
Bome Customer Care
Hey all,
I never managed to get it working using the bomebox to send the raw midi. Seeing as Iām using logic, I worked out a way to generate the raw midi in a .mid file and simply drop it on the logic timeline at beat intervals. Sending the midi to LV1 then worked perfectly!
Iām attaching the midi file for 1 beat here in case anyone else wants to use it!
The annoying thing is, I have been in contact with Waves for several years and they have confirmed the tempo mismatch is a known bug. Unfortunately they do not seem to care enough to fix it. Interestingly, the tempo works flawlesly on their SuperRack softwareā¦
Anyway, I hope this solution helps some people.
raw_midi_tap_tempo.mid.zip (286 Bytes)
