Announcing ReaLearn: Sophisticated MIDI/MCU/OSC learn for REAPER

[helgoboss]

Originally Posted by Sound asleep

I just tried doing some recording, and the relative mode didn't record properly. The width control moved correctly when I wasn't recording, but it would only record at 2 extremes. The absolute function worked ok, but unfortunately for me, my controller has a terrible rate of movement in absolute mode, which can only be adjusted in relative mode with step-size function in this plugin, which means I'm shit out of luck for this, unless maybe I get another controller sometime.

Could reproduce it, will look into it. Little translation: It's not recording, it's writing automation. With the "Track pan" target it works, it's just the new "Track width" target that has this issue.

[Sound asleep]

Originally Posted by helgoboss

Could reproduce it, will look into it. Little translation: It's not recording, it's writing automation. With the "Track pan" target it works, it's just the new "Track width" target that has this issue.

What I meant by "not recording" is "not writing automation". It looks like you're right. The pan worked normally, just pan width wasn't automating correctly.

[Arthur McArthur]

Originally Posted by helgoboss

This is how I understand you: You want a button that kind of "activates" the selected track's EQ, meaning that as soon as it's activated it can be controlled by one of your controllers. Also, you want the EQ to be automatically added to the track if it doesn't exist yet. Right?

At the moment you can achieve that by using a combination of a pretty simple ReaScript (triggered by ReaLearn at the press of a button) and ReaLearn's "Auto-load preset" feature. The script (or maybe can even be done using a custom REAPER action) would take care of opening the track's EQ, e.g. in a floating window and adding it in case it's not there. ReaLearn's "Auto-load preset" feature would react to the EQ being opened and automatically load the EQ preset.

OK so I got this figured out by using a script as you suggested, in combination with conditional activation! I mapped one button to run the script, as well as set the program for the script. Here's the script I hacked together from a few sources: it inserts a user-defined FX with a user-defined preset if none exists on the track and floats it to a specified position. If there is already one of these FX but the GUI is closed, it opens the GUI. If the GUI is already open, it closes it.

--Insert FX, select preset, float to location, or close/open GUI if already in track

FX = "Pro-Q"
preset = "4 bands & filters"
x  = 850
y  = 400
spacing  = 0 -- Added to x and y for each FX

reaper.Undo_BeginBlock2(0)
    
-- Create a table with all currently open windows, so that newly opened FX windows can be distinguished

a = reaper.new_array({}, 1000)
reaper.JS_Window_ArrayAllTop(a)
t = a.table()
t1 = {}
for i = 1, #t do
    t1[t[i]] = true
end 

TrackCount = reaper.CountSelectedTracks(0)
track = reaper.GetSelectedTrack(0,0)
fxidx = reaper.TrackFX_AddByName(track, FX, 0, 0)
    
if fxidx >= 0 then 
    
    IsVisible = reaper.TrackFX_GetOpen(track, fxidx)
      
if IsVisible then
    reaper.TrackFX_Show(track, fxidx, 2)
    return
    end
end    

if fxidx <= 0 then   

    -- Now add FX (if not already in track chain) and open FX window
    
    for t = 0, reaper.CountSelectedTracks(0)-1 do
        track = reaper.GetSelectedTrack(0, t)
         index = reaper.TrackFX_AddByName(track, FX, false, 1) -- 1=only add if not yet already in chain. -1 to always add
         reaper.TrackFX_Show(track, index, 3)
         
        --set preset
        
             fxnum = reaper.GetFocusedFX()
             reaper.TrackFX_SetPreset(track, fxnum, preset)
    end
    
      -- Find all newly opened windows, and move them to x,y coordinates
      
    a.resize(0)
    reaper.JS_Window_ArrayAllTop(a)
    t2 = a.table()
    for i = 1, #t2 do
    address = t2[i]
    if not t1[address] then 
         hwnd = reaper.JS_Window_HandleFromAddress(address)
             if reaper.ValidatePtr(hwnd, "HWND") 
             then
             reaper.JS_Window_Move(hwnd, x, y)
             x, y = x+spacing, y+spacing
           end
       end
    end
end 

reaper.Undo_EndBlock("Insert FX Plugin",-1)

I'm very happy with this workflow at the moment, cheers and thanks again!

