![]() |
#1 |
Human being with feelings
Join Date: Nov 2023
Posts: 4
|
![]()
Hello everyone,
I'm trying to see if I can use Reaper for band rehearsals and live performances, but I just can't figure it out. I'm hoping someone give me some tips. I got 3 tracks set up running NAM (neural amp modeler). I'm trying to switch these with an Amazon/Aliexpress USB 3 pedal footswitch. Without installing any sketchy Chinese drivers, the footswitch is putting out the letters A-B-C like a keyboard. I got it working with autoarm when selected, and "select track" assigned to the letters, but I quickly discovered there was a substantial time gap between switching tracks. I then read it would be better to use mutes to prevent this issue. Selecting 2 tracks, grouping them with one mute selected, and then selecting mute lead/mute follow in the menu seemed to improve things, but I can't get this to work with 3 tracks. I then tried to set up liveconfigs and I downloaded a bunch of mute options from reapack, but same story here, I can't get the tracks to switch. I assigned the A-B-C to apply live config 1-2-3. I then put a track in each live config and hit mute all but active track. This doesn't do anything. I then tried to add mute commands to 'activate action' but can't seem to figure out how to even get them added in there. At this point I don't know what else to try, I just don't know what I'm missing/doing wrong. |
![]() |
![]() |
![]() |
#2 |
Human being with feelings
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 14,164
|
![]()
I suggest asking HelgoBoss in his Thread on ReaLearn.
Otherwise it can be done by some JSFX programming: JSFX in focus receives key strokcs -> sends Midi CC messages -> MidiToReaControlPath routes them onto the Reaper Control Path -> LiveConfigs receives them -> and mutes/unmutes the tracks. Supposedly a script with a dedicated window also could be crafted. AFAIU, assigned actions would permanently block those letters which does not seem appropriate. If you can assign "weird" keys by that driver, this might be an easy solution. Last edited by mschnell; 11-21-2023 at 12:51 AM. |
![]() |
![]() |
![]() |
#3 |
Human being with feelings
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 14,164
|
![]()
I tested and got it working by setting in ReaLearn.
- two "Mappings" for two keys ("1" and "2" - selecting "Project Invoke REAPER action - Absolute 7 Bit - "SWS/SM Live Configs #1 apply config - Target min and max = 1% with "1" and 2% with "2" (results in selecting config lines 1 and 3 appropriately) - "Fire on Press" -> "Press only" |
![]() |
![]() |
![]() |
#4 |
Human being with feelings
Join Date: Jun 2013
Location: Krefeld, Germany
Posts: 14,164
|
![]()
Problem:
ReaLearn uses (and optionally blocks) key presses even if the ReaLearn Window does not have the focus. This might be inappropriate with certain applications. |
![]() |
![]() |
![]() |
#5 |
Human being with feelings
Join Date: Nov 2023
Posts: 4
|
![]()
here's a writeup of all steps required to make this work. huge thanks to mschnell for helping me sort this out.
required are 2 add-ons to Reaper which need to be downloaded: 1) SWS Extension (this is an installer) 2) Realearn 2 by Helgoboss (a dll file, put this in program files/common files/VST3) things to set up: - create a track and call it Realearn, hit "record: disable input (input monitoring only)". in the fx, you should load Realearn. arm this track at all times. - this example uses 3 tracks with an amp modeler with different presets, so we need to create more tracks and add the fx. - create sends from the track with realearn to every other track, this can be done by dragging the route button from track 1 to the others. - assign the input in Realearn (in this case "computer keyboard") - create 3 mappings in Realearn, and set the sources (the letters A, B and C in this case) - then we need to set the target. select type: "project: invoke reaper action". invoke needs to be set at "absolute 7-bit". action should be set at "SWS/SM: Live Config #1 - Apply config (MIDI/OSC only)". below, the button control should be set at "press only". these settings are identical on all 3 mappings. - each mapping needs to have a different target % setting to control the different controller values in Live Configs. with this pedal I used 1, 2 and 3%, entered in both min and max settings. this will control controller values 1, 3 and 4 in Live Configs respectively. in Live Configs: - we only need to use Config #1, so don't make 3 separate configs. this particular step would've saved me many hours. - under "tracks", assign your 3 tracks to controller values 1, 3 and 4. - in options, set "mute all but active track" - things should be working now, but there will be a substantial delay between switching mutes, so the last thing to do is to turn down the controller smoothing and tiny fade setting. This is all there is to it. |
![]() |
![]() |
![]() |
Thread Tools | |
Display Modes | |
|
|