Bome's Midi Translator Pro 1.7.2 15
Shamika Stimus
Hi, I want to make my Launchpad Pro as game controller like the above YT video.
When I open Bomes MIDI translator only, keystroke functions works fine.
but if I open Ableton Live for light effect, MIDI Translator stops working.
Hi, If you need more than simple MIDI routing (IE changine CH 6 to CH 1, then you need translators for that instead of just a simple line through as I showed. The simple line method is just for routing MIDI but not translating one MIDI message to another.
Yes, this is achievable. You will need to set up translators to track your current fader positions in global variables within a given preset. Then when switching presets, have the selected preset use the global variables and a repeating timer to iterate through and update your fader positions on your Platform M+.
Regarding this midi controller led feedback I was talking to you about I would like help with executors for example I have several pages on my lighting software and would want my page up button to flash at a certain rate to match the page the lighting software is on (page one is selected and the controller flashes once a second). I also have several different types of executors ones that you have to press to go through cues and ones that you just press.
Since Cubase does not allow to insert a specific effect when receiving a midi remote command, I have to use AutoHotKey to create script that would react to button in OSC that just inserts the effect on the channel.
To send a midi message to Bome you need to use a virtual MIDI port. On my MAC the server's console looks like this (see picture below). So, in my case, the target of different widgets must look like this:
midi:Bome MIDI Translator 1
In the future I was planning to use a second computer for my live performances. What happens is that in the first it would reproduce Ableton and in the second computer Resolume Arena. Do you know if I can send midi data from the first computer to the second via Ethernet?
I'm trying to send midi or key stroke signals from Ableton Live, thru Bome's, into Character Animator (CA). Does anyone know if it's possible for me to trigger something in Ableton live and simulaneously send the signal to CA to trigger my puppet? I can't seem to get CA to recorgnize any signals coming from Bomes.
Thank you for the feedback. Character Animator has 'MIDI Note' field assigned to every trigger. By entering a number in that field you are essentially telling CA which midi note will be used to initiate the trigger. I set it to the number #74 through #80, for different triggers in CA. You can see below how the Midi Note F# in Ableton, translates to the #74 in CA. In Bomes, I set my 'Incoming' trigger to MIDI 90 4A pp (Which translates to D5 on a keyboard). In my 'Outgoing' setting I set the MIDI exacty the same, 90 4A pp.
1. Remove the 1 midi command limit to controls. Most of the time I want 1 button to do more than 1 thing and as it stands I have to use Bome's to send out multiple midi notes or CC's then isolate them and map them to the multiple controls I want to use in Rekorbox. Similarly the next point applies here too, if I had modifiers I would have a shift button and if that mod was of a value set the same damn MIDI command would ignore one use and be applied in the other, instead of the shift key making the MIDI output different from the controller perspective.
There should be a way to load all samples from a folder to the sampler with a single click or drag and drop, if there is i haven't found it, then there should be a midi code to load folder or even just do it by playlist style savable lists, but it should be doable.
And also this would cause problems on the midi feedback side as the wonderful people @ novation decided upon the most user unfriendly structure for light manipulation i've dealt with. There is no "range" as such which outputs the seperate colours at a consistent brightness, they're spread across all the values and some are dimmer than others and some are flashing. The programmers notes don't make it much clearer either going on about ratios and the what-not, but my point stands that if using your system i used velocity in to output light colour here you would not get a recognisable scale of colours or dimmers, but actually get whatever that value happens to correspond to in launchpad land, without some heavy translation.
I feel your pain robbie, only just went to reprogram some stuff today & found i couldn't. I have come from traktor too & the midi possibilities there are much greater. (Actually the fx quality on traktor is better too. Keylock on rekordbox is far superior though.)
Sérgio, regarding Bomes: Bomes is amazing, best money i've spent on a program for ever, I love it. However, it's changed recently to make it more accessible and in fact more controllable in the last 2 verions 1.8.0+, i'm assuming you are above this version now on 1.8.1, but let me make the point clearly: Now, if you use the "simple Midi" interface and not the RAW midi from the dropdown you must make 2 seperate translations for most midi controllers 1 for note on and 1 for note off and translate them to the same "keystroke" in your case, this is probably why you only trigger the event every other press of your button, it sends a note on 9x xx xx and then a note off 8x xx xx the next time you press it. Normally you should direct these sorts of question to the Bomes forum where the community is amazingly helpful and knowledgeable but this needed to be done like this for me to answer you so no worries.
Tristan, i have and it's not gonna help you i don't think. It's the limitation of not having control of the message sent and the subsequent actual value. Basically until Pioneer give us a seperate midi out interface, if your controller needs values not of 127 or 7F in hex to turn it's LEDs a colour or even off, then you're buggered. it doesn't listen to note off inclusively so my work around has been to translate all 8x xx xx note off messages to note on's with 00 as their "velocity" for want of a better word. So my APC sends say 90 35 7F as it's note on and it then sends 80 35 7F as its note off; so that becomes 90 35 00 via Bomes and then back to the APC i intercept again this note on value of 00 and translate it to 80 35 7F and the light turns off. but this is really long winded and annoying for every button and if i want colours 00 from rekord box becomes 1,2,3,4,5 or 6 in Bomes and the note on can be a different colour this way too, but man it takes so long to setup.
if your controller has a seperate midi code for it's light to it's trigger messages it gets even worse as rekordbox then needs a manual mapping on it's out column and then it still needs translating to make it not provide 7F all the time...
I started mapping my Kontrol F1 to simulate a 4-deck system like others have done using Traktor Pro 2, yet, quickly realized I could not use pages and/or assign a pad to a specific deck to enable other pads/buttons to only work for that particular deck. As Robbie pointed out these are somewhat serious limitations: remove midi limit control, modifiers - shift functionality, need for pages, etc...
So, I am now on "Hold" mode with the F1. I also dusted off and old Numark DJ2GO and an AKai LPD8 which are simple enough products to practice the midi functionality on Rekordbox. Again, I ran into many issues. As an example, for browsing in the DJ2GO, I used the Browse, BrowseBack and BrowseForward commands within the Browse midi editing/capture area. When I proceeded to use the controller, my browsing would basically toggle between tree structures while using the BrowseBack ("Back" pad on controller) instead of going up in the tree menu of the music folders. The BrowseForward worked at times, yet, not always.
So, is there a document that describes what triggers pertain to the midi commands that have been established in the software? (since it seems I might be using [or mis-understand] them incorrectly ,and/or, these are not performing to the intent)
I am hoping the SW team addresses these key lack of functionality soon. Though I am not a midi-mapping expert as many others, please let me know if I can be of service (test out a couple of products) as you progress through the development and future updates.
One more thing - if you send a message to MIDICON - it will stop automatically - it's not broken - only when you receive a midi note - it switches to manual mode - so from then on you have to control the state of the controls from the software - for this preferably not to use midi OUT
MC.. can you see this is another person unhappy about the difficulty trying to control Totalmix ? the lack of user friendly midi and global OSC makes it very hard to work with at times.. it would be really beneficial if you could implement a standard midi CC mapping for all Totalmix functions and also global OSC control.. you did mention global OSC many moons ago, it would be good if you could consider it again ?
Cool, I've done in the past a similar approach on a midi engine (bome's midi translator) to sync software and hardware gear. Although I use a different approach ( calculate the clock pretty much like you did but I send a simple midi CC or sysex tempo change,which my hardware gear recognizes and changes the bpm) ,eventually I had a lag when jumping to large values e.g. : 80 to 150 bpm.
Old topic but I also use the X Touch Mini with a licensed copy of Bome Midi translator. I looked into using some of the helpful tips above but found them not for me by various reasons. I use vJoy to convert the output from Bomes rules/scripts to controller buttons and controller sliders instead of keystrokes. Kind of fidgety at first but works great with some work-arounds in both vJoy and Bome.
0aad45d008