Originally Posted by helgoboss

This sounds even more like a job for scripts because it's full of conditions ("if the receiving track doesn't exist", "if the send doesn't exist"). If this is a use case that pops up again and again with many users, I would consider to make this a built-in function - but at the moment that sounds way too specialized. Or do you have a good concept in mind how to integrate it into ReaLearn's existing range of targets?

Here's the use case I'm thinking of in this regard: you save a track template with ReaLearn on it that has some sends and send controls mapped in ReaLearn. When you open this template again, if the order of the sends has changed or they are on different tracks, the send control mappings now point to the wrong tracks. So I think I can refine this request further to: a "By Name" option for the track sends, instead of them pointing to a track number. Would this work?

On another note: I'm creating a controller preset for the Novation Launchkey 61 MK2 but I'm having a hard time creating correct feedback mapping to light up the pads. I can set one to trigger the light of another pad, but not the same pad that I'm actually pressing. It seems like it sends the feedback color if I hold the pad down, but as soon as I release- the pad it clears itself. I think it's because the pad sends a note on and a note off, and once the note off is received, it resets. So is it possible to block the note off from the pad? Or do you think that is something happening internally in the keyboard itself? Here's the reference guide: https://resource.novationmusic.com/s...ence-guide.pdf

[ChrisDN]

Just been following section 6.3.3 of the user guide, to the T... "Right-click ReaLearn's header panel and press Link current preset to FX".

That option never appears in the context menu.

Any further suggestions? Please and thank you!

[helgoboss]

Originally Posted by Arthur McArthur

I'm very happy with this workflow at the moment, cheers and thanks again!

Great!

Originally Posted by Arthur McArthur

Here's the use case I'm thinking of in this regard: you save a track template with ReaLearn on it that has some sends and send controls mapped in ReaLearn. When you open this template again, if the order of the sends has changed or they are on different tracks, the send control mappings now point to the wrong tracks. So I think I can refine this request further to: a "By Name" option for the track sends, instead of them pointing to a track number. Would this work?

