![]() Test the Mute buttons on the controller and in Reaper, are they synced? ![]() Test if the movement of Track faders in Reaper feed back their values to the LED circles of the X-Touch-mini Encoders ![]() Test if Volume Encoders on X-Touch-mini controller will move the Track faders in Reaper "Realearn_XTouch-mini-Tracks-Mute-Volume-Transport" Realearn_Preset_XTouch-mini-Tracks-Mute-Volume-Transport.RPLĪfter import select the new preset from the drop-down-list In the FX-Window of ReaLearn press the button - Import preset library. Open or create in Reaper a project with 16 audio tracksĬreate a 17th track via Track - Insert virtual instrument on new track. REAPER\UserPlugins\FX\ReaLearn\ReaLearn.dll Into the Editor and press the button "Dump B" XTouch-mini_LayerB-absolute-fan-togglebuttons.bin Into the Editor and press the button "Dump A" XTouch-mini_LayerA-absolute-fan-togglebuttons-and-transport.bin Install X-Touch-mini Editor for Windows V1.21 Master-Volume-Fader (no LED-Feedback inbuilt, hence no "motor-fader-like" behaviour on this one fader possible.) Set Mute-State in 16 Channels via Controller or Reaper-GUI, state sync in both directions Move 16 Channel Faders in Reaper via mouse and feed the values back into the Encoders in X-Touch-mini, represented by LED circles Move 16 Channel Faders in Reaper via the 8 Encoders in X-Touch-mini Layer A, plus 8 Encoders in Layer B The X-Touch-mini is well prepared to simuate Motor-Faders with its endless encoders and LED circles.Īfter many wrong attempts here a successful solution for feeding back the track volume and track mute states back to X-Touch-mini, so that changes made in reaper GUI are reflected at the controller LEDs, just like one would expect from motor faders.Ĭheap "motor faders"-like performance for Reaper with X-Touch-mini.
0 Comments
Leave a Reply. |