I’ve been banging my head against the wall for almost a week now. I have this issues that I cannot, for the life of my, figure out. Here’s what’s going on:
I have quite a few different translators that I’m trying to trigger at the same time, when striking key C4. They each do completely different things and one of them is a preset change to an Arturia Microfreak. I would like to hit key C4 and have it select a specific preset and do a number of other things (already successfully defined in other translators). The biggest issue I have is, when I hit that trigger key (C4), the preset change mutes all the other translators that run along side it, effectively rendering the whole stack of translators, as well as any sound from the Microfreak, essentially mute or choked. If I disable the preset change translator however, all the other translators seem to act as they should.
This makes me think that it’s something with the Microfreak, wherein some kind of micro delay would be in order, but I swear, I’ve tried everything. Any help would be very much appreciated! I honestly feel like I’ve tried everything and I’m starting to go a little insane. Hoping I’m just missing some very basic step somewhere…
Yeah, of course. For context, I’m using a Lauchkey 49 mk4 as my controller and controlling an Arturia Microfreak, using the ‘Settings’ feature on the Launchkey pads to switch between MIDI Channels for presets on the Bome, with the least amount of a acrobatics.
OK, which note number do you have configured for C4 in Bome MIDI Translator Pro. I see several translators with note 60 as triggers as well as a few with not 72 as triggers. I’m assuming you have Bome MIDI Translator Pro configure with note 60 as middle C (C4). Which translator are you referring to that does a preset change in Microfreak?
I fail to see any output that triggers a preset change, however.
Translators 0.0 and 0.1 do not have swallow set so the original incoming message will also go out to the destination. Is that intentional?
Preset 0 has default destination to both “BomeBox:BomeBox DIN” and “MicroFreak”, but the translators in preset 0 override that default and will only send to “MicroFreak”.
Translator 0.0 also calls out input from “Launchkey MK4 49 Out” but the preset already does that do it should not be necessary to call it out in the translator as well.
Preset 2 does not override your default MIDI ports of “Launchkey MK4 49 Midi Out” for input or “Microfreak” for output so that should be OK if that is where you want to monitor and direct your output.
For more information about device selection, see this tutorial.
Translator 1.14 is disabled. Maybe that is the one you want to use for the Microfreak preset change. Of course, if that will make the Microfreak change incoming MIDI channels then you will need to ensure that processes last if the other translators are meant to process before it. You might need a delay on the outgoing action of that translator if you want to process the other translators first.
Since version 1.9.1 of Bome MIDI Translator Pro, if I have a single trigger to perform multiple outgoing actions, I tend to lean to have one incoming translator with an outgoing “perform” action to trigger the various things I want to do. That way if I want to change the trigger, I can do it in one translator.
In some cases, Bome MIDI TRANSLATOR Pro will use parallel execution logic to speed thing up if there are several “like” triggers, so the order of the outgoing actions may not always be consistent (without adding delays). I can also use “perform” in rules to ensure the sequence of event happen in the right order.
Here is a tutorial about using multiple action from one trigger using “Perform”.
Here is a tutorial showing the use of “Perform” in rules.
Maybe if you describe the translators you are struggling with and the order in which you want to execute the outgoing actions? I think I know the first answer (note 60 on MIDI CH 2 incoming trigger translators), but not sure of the order you need.
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
I believe I am using note 60 for middle C (C4). As far the preset change side, there is no translator set up for the preset changes. I do that using the native Launchkey MIDI channel changing capabilities. It’s something I stumbled across, but it works really well and allows me to toggle back and forth between 4 or 5 different setups, fairly quickly.
Definitely not intentional. The incoming notes certainly clash with the programmed chord functions that I set up, so I certainly need to change those to ‘swallow’.
Translator 1.14 is disabled, but is definitely the one I was hoping to use and duplicate, once I got it up and running for preset changes. I believe I would need to delay the note information first, ever so slightly, for live purposes, am I correct? As an example, when the the chorus of a song hits, I would like the sound to switch to a different preset and, in order to achieve this, I believe I would need to have the preset switch ever so slightly ahead of the notes of said chorus, right? Is there a quicker way to achieve this, or is adding delays to the note information translators the best way to do this?
I’ve watched a myriad of tutorials, including the ones linked here, but I’m still struggling to understand how to properly use the ‘Perform’ outgoing actions. This seems like the ideal solution, but after watching the tutorials, I’m still not grasping it.
I am struggling with getting ANY preset change to occur without muting and choking the note information on parallel translators. Essentially, any time I have a preset change translator set to a note (note 60 - C4) where something else is set to trigger, the preset changes, but nothing else is allowed to happen (no notes sounds, etc.). It might be very simple, but it seems to me that the note info needs the slightly delay, effectively allowing the preset change to occur slightly ahead of the MIDI note information. Do I have that correct?
Thanks for your help Steve! It’s very much appreciated.
OK, so translator 0.0 will output chord-on and translator 0.1 is a chord-off.
Translator 1.14 also has the same input trigger and you want it to trigger a program change to the Microfreak.
I think triggering a program change on the Microfreak at the same time as triggering a chord will be problematic using the same input trigger as the MicroFreak will likely kill the playing chord.
Is this what you are running into? If so, this is a function of the Microfreak and we won’t be able to fix that with Bome MIDI Translator Pro .
Maybe you should trigger the program change on the note-off message instead, This will allow the chord to play until you release the key ad which point the program change would be sent,
Steve Caldwell
Bome Customer Care
Also available for paid consulting services: bome@sniz.biz
Yeah, that is exactly the issue I was running into. I think you are 100% correct that a program change killing the chord to be played is an issue with the Microfreak. I did a ton of digging and I’m pretty sure that’s it. I tried doing this on another synth I have and had zero issues with this happening, which I guess is my answer! At least I know I’m not just losing my mind! Thank you Steve. I’ll get creative and think of alternative to my workflow to get around this, as the Microfreak is ultimately what I would like to use…for now, at least. Really appreciate your input!