Created a FR (https://github.com/helgoboss/realearn/issues/169). I remember this has been requested before.

Originally Posted by Arthur McArthur

On another note: I'm creating a controller preset for the Novation Launchkey 61 MK2 but I'm having a hard time creating correct feedback mapping to light up the pads. I can set one to trigger the light of another pad, but not the same pad that I'm actually pressing. It seems like it sends the feedback color if I hold the pad down, but as soon as I release- the pad it clears itself. I think it's because the pad sends a note on and a note off, and once the note off is received, it resets. So is it possible to block the note off from the pad? Or do you think that is something happening internally in the keyboard itself? Here's the reference guide: https://resource.novationmusic.com/s...ence-guide.pdf

If this device doesn't just work with feedback (without further ado), it means that it uses different MIDI messages for control than it uses for feedback. This is not a problem because ReaLearn processes feedback completely independent from control. That means you can separate the control mappings (only control enabled) from the feedback mappings (only feedback enabled).

There are multiple ways of finding out which MIDI messages the controller expects. One way is the reference guide. The one you posted is really good. Wish every controller would have that. Another good way is to experiment by just sending some MIDI notes to the device to the device to find out which pad responds to which MIDI notes - as you have done already. You can do that completely without ReaLearn already. the ReaMIDIControl log function could also be useful in this respect.

Concerning your question about blocking the note off, even it's possible, it's not the way this is supposed to be used. Feedback works like this: You enable track solo in REAPER by pressing the "Solo" button => ReaLearn sends a note on to your device. You disable track solo => ReaLearn sends a note off to your device. So you really don't want to block note off!

There are some controllers which don't just let their lights be operated by incoming MIDI messages but also try to control them themselves - which makes things just worse. For example, Behringer X-Touch Compact (only in MIDI mode) works in this way: You press a button and the device itself will make the button LED light up. You release the button and the device itself will make the button LED light turn off. Bad, bad, bad! The consequence, e.g. when using it with ReaLearn's "Toggle buttons" mode and track solo: Pressing the button makes ReaLearn activate track solo. ReaLearn sends out the "Note on" message as a reaction. The LED is already on, so it's kind of unnecessary, but it doesn't hurt. So far it doesn't hurt! Now you release the button and the controller will switch its LED off. Bad! It's supposed to stay on because we use toggling! Luckily, ReaLearn has a workaround: The "Send feedback after control" checkbox. It just exists to work around bad controller design.

You should find out if your controller does this, too.

Originally Posted by ChrisDN

Just been following section 6.3.3 of the user guide, to the T... "Right-click ReaLearn's header panel and press Link current preset to FX".

That option never appears in the context menu.

Any further suggestions? Please and thank you!

Oh no! You are right! It disappeared with the last version 2.3.0. Sorry, will release a fix later today. In the meantime, go back to 2.2.0.

[ChrisDN]

Originally Posted by helgoboss

Oh no! You are right! It disappeared with the last version 2.3.0. Sorry, will release a fix later today. In the meantime, go back to 2.2.0.

Aha, okie dokie! Not to worry, not in a rush; I'll check it later.
Ty ty!

[Arthur McArthur]

Originally Posted by helgoboss

Now you release the button and the controller will switch its LED off. Bad! It's supposed to stay on because we use toggling! Luckily, ReaLearn has a workaround: The "Send feedback after control" checkbox. It just exists to work around bad controller design.

You should find out if your controller does this, too.

I think that is the case yes, the keyboard has an internal ability to clear the pad color once a note off is received from the pad being released. I think the other part of the problem is that it sends the note on channel 10, but expects the color change on channel 16. In this instance, what should I do?

[helgoboss]

Originally Posted by Arthur McArthur

I think that is the case yes, the keyboard has an internal ability to clear the pad color once a note off is received from the pad being released.

Have you tried both modes of operation? The docs say that it has an InControl mode and another one. Maybe one of these modes doesn't do this unnecessary internal color/LED control. That would be desireable, especially if you are thinking about contributing this as controller preset (which would be very nice). If not, you need to use the mentioned checkbox.

Originally Posted by Arthur McArthur

I think the other part of the problem is that it sends the note on channel 10, but expects the color change on channel 16. In this instance, what should I do?

No problem. Disable the feedback checkbox for the channel 10 mapping and create a second very similar mapping with channel 16 instead and the control checkbox disabled.

[Arthur McArthur]

Hmm, it seems like the alternate mode doesn't solve the issue.

I tried what you suggested, but it seems like I can't get it to work with any configuration of the "Send feedback after control" selected either. I've tried it on both mappings but no luck. Is it perhaps sending the feedback after the note on, but not the note off?

Here's the clipboard data for the two mappings:

{
  "version": "2.2.0",
  "id": "qV1zvOg2",
  "sendFeedbackOnlyIfArmed": true,
  "feedbackDeviceId": "39",
  "defaultGroup": {},
  "mappings": [
    {
      "id": "5f652de6-bb37-4f72-be28-1fcf251f1e3f",
      "name": "1",
      "source": {
        "type": 1,
        "channel": 9,
        "number": 40,
        "isRegistered": false,
        "is14Bit": false
      },
      "mode": {
        "type": 2
      },
      "target": {
        "type": 4
      },
      "feedbackIsEnabled": false
    },
    {
      "id": "959ebfc2-849e-4605-ac84-fa8fa83ef428",
      "name": "Copy of 1",
      "source": {
        "type": 1,
        "channel": 15,
        "number": 40,
        "isRegistered": false,
        "is14Bit": false
      },
      "mode": {
        "type": 2
      },
      "target": {
        "type": 4
      },
      "controlIsEnabled": false,
      "sendFeedbackAfterControl": true
    }
  ]
}

[helgoboss]

Originally Posted by Arthur McArthur

Hmm, it seems like the alternate mode doesn't solve the issue.

I tried what you suggested, but it seems like I can't get it to work with any configuration of the "Send feedback after control" selected either. I've tried it on both mappings but no luck. Is it perhaps sending the feedback after the note on, but not the note off?

Damn, I forgot that the "Send feedback after control" thing is only working within one mapping, so it would only work if it's a combined control/feedback mapping. Are you absolutely sure that an alternative mode doesn't solve your problem?

If not, then this is what you need: https://github.com/helgoboss/realearn/issues/14. It has been requested before by someone. You can give it a thumbs up (smiley button) so I'm reminded that is important for some.

One thing we should check if feedback works in general for that button (want to make sure that it's not another problem): If you change the pan in REAPER, does your button light change? It should, otherwise it's something else.

[Arthur McArthur]

Originally Posted by helgoboss

Damn, I forgot that the "Send feedback after control" thing is only working within one mapping, so it would only work if it's a combined control/feedback mapping. Are you absolutely sure that an alternative mode doesn't solve your problem?

If not, then this is what you need: https://github.com/helgoboss/realearn/issues/14. It has been requested before by someone. You can give it a thumbs up (smiley button) so I'm reminded that is important for some.

One thing we should check if feedback works in general for that button (want to make sure that it's not another problem): If you change the pan in REAPER, does your button light change? It should, otherwise it's something else.

Yes, tried the InControl/Extended mode but it doesn't solve the issue. When I change the pan, the pad's button does in fact light up. I'll go ahead and throw a smiley face on the pile

[fak0u]

Using "Auto-load preset" to control whatever plug-in is currently in focus


Hello, very interesting plugin, thank you for all the work.

I just can't find a way to make this work, any tips ?

I've read https://github.com/helgoboss/realear...troller-preset a dozen times

Cheers
Seb

[helgoboss]

Originally Posted by fak0u

Using "Auto-load preset" to control whatever plug-in is currently in focus


Hello, very interesting plugin, thank you for all the work.

I just can't find a way to make this work, any tips ?

I've read https://github.com/helgoboss/realear...troller-preset a dozen times

Cheers
Seb

2.3.0 has a problem. Use 2.2.0 please. Going to push an update soon.

[fak0u]

I am using 2.2.0 2021-02-16

[helgoboss]

Originally Posted by fak0u

I am using 2.2.0 2021-02-16

Oh, then I'm going to need a bit more details in what doesn't work for you exactly

[helgoboss]

Released ReaLearn 2.3.1 (ReaPack installation instructions)

Changes:
- Fixed non-visible "Link current preset to FX ..." context menu entry

[fak0u]

Originally Posted by helgoboss

Oh, then I'm going to need a bit more details in what doesn't work for you exactly

I don't get the presets to change automaticaly when I select a plugin

I have to manually change the preset in realearn for each plugin

[helgoboss]

Originally Posted by fak0u

I don't get the presets to change automaticaly when I select a plugin

I have to manually change the preset in realearn for each plugin

Please send the following things to info@helgoboss.org:

- A screenshot of ReaLearn's plug-in window.
- File "fx.json" in REAPER resource directory (REAPER → Actions → Show action list... → Show REAPER resource path in explorer/finder) "/Data/helgoboss/realearn/auto-load-configs"

That way I should be able to help you.

[BenK-msx]

HI Benjamin,

really need 'last touched' to not mess with tempo ( unless user specifies ), in newest version it 'seems' to default to tempo if i click in arrange view.. too easily anyway
suddenly having a tempo of 335 is a bit disconcerting!

Originally Posted by BenK-msx

Thanks for these tweaks,
regarding last touched, is it possible to exclude certain targets? (comment out a txt list or something?)

my large encoder assigned to last touched just made my project tempo go crazy until i realised what was going on! seems cool tho as can use on track volumes etc. as well as fx params.

-
cheers again

thanks again

EDIT: what seems to be happening is when i reach max param value of last touched (e.g master volume) and keep turning the encoder, it starts adjusting Tempo.. hope that helps.

[helgoboss]

Originally Posted by BenK-msx

HI Benjamin,

really need 'last touched' to not mess with tempo ( unless user specifies ), in newest version it 'seems' to default to tempo if i click in arrange view.. too easily anyway
suddenly having a tempo of 335 is a bit disconcerting!




thanks again

EDIT: what seems to be happening is when i reach max param value of last touched (e.g master volume) and keep turning the encoder, it starts adjusting Tempo.. hope that helps.

Understand. I think I will remove "Tempo" target learning completely. It has too many false positives (don't really know why). I don't think anyone is going to miss it anyway.

[BenK-msx]

do you mean from the last touched section? having it as a realearn target generally seems harmless enough.

thanks anyway, as at the moment this is sort of a bug and cant use last touched (which is awesome) at all.

[helgoboss]

Originally Posted by BenK-msx

do you mean from the last touched section? having it as a realearn target generally seems harmless enough.

thanks anyway, as at the moment this is sort of a bug and cant use last touched (which is awesome) at all.

No, I mean both from normal learning and last touched. The target will stay, it will just not be learnable anymore. I had some issues myself with that. Wanted to learn some parameter and suddenly had the tempo learned.

[BenK-msx]

Originally Posted by helgoboss

No, I mean both from normal learning and last touched. The target will stay, it will just not be learnable anymore. I had some issues myself with that. Wanted to learn some parameter and suddenly had the tempo learned.

ah cool, sure you'll sort it - cheers

[helgoboss]

Released ReaLearn 2.3.2 (ReaPack installation instructions)

Changes:
- Improved usability by vastly increasing OSC feedback performance ... much smoother now (MIDI feedback has been reworked as well and should be more snappy and accurate, too)

[helgoboss]

Originally Posted by Stroudy

Amazing work. Very cool indeed

Is there a way to link Preset NOT by the FX, but by the FX AND loaded preset?

For example, Kontakt will have any number of different assignable parameters, but ReaLearn will only load one, the 'Kontakt.vst" preset.

Here there are 2 instances of kontakt, but each has it's own preset name. Could that name be used by ReaLearn?

I could implement that, it's possible to access that name. There could be a second entry in the "Auto-load FX preset" dropdown named "Depending on focused FX and preset". I knew this dropdown would be good for something

[cjunekim]

I have been using ReaLearn without any issue for a while. I've set up a project template for a very complex setting and have been using it for months.

A couple of days ago I did synchronized the package and it was updated to a newer version.

During a live performance, the midi controller feedback didn't work at all and I was really embarassed.

From my investigation, the cause seems to be "<Any> (no feedback)" in Source Channel setting. The old version that I was using had no "(no feedback)" part when "Any" was chosen as far as I remember. Is there any specific reason that you disabled feedback on "Any" source channel option?

[maxdembo]

So, noob question alert...

Can I use Realearn 2 to set up the Roller/Looper on a Beatstep Pro to control playback in Reaper? So it performs the similar 'looping of a section' as it does on the BSP itself?

[helgoboss]

Originally Posted by cjunekim

I have been using ReaLearn without any issue for a while. I've set up a project template for a very complex setting and have been using it for months.

A couple of days ago I did synchronized the package and it was updated to a newer version.

During a live performance, the midi controller feedback didn't work at all and I was really embarassed.

From my investigation, the cause seems to be "<Any> (no feedback)" in Source Channel setting. The old version that I was using had no "(no feedback)" part when "Any" was chosen as far as I remember. Is there any specific reason that you disabled feedback on "Any" source channel option?

Sorry to hear that. Seems you have used a prerelease version before you updated (1.12.0-pre1 - 1.12.0-pre8) and didn't take note of the post about this prerelease bug. Please follow the instructions in that post to fix your project.

As a side note, whether prerelease or not (but especially with prereleases = beta releases): If you use this live, I highly recommend to run some tests after each update to see if your projects still work as desired, not just with ReaLearn but also with other software. Even though I run manual and automated tests before each release and try hard to avoid bugs ... there's no guarantee that something unwanted slips through. Triggered by the prerelease bug that you run into, I also introduced a version number in the preset to be able to better deal with this kind of bugs, which also makes it much easier to ensure backward compatibility whenever I make a change in existing behavior.

The "<Any>" setting never supported feedback. It was just that these flawed prerelease versions wrongly loaded and operated the "<Any>" channel as channel 0.

Originally Posted by maxdembo

So, noob question alert...

Can I use Realearn 2 to set up the Roller/Looper on a Beatstep Pro to control playback in Reaper? So it performs the similar 'looping of a section' as it does on the BSP itself?

I don't know the Beatstep Pro. ReaLearn is a rather general-purpose tool for mapping control elements to actions and parameters in REAPER. There might be ways to achieve what you want by a combination of ReaLearn targets with effects/scripts etc, but it's not a dedicated looping tool. That said, I plan to add some targets (such as "Play region") which can greatly help in doing loop-based music.

[maxdembo]

Originally Posted by helgoboss

I don't know the Beatstep Pro. ReaLearn is a rather general-purpose tool for mapping control elements to actions and parameters in REAPER. There might be ways to achieve what you want by a combination of ReaLearn targets with effects/scripts etc, but it's not a dedicated looping tool. That said, I plan to add some targets (such as "Play region") which can greatly help in doing loop-based music.

Thanks for the reply. I guess I should give it a go and see what it can do

[foxAsteria]

Originally Posted by maxdembo

So, noob question alert...

Can I use Realearn 2 to set up the Roller/Looper on a Beatstep Pro to control playback in Reaper? So it performs the similar 'looping of a section' as it does on the BSP itself?

I have Beatstep but I've never used it natively (only as MIDI controller). OTOH it works spendidly with ReaLearn and is great for instant visual feedback of track controls and playback, toggles etc.

Probably one of the most flexible controllers around IMO with externally controllable LED pads and smooth encoders.

[helgoboss]

Released ReaLearn 2.4.0 (ReaPack installation instructions)

Changes:
- #156 Added "Exclusive" dropdown to all "track property on/off"-style targets (arm, selection, mute, solo, fx all enable, automation touch state) which even allows "Exclusive within folder" behavior
- #147 Added "Automation touch state" target in order to support "Touch" automation mode for volume, pan and width envelopes (e.g. with touch-sensitive faders or push encoders)
- #47 Added option "Behavior" for "Track solo" target, start using the routing-friendly "Solo in front" behavior by default
- #176 Added REAPER action "ReaLearn: Send feedback for all instances" (useful mainly for debugging purposes because ReaLearn usually sends feedback automatically)
- #162 Improved "Track solo" target by making it work with "Options → Solo in front"
- #176 Improved usability by clearing feedback (switch off lights or turn down motorized faders) when closing ReaLearn instance or REAPER project
- #171 Improved "Track mute" target by making it work reliably also on master track and by making feedback from automation work
- #167 Improved usability by disabling learning of "Track selection" target if REAPER preference "Mouse click on volume/pan faders and track buttons changes track selection" enabled (in order to avoid false positives, preference change respected after REAPER restart)
- #170 Improved usability by making "Master tempo" target uneligible as "Last touched" target and for learning in general (there were too many false positives and it could get annoying at times, just select the target manually in the dropdown to use it)
- #165 Improved usability by letting the user confirm before globally removing an OSC device
- #181 Improved usability by not firing immediately when changing the encoder turning direction while using a negative "Speed" setting (that was annoying and could result in sudden unwanted parameter changes)
- #177 Improved usability by not annoying user with error messages when controlling just because they use some setting that doesn't make sense (such as controlling relative targets with absolute messages)
- Improved usability by clearing feedback of the previous source if a mapping source is changed
- #168 Fixed non-working automation writing for "Track width" target when controlled via relative encoder
- #172 Fixed often missing initial feedback for virtual controller mappings (LEDs were sometimes not updated before interacting with the project, e.g. by pressing play)
- #177 Fixed possible "assertion failed: 0.0 &lt;= normalized_value || normalized_value.is_nan()" error with volume targets
- #179 Fixed recent bug that caused "Track selection" target to be learned with wrong track (the previously selected one instead of the newly selected)
- #180 Fixed recent bug that caused wrong "Selected track" target feedback


My personal favorite of this release is the new "Exclusive: Within folder" option that is available now for many kinds of "on/off style" track targets. E.g. it allows you to select a track exclusively within its folder, not among all tracks ... super useful for creating live playing setups. I think track folders and in particular the ability to nest them is one of REAPER's most intuitive features. It just feels natural to route audio/MIDI that way. Now you can take advantage of this for many ReaLearn targets.

[Regisfofo]

Thanks for the update!

Exclusive within folder, I don't get that. Could you describe a use case ?

[helgoboss]

Originally Posted by Regisfofo

Thanks for the update!

Exclusive within folder, I don't get that. Could you describe a use case ?

Definitely. Here's one: Let's say you have multiple keyboards or key splits and you want that each keyboard plays exactly one sound (1 sound = 1 track, so it can be a really sophisticated sound with all kinds of FX attached). Now you want to be able to change which sound is played on each keyboard by the press of buttons. That's dead-easy now by creating one folder for each keyboard and using folder-exclusive "Track arm" (or folder-exclusive "Track selection" if your tracks have auto-arm enabled).

UPDATED: Just like I demonstrated in the video here but with multiple keyboards or splits.

Generally, it always comes in useful if you feel your control scenario needs some kind of "partial exclusiveness" ... sorry, I don't know how to describe this in more vivid words, maybe someone else who understood the potential of this can describe it in a better way in future Basically, you define groups of tracks simply by using REAPER's intuitive folder drag and drop and then make sure that within that group only one thing is ever active.

[Regisfofo]

Thanks I got it!
So we could use 2 distinct midi sources to go to 2 folders and control easily Arm and Mute so only one track is active within each folder. I like it !

I tested it with 2.4.0 and it seems to be triggering the folder beneath too. Is it a bug ?

Edit : Do you think it could possible to hide all other tracks Exclusive within folder too ?
And another one, more difficult I suspect : Would it be possible to set a button so it goes activate (unmute, arm, (unhide?) ) the next/previous track within folder ?

ReEdit : Would be even greater to use Midi note number to switch within track in one folder. Here is what I have in mind :
-One folder with all your favorite bass sounds
-Hold a modifier and hit a key on your midi controller
-Track activation change accordingly within that folder.
So there could one modifier for each folder, for each type of sound.

[maxdembo]

Originally Posted by foxAsteria

I have Beatstep but I've never used it natively (only as MIDI controller). OTOH it works spendidly with ReaLearn and is great for instant visual feedback of track controls and playback, toggles etc.

Probably one of the most flexible controllers around IMO with externally controllable LED pads and smooth encoders.

Interesting.

I still havent got round to trying this (we know why), but I shall!

Thanks man.

[cjunekim]

Thank you for a wonderful addition!

BTW, I can't really figure it out. Could you have a look into this?



In this screen recording, I've set such that:

1) MIDI note A -> Track 2 arm, within folder exclusive (Mode: toggle buttons)
2) MIDI note B -> Track 4 arm, within folder exclusive (Mode: toggle buttons)

When I hit note A and B alternatingly, the track 2 and 4 are armed alternatingly, as expected. If I hit note B twice successively, track 4 is armed first and then track 2 is armed with track 4 unarmed. But now it gets interesting. When I hit note A twice successively, track 2 is armed first and then track 4 and 5 are armed now. I think track 5 shouldn't be armed at all.

What's happening?

Originally Posted by helgoboss

Definitely. Here's one: Let's say you have multiple keyboards or key splits and you want that each keyboard plays exactly one sound (1 sound = 1 track, so it can be a really sophisticated sound with all kinds of FX attached). Now you want to be able to change which sound is played on each keyboard by the press of buttons. That's dead-easy now by creating one folder for each keyboard and using folder-exclusive "Track arm" (or folder-exclusive "Track selection" if your tracks have auto-arm enabled).

UPDATED: Just like I demonstrated in the video here but with multiple keyboards or splits.

Generally, it always comes in useful if you feel your control scenario needs some kind of "partial exclusiveness" ... sorry, I don't know how to describe this in more vivid words, maybe someone else who understood the potential of this can describe it in a better way in future Basically, you define groups of tracks simply by using REAPER's intuitive folder drag and drop and then make sure that within that group only one thing is ever active.

[helgoboss]

Originally Posted by Regisfofo

Thanks I got it!
So we could use 2 distinct midi sources to go to 2 folders and control easily Arm and Mute so only one track is active within each folder. I like it !

I tested it with 2.4.0 and it seems to be triggering the folder beneath too. Is it a bug ?

Seems like. Looking into it today or tomorrow.

Originally Posted by Regisfofo

Edit : Do you think it could possible to hide all other tracks Exclusive within folder too ?

I could provide a "Track hide" target that does this. Though I think it will not be possible to make it work with feedback, but maybe that's not important in your case?

Originally Posted by Regisfofo

And another one, more difficult I suspect : Would it be possible to set a button so it goes activate (unmute, arm, (unhide?) ) the next/previous track within folder ?

Would be possible but it sounds a bit exotic. Why would you want that?

Originally Posted by Regisfofo

ReEdit : Would be even greater to use Midi note number to switch within track in one folder. Here is what I have in mind :
-One folder with all your favorite bass sounds
-Hold a modifier and hit a key on your midi controller
-Track activation change accordingly within that folder.
So there could one modifier for each folder, for each type of sound.

That sounds like rather a job for the "Selected track" target. All on/off targets (such as "Track selection") by definition work on a very specific track, making them especially suitable for buttons. Some of them also have a counterpart that's intended to be used with control elements such as encoders, knobs, faders or a range of keyboard key. For "Track selection" that would be "Selected track". It sounds like you could use that in combination with auto-arm to achieve what you want. But it might not work so well in the long run because it always operates on the complete list of tracks, not just within a specific folder. I will see if there's a good (and not too exotic) concept that I can implement to support your use case.

Originally Posted by cjunekim

When I hit note A and B alternatingly, the track 2 and 4 are armed alternatingly, as expected. If I hit note B twice successively, track 4 is armed first and then track 2 is armed with track 4 unarmed. But now it gets interesting. When I hit note A twice successively, track 2 is armed first and then track 4 and 5 are armed now. I think track 5 shouldn't be armed at all.

What's happening?

Oh, that's this bug that Regisfofo mentioned above.

[Regisfofo]

By the way thanks for that one :
- #176 Added REAPER action "ReaLearn: Send feedback for all instances" (useful mainly for debugging purposes because ReaLearn usually sends feedback automatically)
I'll use it when uhe synth don't give feedback when switching preset.

[Regisfofo]

Originally Posted by helgoboss

I could provide a "Track hide" target that does this. Though I think it will not be possible to make it work with feedback, but maybe that's not important in your case?

I don't know, I'm not very clear with my idea. Let me think more about it.
The thing is I'd love to have a "cleaner" session where I could hide all the utility/unused tracks. Makes me think that that would be awesome to be able to float an fx without using track selection. some cases comes to me :
- Float a realearn instance with the touch of a button to tweak with the settings
- Float a dedicated tuner on an hidden track. With the touch of a button, without breaking Auto-arm selection for exemple.
- Float PlayTime...

Would be possible but it sounds a bit exotic. Why would you want that?

Maybe handle multi selection... One selected track within each folder to make distinct instruments active... Sounds pretty delicate I recon!

That sounds like rather a job for the "Selected track" target. All on/off targets (such as "Track selection") by definition work on a very specific track, making them especially suitable for buttons. Some of them also have a counterpart that's intended to be used with control elements such as encoders, knobs, faders or a range of keyboard key. For "Track selection" that would be "Selected track". It sounds like you could use that in combination with auto-arm to achieve what you want. But it might not work so well in the long run because it always operates on the complete list of tracks, not just within a specific folder. I will see if there's a good (and not too exotic) concept that I can implement to support your use case.

Thanks for considering.
My aim is to set a creative template for me to play my guitars (electric/acoustic), control their sends to synth (converted by MidiGuitar2), other audio input an invited friend could be using and some other controllers for synths and drums. The thing is the session can become a mess pretty quickly and my little brain is struggling to cope with all of it...
I was thinking that clearer, hiding a lot of unused sounds/tracks etc could help...

[helgoboss]

Originally Posted by Regisfofo

And another one, more difficult I suspect : Would it be possible to set a button so it goes activate (unmute, arm, (unhide?) ) the next/previous track within folder ?

Originally Posted by Regisfofo

Maybe handle multi selection... One selected track within each folder to make distinct instruments active... Sounds pretty delicate I recon!

I guess I'm not sure yet what you are getting at. Do you want to be able to not just e.g. select 1 track exclusively within a folder, but maybe a group of 2 or more tracks ("multi selection")? If this is what you want, I have another idea: I could add a new option for "Exclusive" named "Within folder, including nested tracks". With such an option you could make all the tracks that you want to be selected at once into one folder. Working on folders should be more stable and clean than affecting previous/next tracks.

Originally Posted by Regisfofo

ReEdit : Would be even greater to use Midi note number to switch within track in one folder. Here is what I have in mind :
-One folder with all your favorite bass sounds
-Hold a modifier and hit a key on your midi controller
-Track activation change accordingly within that folder.
So there could one modifier for each folder, for each type of sound.

I added the following FRs:
- #184 (most important requirement for this scenario)
- #191 (2nd most important one)