Quote:
Originally Posted by Geoff Waddington
Cool, now you can make your own file set.
For instance, here is the Reaper Action connected to the Marker button in the MCU.axt, which I think you are using:
Marker Reaper 40172
You likely want:
Marker Reaper 40171
which drops a maker at current position.
You can customize just about everything this way.
You first name the control and match it to an incoming press/release midi message in the .rst:
Marker PressFB 90 54 7f 90 54 00
Then you simply assign that control to an action in the .axt/.fxt:
Marker Reaper 40171
In this case it's a Reaper Action, but there are other actions -- you can see examples in the .axt files.
|
Comparing the MCU.rst to what I mapped from the X-Touch, most things are the same, but there are a few things using different values. For example, the jog wheel in MCU is b0 3c 7f b0 3c 00, but the X-Touch gives b0 3c 41 b0 3c 01.
I'm guessing the first step would be to copy the MCU.rst file, (rename to "X-Touch) and change any values that are different so they match the what the X-Touch is sending? Then I can also copy and rename the .axt file and customize the actions?
This makes a lot more sense now knowing there are unique numbers for every action in Reaper. Somehow I missed that during all this. Still not really clear on setting up sends/plug-ins, but we'll get there.
Thanks!