| ♥ 0 |
I am using Akai’s MPD232 and sadly the step sequencer buttons aren’t MIDI. The user denoiser found out the SysEx messages they send in this topic ( https://www.bome.com/forums/viewtopic.php?t=2818 ) and that got me wondering if this is possible: can you translate the SysEx message the button sends and translate that into MIDI CC# so that I can use the buttons to control Reasons Redrum steps? Or so that I can map the buttons at all in Reason? disclaimer: I am completely new to all of this and am just figuring out what can be done, thank you for your time and advice. Marked as spam
|
Posted by |
Private answer
Hi betabob, I realise this is an old thread but I’m in the process of trying to create a template for the 232 in Reason and I wondered if you had any success with getting the step sequencer buttons mapped? I’m very new to mapping in general and especially programs such as Bome, MIDIox etc so any help you could throw my way would be greatly appreciated. Thanks Martin
Marked as spam
 Posted by martin.gardner (Q&A Forum: 0, Answers: 2) June 22, 2018 7:58 pm
|
|
|
Private answer
So if your MPD is putting out the following Sysex for each control as shown in https://www.bome.com/forums/viewtopic.php?t=2818 Unlock (unlocks mpd to send sysex on port4 for every button/pad/fader): F0 47 00 36 30 00 04 01 00 00 38 F7 Then use Reason Remote Override feature to create your own mappings with output messages cc of your own choice. Assuming the MPD232 is not listed as a Standard Mapping.
Marked as spam
 Posted by Steve-Bome Forum Moderator (Q&A Forum: 27, Answers: 1892) April 12, 2017 10:41 pm
That’s the problem though, where, or how do I do that? I can remote map everything except the buttons listed above. I am trying to get the buttons above recognized in reason. For example: for Step 1, let’s say hypothetically I want it to be set to Pattern A. I’ve set my remote override to Step 1 (I don’t have a CC number though b/c the step buttons aren’t recognized as MIDI on the controller)
In my remote map I have
Map Step 1 Run
in my redrum section.
Then in my lua script I tried defining Step 1 as
{name=”Step 1”, input=”button”}, //to name
{pattern=”F0 47 00 36 31 00 04 01 0B 0E xx F7”, name=”Step 1”, value=”1”}, //to recognize
but that doesn’t seem to work. I know it’s also only sending the above SysEx on Ch4 but I can’t get anything to work on that Channel in Reason.
I’m having a hard time what to do with the list of SysEx above and how to get them to work for me.
OMG, I think I figured it out. The hex from denoiser wasn\’t what I was getting. I used this for step one: F0 47 00 36 40 00 02 18 xx F7 instead (found via MIDIox) and I could finally map it in channel four, now I just need to get my pads working in the same channel, which shouldn\’t be an issue. Thanks for helping! (oh and before anything happens I have to send my mpd the unlock code (F0 47 00 36 30 00 04 01 00 00 38 F7) via send sysex, gonna see if I can have this automate later instead of having to do it manually everytime.
ps: I’ll have a custom mpd232 codec (built upon the mod32) one soon if anyone is interested.
You can set up a translator to send raw midi message from MT pro on project open if you like. You can also set it up so that maybe an Escape key from your computer keyboard, or another midi type controller on you MPD triggers it. You would just set it up so that MT Pro sends it only to you MPD. I usually have a translator on project open that start and Init timer. |
|
|
Private answer
Converting incoming sysex to outgoing cc, program or notes is certainly possible with MT pro. In order to do this you need to determine the specific input that will need to be converted, evaluate the current incoming sysex messages and what makes each one unique and the write rules to use the unique portions into valid midi output messages. If you can provide an example of say 2 messages to convert, I can assist on this forum as an example and then you can use this to create other translations. If you want a complete solution you can contract directly with me to assist. Just sent a email to bome@sniz.biz. Steve Bome Q&A Moderator and Independent Bome programming specialist.
Marked as spam
Posted by Steve-Bome Forum Moderator (Q&A Forum: 27, Answers: 1892) April 12, 2017 6:41 pm
I guess that’s part of the question I haven’t fully understood yet. According to MIDIox and the user denoiser the sysex messages I would need are these.
F0 47 00 36 30 00 04 01 00 00 38 F7
This one unlocks the mpd232 to send sysex on port 4 for every button. (importantly the non MIDI ones)
Then as an example:
F0 47 00 36 31 00 04 01 0B 0E xx F7
this SysEx toggles the button Step 1 in the sequencer. (the only thing that I know of that defines this button)
What I don’t know is what to convert it in to. I’m assuming I’ll need to send that info to the .lua codec I’m using in reason to recognize my controls.
An excerpt of code recognizing the buttons in the codec:
function remote_init()
local items={
{name=”Keyboard”, input=”keyboard”},
{name=”Fader 1”, input=”value”, min=0, max=127},
{name=”Rewind”, input=”button”},
}
remote.define_items(items)
local inputs={
{pattern=”b0 0C xx”, name=”Fader 1”},
{pattern=”F0 7F 7F 06 05 F7”, name=”Rewind”, value=”1”},
}
remote.define_auto_inputs(inputs)
end
So I need to figure out how to define a ”Step 1” button? Not sure where to go from here.
Thanks for the quick response and helping out!
|
Hi Martin,
I can probably help but I would need to know specifically what incoming Sysex message from MND232 is and what MIDI message Reason would be looking for in it’s place.
If the inputs are as I documented earlier, just give me one example how how you would want it mapped in Reason, and I should be able to put a test case for you to try.
Steve Caldwell
Bome Q and A Moderator and
Independent Bome Consultant/Specialist
bome@sniz.biz
Hi Steve,
Thank you for the reply, I managed to get in contact with betabob who help me get this resolved. Thank you very much for your time I really appreciate it!