Vendor helgoboss/helgobox (ReaLearn) as basis for custom UI fork

Stripped upstream git history; starting point for replacing the native SWELL/Win32 mapping UI with something more suited to bulk editing. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-07-15 17:38:29 -04:00
parent 583ed77a67
commit e58f06d9fa
2232 changed files with 685575 additions and 1 deletions
@@ -0,0 +1,5 @@
+= Target "Track: Arm/disarm"
+
+Arms the track for recording if the incoming absolute control value is greater than 0%, otherwise disarms the track.
+This disables "Automatic record-arm when track selected".
+If you don't want that, use xref:targets/track/select-unselect.adoc[] instead.
@@ -0,0 +1,3 @@
+= Target "Track: Enable/disable all FX"
+
+Enables all the track's FX instances if the incoming absolute control value is greater than 0%, otherwise disables them.
@@ -0,0 +1,3 @@
+= Target "Track: Enable/disable parent send"
+
+Enables the parent send routing of the track if the incoming absolute control value is greater than 0%, otherwise disables it.
@@ -0,0 +1,3 @@
+= Target "Track: Mute/unmute"
+
+Mutes the track if the incoming absolute control value is greater than 0%, otherwise unmutes the track.
@@ -0,0 +1,16 @@
+= Target "Track: Peak"
+
+This is a feedback-only target!
+It turns your feedback-capable controller into a VU meter by constantly reporting the current volume of the configured track to it.
+
+In addition to connecting it with a LED ring or motor fader source (which should be obvious), it can also be used with a single LED to build a clipping indicator:
+
+. Set _Target Min_ to the minimum dB value that should make your clipping LED turn on.
+Leave _Target Max_ at 12.00 dB.
+. Make sure the xref:user-interface/mapping-panel/glue-section.adoc#out-of-range-behavior[] is set to "Min or max".
+. If you have an LED that supports multiple colors, you will probably see a rainbow of colors flashing up which can be quite confusing.
+Use the feedback transformation formula `x = ceil(y)` to restrict the feedback to just two values:
+Min (0%) or Max (100%).
+You can then use xref:user-interface/mapping-panel/glue-section.adoc#source-min-max[] to adjust the off/on LED colors.
+
+At the moment this target only reports peak volume, not RMS.
@@ -0,0 +1,3 @@
+= Target "Track: Phase invert/normal"
+
+Inverts the track phase if the incoming absolute control value is greater than 0%, otherwise switches the track phase back to normal.
@@ -0,0 +1,14 @@
+= Target "Track: Select/unselect"
+
+Selects the track if the incoming absolute control value is greater than 0%, otherwise unselects the track.
+
+This target stops being learnable if you activate the REAPER preference "Mouse click on volume/pan faders and track buttons changes track selection" (because this preference would generate too many false positives).
+If you change the preference, ReaLearn will take it into consideration the next time you restart REAPER.
+
+== Scroll TCP checkbox
+
+Also scrolls the track control panel to the desired track.
+
+== Scroll mixer checkbox
+
+Also scrolls the mixer control panel to the desired track.
@@ -0,0 +1,7 @@
+= Target "Track: Set automation mode"
+
+Sets the track to a specific automation mode if the incoming control value is greater than 0%, otherwise sets it back to REAPER's default track automation mode "Trim/Read".
+
+== Mode menu
+
+Here you can pick the desired automation mode.
@@ -0,0 +1,14 @@
+= Target "Track: Set automation touch state"
+
+When you use REAPER's "Touch" automation mode, REAPER needs a way to know if you are currently touching the control element which is bound to the automation envelope or not.
+As long as you keep touching it, it will overwrite existing automation.
+As soon as you release it, REAPER will leave the envelope untouched.
+
+Classical control surfaces implement this very intuitively by providing touch-sensitive faders.
+With this target, you can easily reproduce exactly this behavior via ReaLearn.
+You do this by mapping the touch event (which is usually nothing else than a MIDI note on/off message) to this target.
+The touch state is scoped to a particular track and parameter type which you can choose in the *Type* dropdown.
+
+However, ReaLearn wouldn't be ReaLearn if it wouldn't allow you to let totally different sources take control of the touch state.
+For example, if you have a push encoder, you could map the "push" event to the touch state, allowing you to write automation only while you are touching the encoder.
+Or if you don't have a push encoder, you could just use some spare button.
@@ -0,0 +1,7 @@
+= Target "Track: Set monitoring mode"
+
+Sets the track to a specific input monitoring mode if the incoming control value is greater than 0%, otherwise sets it back to "Off".
+
+== Mode menu
+
+Here you can pick the desired monitoring mode.
@@ -0,0 +1,14 @@
+= Target "Track: Set pan"
+
+Sets the track's pan value.
+
+== Target-specific properties
+
+This target supports the following additional xref:further-concepts/target.adoc#target-property[target properties].
+
+[cols="m,1,3"]
+|===
+|Name|Type|Description
+
+|target.pan.mcu | String | Pan value tailored to one line on a Mackie Control LCD
+|===
@@ -0,0 +1,14 @@
+= Target "Track: Set stereo pan width"
+
+Sets the track's width value (applicable if the track is in stereo pan mode).
+
+== Target-specific properties
+
+This target supports the following additional xref:further-concepts/target.adoc#target-property[target properties].
+
+[cols="m,1,3"]
+|===
+|Name|Type|Description
+
+|target.width.mcu | String | Width value tailored to one line on a Mackie Control LCD
+|===
@@ -0,0 +1,3 @@
+= Target "Track: Set volume"
+
+Sets the track's volume.
@@ -0,0 +1,7 @@
+= Target "Track: Show/hide"
+
+Shows the track if the incoming absolute control value is greater than 0%, otherwise hides it.
+
+== Area menu
+
+Lets you decide if you want it to show/hide in the track control panel or the mixer.
@@ -0,0 +1,14 @@
+= Target "Track: Solo/unsolo"
+
+Soloes the track if the incoming absolute control value is greater than 0%, otherwise unsoloes the track.
+
+== Behavior menu
+
+See the REAPER user guide for details.
+
+Solo in place:: Soloes the track while respecting REAPER's routing.
+This is REAPER's default and since ReaLearn v2.4.0 also ReaLearn's default.
+Solo (ignore routing):: Soloes the track muting everything else, no matter the routing.
+Use REAPER preference:: Follows whatever is set in the REAPER preferences.
+
+Learning this target by pressing the "Solo" button of the _master_ track is currently not possible but of course you can just select it manually in the dropdown menu.
@@ -0,0 +1,24 @@
+= Target "Track"
+
+A target that allows you to define a track.
+
+== Act/Tags controls
+
+**Act/Tags** stands for "Action / Unit tags" and decides what happens when a control messages arrives, e.g. a button press.
+
+=== Action menu
+
+None (feedback only):: With this setting, nothing will happen.
+It's suited very well as neutral target for textual feedback with an expression that contains a track property, e.g. `{{ target.track.name }}`.
+
+Set (as unit track):: The button press will set the track defined in this target as xref:further-concepts/unit.adoc#unit-track[] _without resolving it before_.
+For example, if this target defines to use the currently selected track (xref:further-concepts/target.adoc#selected-selector[]), pressing the button will make the unit track dynamically reflect whatever track is selected.
+
+Pin (as unit track):: The button press will resolve the track defined in this target and set the result as xref:further-concepts/unit.adoc#unit-track[].
+For example, if this target defines to use the currently selected track, pressing the button will check which track is currently selected and set the unit track to exactly this track.
+It will stay that way even if the user selects another track.
+
+=== Unit tags field
+
+The text field lets you define xref:further-concepts/unit.adoc#unit-tag[unit tags] to determine for which xref:key-concepts.adoc#unit[units] the xref:further-concepts/unit.adoc#unit-track[] should be changed.
+If it's empty, the current unit will be affected.