p4piwabl0/virtual-controller
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Reorganize top-level directories with clearer naming convention

Browse Source 
app -> app-desktop-macos, presets -> app-presets, server -> remote-server,
daw-config-reaper -> osc-config-daw, plugin-reaper-realearn -> plugin-reaper-relearn.
Updated run.py and presets.py path references accordingly.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
Paul Lipscomb
2026-07-15 17:51:05 -04:00
parent e58f06d9fa
commit 7ecc718f5d
2256 changed files with 11 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugin-reaper-relearn/doc/realearn/modules/ROOT/pages/targets/track/set-automation-touch-state.adoc
+14
View File
@@ -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.