Saving midi mapping in reason?
Saving midi mapping in reason? Posted on: 09.11.2011 by Charise Severs not sure if this is in the right place but here goes. just got an mpd off a mate and can having some problems i can map the knobs and faders to reason using the ...edit remote override mapping... but my problem is that i want to change different synths live using the knobs on the combinators to change frequency and resonance and that kind of thing live. is it possible for me to assign the knobs on my mpd to four differnt knobs on a combinator , and then select another combinator and use the same mpd knobs to control another combinator? atm i have to change the mapping everytime i want to control a different synth which is useless live. and whats worse i dont know how save mapping either. please help! i cant find the answers anywhere | |
| Charise Severs 09.11.2011 | not sure if this is in the right place but here goes. just got an mpd off a mate and can having some problems i can map the knobs and faders to reason using the ...edit remote override mapping... but my problem is that i want to change different synths live using the knobs on the combinators to change frequency and resonance and that kind of thing live. is it possible for me to assign the knobs on my mpd to four differnt knobs on a combinator , and then select another combinator and use the same mpd knobs to control another combinator? atm i have to change the mapping everytime i want to control a different synth which is useless live. and whats worse i dont know how save mapping either. please help! i cant find the answers anywhere |
| Chasidy Heckenbach 10.11.2011 | as for "wiring up" first u need to teach it about the mpd u have using learn.exe which will then create you a file like "devices/my-mpd.lua" then u need to create one for reason in devices/reason.lua which contains the midi u want to send out and what to call them, simpler than it sounds, have a look at devices/traktor.lua for how i do that - at least u don't need to create a matching tsi create a virtual midi device called something like "MM to Reason" - i guess u only need communication from the mpd to reason and not vice versa? then in your config/reason.lua (which is the file you'll tell midimasher to load) you'd need these 2 lines to attach the 2 devices: Code:
open_midi_device("reason", "reason", "", "MM to Reason");
open_midi_device("mpd", "my-mpd", "MPD-midi-devname", "MPD-midi-devname", 6);
you'd ofc need some way to "change page/layer" from your mpd, i can help u with that. you could use some fader or pot but a button or two would be easier. even simpler would be to use the top 4 pads "midi fighter 4 banks style". in fact if u did that u wouldn't even need to "teach" midimasher what midi u want to send to reason - just make your mpd emulate a midi fighter and then map that midi to reason. probably the simplest. then in theory a config like this would be all u need: Code:
open_midi_device("reason", "generic", "", "MM to Reason");
open_midi_device("mpd", "my-mpd", "MPD-midi-devname", "MPD-midi-devname", 6);
virtual_midifighter_4banks("mpd", 0, "reason", 0, 0, 127, 0)
running debug.bat would be helpfull as you'd then see if midimasher is doing what it should be |
| Chasidy Heckenbach 10.11.2011 | last time i used reason it saved all the midi setup with the song i was working on - not sure what version that was tho. |
| Charise Severs 10.11.2011 | cheers but how would i wire it into reason? and everytime i open reason up i need to set everything up is there a way to save a mapping in reason? so its all done for me when i open it up |
| Chasidy Heckenbach 10.11.2011 | some middleware software like my midimasher maybe? that could then give your controller multiple pages that each send out different midi data? then map each page to what u need. or something like bomes etc could work too. |
<< Back to Reviews of DJ equipment Reply