Yeah RT is probably the easiest thing to type...Carly(Poohbear) wrote: ↑30 Oct 2017First thing lets name the maps so we know which maps we are talking about.
ReasonTalk maps or RTs maps, those are maps we produce and manage
Tim's maps, Come straight from Nektar
Ch knobs are the pitch of individual steps it displays the note# on screen. I would put Velocity on faders reason being 0-127 and you can control 8 steps in one go as opposed to only controlling 2 steps at the same time with finger/thumb.
Any map that picks up grab in error will have to be rewritten to the old system. You have to completely stop play back in order to grab on the maps that have movement europa/grain EnvPo, step Steps. I have not tested grab on VST but I'd reckon iZoptope Iris2 and FabFilter Twin2 will be picked up on grab in error also because both use modulation that ghost moves knobs on the VST.
You tell the map to use the new grab system by naming the of the device
Code: Select all
Map Device Name "_Step" HOME
Code: Select all
Map Device Name "Step" HOME
So that is the reason why those maps that pick up grab in error will have to be rewritten to the old system.
X5 is the only spare button so that could switch faders to X1-4. Velocity for steps (x1)1-8, (x2)9-16, (x3)17-24, (x4)25-32. Width for steps 1-8, 9-16, 17-24, 25-32. Repeat for steps 1-8, 9-16, 17-24, 25-32 each press of X5 could display X1-4 to new pages. The width would be great on the faders but also the global width on fader 9 as well as the global velocity on fader 9 when each are selcted would work out good. The mode and repeat have less to change to so they might be better suited to encoders. Mode 4 states Repeat 8.
Perhaps X1 pitch steps 1-8 second function X1 pitch steps 17-24. X2 pitch steps 9-16 second function pitch steps 25-32 on the ch knobs. I would use 16 steps mostly. You gain the 2 extra X buttons which could be mapped to shuffle, offset etc.