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

[djfrodo]

O.k. so...

On my newer mac (Monteray) Realearn works great.

On my older mac (Mojave) no love.

Just checking to see if this is expected.

I updated to the latest version of Reaper for 10.4 macs and thought that would do it, but - nope.

[Bassman002]

Originally Posted by helgoboss

You create a Lua script from the actions window. And there you write some Lua code like reaper.IForgotTheFunctionName() to call the MIDI editor action. I don't have access to a computer these days, so you need to have a look yourself or other ReaScripters might help.

HI

It works now, the ReaScripters (vitalker) helped me.

reaper.MIDIEditor_OnCommand( reaper.MIDIEditor_GetActive(), reaper.NamedCommandLookup("_OSARA_NEXTCHORD") )

I've set up a fader to move to the next/previous chord (2, 1 for increment and 1 for decrement), fast and helpful.

I have asked this months ago I think. How can I set up to not trigger every step but every other or third step of the fader?

Not possible at the moment, just for endless encoders (stepsize)...?

Thanks,
Bassman.

[helgoboss]

Originally Posted by djfrodo

O.k. so...

On my newer mac (Monteray) Realearn works great.

On my older mac (Mojave) no love.

Just checking to see if this is expected.

I updated to the latest version of Reaper for 10.4 macs and thought that would do it, but - nope.

Mojave is 10.14 right? That should work actually. Which realearn versions did you try? Any error message when you rescan (you need to start a current version of REAPER via Terminal to see them)?

[helgoboss]

Originally Posted by Bassman002

HI

It works now, the ReaScripters (vitalker) helped me.



I've set up a fader to move to the next/previous chord (2, 1 for increment and 1 for decrement), fast and helpful.

I have asked this months ago I think. How can I set up to not trigger every step but every other or third step of the fader?

Not possible at the moment, just for endless encoders (stepsize)...?

Thanks,
Bassman.

So you use "Make relative" I suppose? Or a control transformation? Yes, in both cases, step size / speed is not configurable yet. There's an FR for that already

[blinddrew]

Originally Posted by helgoboss

Please put ReaControlMIDI on a track, show the log and make a complete clockwise turn of your knob. If it's an endless encoder, keep turning a bit even after the maximum value has been reached, so I see which messages (if any) it keeps sending in that case. Post the result here. Then I will see what's the right strategy.

Hi Helgoboss,
Yep, it's an endless encoder. The output is a midi note on channel 7 up to note 99 then it changes to channel 8 up to note 100. If you keep scrolling past that it keeps sending that last note.

Here's the log:
0: 96 02 7F [Note On] chan 7 note 2 vel 127
1: 96 03 7F [Note On] chan 7 note 3 vel 127
2: 96 04 7F [Note On] chan 7 note 4 vel 127
3: 96 05 7F [Note On] chan 7 note 5 vel 127
4: 96 06 7F [Note On] chan 7 note 6 vel 127
5: 96 07 7F [Note On] chan 7 note 7 vel 127
6: 96 08 7F [Note On] chan 7 note 8 vel 127
7: 96 09 7F [Note On] chan 7 note 9 vel 127
8: 96 0A 7F [Note On] chan 7 note 10 vel 127
9: 96 0B 7F [Note On] chan 7 note 11 vel 127
10: 96 0C 7F [Note On] chan 7 note 12 vel 127
11: 96 0E 7F [Note On] chan 7 note 14 vel 127
12: 96 0F 7F [Note On] chan 7 note 15 vel 127
13: 96 10 7F [Note On] chan 7 note 16 vel 127
14: 96 11 7F [Note On] chan 7 note 17 vel 127
15: 96 12 7F [Note On] chan 7 note 18 vel 127
16: 96 13 7F [Note On] chan 7 note 19 vel 127
17: 96 14 7F [Note On] chan 7 note 20 vel 127
18: 96 15 7F [Note On] chan 7 note 21 vel 127
19: 96 16 7F [Note On] chan 7 note 22 vel 127
20: 96 17 7F [Note On] chan 7 note 23 vel 127
21: 96 18 7F [Note On] chan 7 note 24 vel 127
22: 96 19 7F [Note On] chan 7 note 25 vel 127
23: 96 1A 7F [Note On] chan 7 note 26 vel 127
24: 96 1B 7F [Note On] chan 7 note 27 vel 127
25: 96 1C 7F [Note On] chan 7 note 28 vel 127
26: 96 1D 7F [Note On] chan 7 note 29 vel 127
27: 96 1E 7F [Note On] chan 7 note 30 vel 127
28: 96 1F 7F [Note On] chan 7 note 31 vel 127
29: 96 20 7F [Note On] chan 7 note 32 vel 127
30: 96 21 7F [Note On] chan 7 note 33 vel 127
31: 96 22 7F [Note On] chan 7 note 34 vel 127
32: 96 23 7F [Note On] chan 7 note 35 vel 127
33: 96 24 7F [Note On] chan 7 note 36 vel 127
34: 96 25 7F [Note On] chan 7 note 37 vel 127
35: 96 26 7F [Note On] chan 7 note 38 vel 127
36: 96 27 7F [Note On] chan 7 note 39 vel 127
37: 96 28 7F [Note On] chan 7 note 40 vel 127
38: 96 29 7F [Note On] chan 7 note 41 vel 127
39: 96 2A 7F [Note On] chan 7 note 42 vel 127
40: 96 2B 7F [Note On] chan 7 note 43 vel 127
41: 96 2C 7F [Note On] chan 7 note 44 vel 127
42: 96 2D 7F [Note On] chan 7 note 45 vel 127
43: 96 2E 7F [Note On] chan 7 note 46 vel 127
44: 96 2F 7F [Note On] chan 7 note 47 vel 127
45: 96 30 7F [Note On] chan 7 note 48 vel 127
46: 96 31 7F [Note On] chan 7 note 49 vel 127
47: 96 32 7F [Note On] chan 7 note 50 vel 127
48: 96 33 7F [Note On] chan 7 note 51 vel 127
49: 96 34 7F [Note On] chan 7 note 52 vel 127
50: 96 35 7F [Note On] chan 7 note 53 vel 127
51: 96 36 7F [Note On] chan 7 note 54 vel 127
52: 96 37 7F [Note On] chan 7 note 55 vel 127
53: 96 38 7F [Note On] chan 7 note 56 vel 127
54: 96 39 7F [Note On] chan 7 note 57 vel 127
55: 96 3A 7F [Note On] chan 7 note 58 vel 127
56: 96 3B 7F [Note On] chan 7 note 59 vel 127
57: 96 3C 7F [Note On] chan 7 note 60 vel 127
58: 96 3D 7F [Note On] chan 7 note 61 vel 127
59: 96 3E 7F [Note On] chan 7 note 62 vel 127
60: 96 3F 7F [Note On] chan 7 note 63 vel 127
61: 96 40 7F [Note On] chan 7 note 64 vel 127
62: 96 41 7F [Note On] chan 7 note 65 vel 127
63: 96 42 7F [Note On] chan 7 note 66 vel 127
64: 96 43 7F [Note On] chan 7 note 67 vel 127
65: 96 44 7F [Note On] chan 7 note 68 vel 127
66: 96 45 7F [Note On] chan 7 note 69 vel 127
67: 96 46 7F [Note On] chan 7 note 70 vel 127
68: 96 47 7F [Note On] chan 7 note 71 vel 127
69: 96 48 7F [Note On] chan 7 note 72 vel 127
70: 96 49 7F [Note On] chan 7 note 73 vel 127
71: 96 4A 7F [Note On] chan 7 note 74 vel 127
72: 96 4B 7F [Note On] chan 7 note 75 vel 127
73: 96 4C 7F [Note On] chan 7 note 76 vel 127
74: 96 4D 7F [Note On] chan 7 note 77 vel 127
75: 96 4E 7F [Note On] chan 7 note 78 vel 127
76: 96 4F 7F [Note On] chan 7 note 79 vel 127
77: 96 50 7F [Note On] chan 7 note 80 vel 127
78: 96 51 7F [Note On] chan 7 note 81 vel 127
79: 96 52 7F [Note On] chan 7 note 82 vel 127
80: 96 53 7F [Note On] chan 7 note 83 vel 127
81: 96 54 7F [Note On] chan 7 note 84 vel 127
82: 96 55 7F [Note On] chan 7 note 85 vel 127
83: 96 56 7F [Note On] chan 7 note 86 vel 127
84: 96 57 7F [Note On] chan 7 note 87 vel 127
85: 96 58 7F [Note On] chan 7 note 88 vel 127
86: 96 59 7F [Note On] chan 7 note 89 vel 127
87: 96 5A 7F [Note On] chan 7 note 90 vel 127
88: 96 5B 7F [Note On] chan 7 note 91 vel 127
89: 96 5C 7F [Note On] chan 7 note 92 vel 127
90: 96 5D 7F [Note On] chan 7 note 93 vel 127
91: 96 5E 7F [Note On] chan 7 note 94 vel 127
92: 96 5F 7F [Note On] chan 7 note 95 vel 127
93: 96 60 7F [Note On] chan 7 note 96 vel 127
94: 96 61 7F [Note On] chan 7 note 97 vel 127
95: 96 62 7F [Note On] chan 7 note 98 vel 127
96: 96 63 7F [Note On] chan 7 note 99 vel 127
97: 97 00 7F [Note On] chan 8 note 0 vel 127
98: 97 00 7F [Note On] chan 8 note 0 vel 127
99: 97 01 7F [Note On] chan 8 note 1 vel 127
100: 97 02 7F [Note On] chan 8 note 2 vel 127
101: 97 03 7F [Note On] chan 8 note 3 vel 127
102: 97 04 7F [Note On] chan 8 note 4 vel 127
103: 97 05 7F [Note On] chan 8 note 5 vel 127
104: 97 06 7F [Note On] chan 8 note 6 vel 127
105: 97 07 7F [Note On] chan 8 note 7 vel 127
106: 97 08 7F [Note On] chan 8 note 8 vel 127
107: 97 09 7F [Note On] chan 8 note 9 vel 127
108: 97 0A 7F [Note On] chan 8 note 10 vel 127
109: 97 0B 7F [Note On] chan 8 note 11 vel 127
110: 97 0C 7F [Note On] chan 8 note 12 vel 127
111: 97 0D 7F [Note On] chan 8 note 13 vel 127
112: 97 0E 7F [Note On] chan 8 note 14 vel 127
113: 97 0F 7F [Note On] chan 8 note 15 vel 127
114: 97 10 7F [Note On] chan 8 note 16 vel 127
115: 97 11 7F [Note On] chan 8 note 17 vel 127
116: 97 12 7F [Note On] chan 8 note 18 vel 127
117: 97 13 7F [Note On] chan 8 note 19 vel 127
118: 97 14 7F [Note On] chan 8 note 20 vel 127
119: 97 15 7F [Note On] chan 8 note 21 vel 127
120: 97 16 7F [Note On] chan 8 note 22 vel 127
121: 97 17 7F [Note On] chan 8 note 23 vel 127
122: 97 18 7F [Note On] chan 8 note 24 vel 127
123: 97 19 7F [Note On] chan 8 note 25 vel 127
124: 97 1A 7F [Note On] chan 8 note 26 vel 127
125: 97 1B 7F [Note On] chan 8 note 27 vel 127
126: 97 1C 7F [Note On] chan 8 note 28 vel 127
127: 97 1D 7F [Note On] chan 8 note 29 vel 127
128: 97 1E 7F [Note On] chan 8 note 30 vel 127
129: 97 1F 7F [Note On] chan 8 note 31 vel 127
130: 97 20 7F [Note On] chan 8 note 32 vel 127
131: 97 21 7F [Note On] chan 8 note 33 vel 127
132: 97 22 7F [Note On] chan 8 note 34 vel 127
133: 97 23 7F [Note On] chan 8 note 35 vel 127
134: 97 24 7F [Note On] chan 8 note 36 vel 127
135: 97 25 7F [Note On] chan 8 note 37 vel 127
136: 97 26 7F [Note On] chan 8 note 38 vel 127
137: 97 27 7F [Note On] chan 8 note 39 vel 127
138: 97 28 7F [Note On] chan 8 note 40 vel 127
139: 97 29 7F [Note On] chan 8 note 41 vel 127
140: 97 2A 7F [Note On] chan 8 note 42 vel 127
141: 97 2B 7F [Note On] chan 8 note 43 vel 127
142: 97 2C 7F [Note On] chan 8 note 44 vel 127
143: 97 2D 7F [Note On] chan 8 note 45 vel 127
144: 97 2E 7F [Note On] chan 8 note 46 vel 127
145: 97 2F 7F [Note On] chan 8 note 47 vel 127
146: 97 30 7F [Note On] chan 8 note 48 vel 127
147: 97 31 7F [Note On] chan 8 note 49 vel 127
148: 97 32 7F [Note On] chan 8 note 50 vel 127
149: 97 33 7F [Note On] chan 8 note 51 vel 127
150: 97 34 7F [Note On] chan 8 note 52 vel 127
151: 97 35 7F [Note On] chan 8 note 53 vel 127
152: 97 36 7F [Note On] chan 8 note 54 vel 127
153: 97 37 7F [Note On] chan 8 note 55 vel 127
154: 97 38 7F [Note On] chan 8 note 56 vel 127
155: 97 39 7F [Note On] chan 8 note 57 vel 127
156: 97 3A 7F [Note On] chan 8 note 58 vel 127
157: 97 3B 7F [Note On] chan 8 note 59 vel 127
158: 97 3C 7F [Note On] chan 8 note 60 vel 127
159: 97 3D 7F [Note On] chan 8 note 61 vel 127
160: 97 3E 7F [Note On] chan 8 note 62 vel 127
161: 97 3F 7F [Note On] chan 8 note 63 vel 127
162: 97 40 7F [Note On] chan 8 note 64 vel 127
163: 97 41 7F [Note On] chan 8 note 65 vel 127
164: 97 42 7F [Note On] chan 8 note 66 vel 127
165: 97 43 7F [Note On] chan 8 note 67 vel 127
166: 97 44 7F [Note On] chan 8 note 68 vel 127
167: 97 45 7F [Note On] chan 8 note 69 vel 127
168: 97 46 7F [Note On] chan 8 note 70 vel 127
169: 97 47 7F [Note On] chan 8 note 71 vel 127
170: 97 48 7F [Note On] chan 8 note 72 vel 127
171: 97 49 7F [Note On] chan 8 note 73 vel 127
172: 97 4A 7F [Note On] chan 8 note 74 vel 127
173: 97 4B 7F [Note On] chan 8 note 75 vel 127
174: 97 4D 7F [Note On] chan 8 note 77 vel 127
175: 97 4E 7F [Note On] chan 8 note 78 vel 127
176: 97 4F 7F [Note On] chan 8 note 79 vel 127
177: 97 50 7F [Note On] chan 8 note 80 vel 127
178: 97 51 7F [Note On] chan 8 note 81 vel 127
179: 97 52 7F [Note On] chan 8 note 82 vel 127
180: 97 53 7F [Note On] chan 8 note 83 vel 127
181: 97 54 7F [Note On] chan 8 note 84 vel 127
182: 97 55 7F [Note On] chan 8 note 85 vel 127
183: 97 56 7F [Note On] chan 8 note 86 vel 127
184: 97 57 7F [Note On] chan 8 note 87 vel 127
185: 97 58 7F [Note On] chan 8 note 88 vel 127
186: 97 59 7F [Note On] chan 8 note 89 vel 127
187: 97 5A 7F [Note On] chan 8 note 90 vel 127
188: 97 5B 7F [Note On] chan 8 note 91 vel 127
189: 97 5C 7F [Note On] chan 8 note 92 vel 127
190: 97 5D 7F [Note On] chan 8 note 93 vel 127
191: 97 5E 7F [Note On] chan 8 note 94 vel 127
192: 97 5F 7F [Note On] chan 8 note 95 vel 127
193: 97 60 7F [Note On] chan 8 note 96 vel 127
194: 97 61 7F [Note On] chan 8 note 97 vel 127
195: 97 62 7F [Note On] chan 8 note 98 vel 127
196: 97 63 7F [Note On] chan 8 note 99 vel 127
197: 97 64 7F [Note On] chan 8 note 100 vel 127
198: 97 64 7F [Note On] chan 8 note 100 vel 127
199: 97 64 7F [Note On] chan 8 note 100 vel 127
200: 97 64 7F [Note On] chan 8 note 100 vel 127
201: 97 64 7F [Note On] chan 8 note 100 vel 127
202: 97 64 7F [Note On] chan 8 note 100 vel 127
203: 97 64 7F [Note On] chan 8 note 100 vel 127
204: 97 64 7F [Note On] chan 8 note 100 vel 127
205: 97 64 7F [Note On] chan 8 note 100 vel 127
206: 97 64 7F [Note On] chan 8 note 100 vel 127
207: 97 64 7F [Note On] chan 8 note 100 vel 127
208: 97 64 7F [Note On] chan 8 note 100 vel 127
209: 97 64 7F [Note On] chan 8 note 100 vel 127

[helgoboss]

Originally Posted by blinddrew

Hi Helgoboss,
Yep, it's an endless encoder. The output is a midi note on channel 7 up to note 99 then it changes to channel 8 up to note 100. If you keep scrolling past that it keeps sending that last note.

Here's the log:
0: 96 02 7F [Note On] chan 7 note 2 vel 127
1: 96 03 7F [Note On] chan 7 note 3 vel 127
2: 96 04 7F [Note On] chan 7 note 4 vel 127
3: 96 05 7F [Note On] chan 7 note 5 vel 127
4: 96 06 7F [Note On] chan 7 note 6 vel 127
5: 96 07 7F [Note On] chan 7 note 7 vel 127
6: 96 08 7F [Note On] chan 7 note 8 vel 127
7: 96 09 7F [Note On] chan 7 note 9 vel 127
8: 96 0A 7F [Note On] chan 7 note 10 vel 127
9: 96 0B 7F [Note On] chan 7 note 11 vel 127
10: 96 0C 7F [Note On] chan 7 note 12 vel 127
11: 96 0E 7F [Note On] chan 7 note 14 vel 127
12: 96 0F 7F [Note On] chan 7 note 15 vel 127
13: 96 10 7F [Note On] chan 7 note 16 vel 127
14: 96 11 7F [Note On] chan 7 note 17 vel 127
15: 96 12 7F [Note On] chan 7 note 18 vel 127
16: 96 13 7F [Note On] chan 7 note 19 vel 127
17: 96 14 7F [Note On] chan 7 note 20 vel 127
18: 96 15 7F [Note On] chan 7 note 21 vel 127
19: 96 16 7F [Note On] chan 7 note 22 vel 127
20: 96 17 7F [Note On] chan 7 note 23 vel 127
21: 96 18 7F [Note On] chan 7 note 24 vel 127
22: 96 19 7F [Note On] chan 7 note 25 vel 127
23: 96 1A 7F [Note On] chan 7 note 26 vel 127
24: 96 1B 7F [Note On] chan 7 note 27 vel 127
25: 96 1C 7F [Note On] chan 7 note 28 vel 127
26: 96 1D 7F [Note On] chan 7 note 29 vel 127
27: 96 1E 7F [Note On] chan 7 note 30 vel 127
28: 96 1F 7F [Note On] chan 7 note 31 vel 127
29: 96 20 7F [Note On] chan 7 note 32 vel 127
30: 96 21 7F [Note On] chan 7 note 33 vel 127
31: 96 22 7F [Note On] chan 7 note 34 vel 127
32: 96 23 7F [Note On] chan 7 note 35 vel 127
33: 96 24 7F [Note On] chan 7 note 36 vel 127
34: 96 25 7F [Note On] chan 7 note 37 vel 127
35: 96 26 7F [Note On] chan 7 note 38 vel 127
36: 96 27 7F [Note On] chan 7 note 39 vel 127
37: 96 28 7F [Note On] chan 7 note 40 vel 127
38: 96 29 7F [Note On] chan 7 note 41 vel 127
39: 96 2A 7F [Note On] chan 7 note 42 vel 127
40: 96 2B 7F [Note On] chan 7 note 43 vel 127
41: 96 2C 7F [Note On] chan 7 note 44 vel 127
42: 96 2D 7F [Note On] chan 7 note 45 vel 127
43: 96 2E 7F [Note On] chan 7 note 46 vel 127
44: 96 2F 7F [Note On] chan 7 note 47 vel 127
45: 96 30 7F [Note On] chan 7 note 48 vel 127
46: 96 31 7F [Note On] chan 7 note 49 vel 127
47: 96 32 7F [Note On] chan 7 note 50 vel 127
48: 96 33 7F [Note On] chan 7 note 51 vel 127
49: 96 34 7F [Note On] chan 7 note 52 vel 127
50: 96 35 7F [Note On] chan 7 note 53 vel 127
51: 96 36 7F [Note On] chan 7 note 54 vel 127
52: 96 37 7F [Note On] chan 7 note 55 vel 127
53: 96 38 7F [Note On] chan 7 note 56 vel 127
54: 96 39 7F [Note On] chan 7 note 57 vel 127
55: 96 3A 7F [Note On] chan 7 note 58 vel 127
56: 96 3B 7F [Note On] chan 7 note 59 vel 127
57: 96 3C 7F [Note On] chan 7 note 60 vel 127
58: 96 3D 7F [Note On] chan 7 note 61 vel 127
59: 96 3E 7F [Note On] chan 7 note 62 vel 127
60: 96 3F 7F [Note On] chan 7 note 63 vel 127
61: 96 40 7F [Note On] chan 7 note 64 vel 127
62: 96 41 7F [Note On] chan 7 note 65 vel 127
63: 96 42 7F [Note On] chan 7 note 66 vel 127
64: 96 43 7F [Note On] chan 7 note 67 vel 127
65: 96 44 7F [Note On] chan 7 note 68 vel 127
66: 96 45 7F [Note On] chan 7 note 69 vel 127
67: 96 46 7F [Note On] chan 7 note 70 vel 127
68: 96 47 7F [Note On] chan 7 note 71 vel 127
69: 96 48 7F [Note On] chan 7 note 72 vel 127
70: 96 49 7F [Note On] chan 7 note 73 vel 127
71: 96 4A 7F [Note On] chan 7 note 74 vel 127
72: 96 4B 7F [Note On] chan 7 note 75 vel 127
73: 96 4C 7F [Note On] chan 7 note 76 vel 127
74: 96 4D 7F [Note On] chan 7 note 77 vel 127
75: 96 4E 7F [Note On] chan 7 note 78 vel 127
76: 96 4F 7F [Note On] chan 7 note 79 vel 127
77: 96 50 7F [Note On] chan 7 note 80 vel 127
78: 96 51 7F [Note On] chan 7 note 81 vel 127
79: 96 52 7F [Note On] chan 7 note 82 vel 127
80: 96 53 7F [Note On] chan 7 note 83 vel 127
81: 96 54 7F [Note On] chan 7 note 84 vel 127
82: 96 55 7F [Note On] chan 7 note 85 vel 127
83: 96 56 7F [Note On] chan 7 note 86 vel 127
84: 96 57 7F [Note On] chan 7 note 87 vel 127
85: 96 58 7F [Note On] chan 7 note 88 vel 127
86: 96 59 7F [Note On] chan 7 note 89 vel 127
87: 96 5A 7F [Note On] chan 7 note 90 vel 127
88: 96 5B 7F [Note On] chan 7 note 91 vel 127
89: 96 5C 7F [Note On] chan 7 note 92 vel 127
90: 96 5D 7F [Note On] chan 7 note 93 vel 127
91: 96 5E 7F [Note On] chan 7 note 94 vel 127
92: 96 5F 7F [Note On] chan 7 note 95 vel 127
93: 96 60 7F [Note On] chan 7 note 96 vel 127
94: 96 61 7F [Note On] chan 7 note 97 vel 127
95: 96 62 7F [Note On] chan 7 note 98 vel 127
96: 96 63 7F [Note On] chan 7 note 99 vel 127
97: 97 00 7F [Note On] chan 8 note 0 vel 127
98: 97 00 7F [Note On] chan 8 note 0 vel 127
99: 97 01 7F [Note On] chan 8 note 1 vel 127
100: 97 02 7F [Note On] chan 8 note 2 vel 127
101: 97 03 7F [Note On] chan 8 note 3 vel 127
102: 97 04 7F [Note On] chan 8 note 4 vel 127
103: 97 05 7F [Note On] chan 8 note 5 vel 127
104: 97 06 7F [Note On] chan 8 note 6 vel 127
105: 97 07 7F [Note On] chan 8 note 7 vel 127
106: 97 08 7F [Note On] chan 8 note 8 vel 127
107: 97 09 7F [Note On] chan 8 note 9 vel 127
108: 97 0A 7F [Note On] chan 8 note 10 vel 127
109: 97 0B 7F [Note On] chan 8 note 11 vel 127
110: 97 0C 7F [Note On] chan 8 note 12 vel 127
111: 97 0D 7F [Note On] chan 8 note 13 vel 127
112: 97 0E 7F [Note On] chan 8 note 14 vel 127
113: 97 0F 7F [Note On] chan 8 note 15 vel 127
114: 97 10 7F [Note On] chan 8 note 16 vel 127
115: 97 11 7F [Note On] chan 8 note 17 vel 127
116: 97 12 7F [Note On] chan 8 note 18 vel 127
117: 97 13 7F [Note On] chan 8 note 19 vel 127
118: 97 14 7F [Note On] chan 8 note 20 vel 127
119: 97 15 7F [Note On] chan 8 note 21 vel 127
120: 97 16 7F [Note On] chan 8 note 22 vel 127
121: 97 17 7F [Note On] chan 8 note 23 vel 127
122: 97 18 7F [Note On] chan 8 note 24 vel 127
123: 97 19 7F [Note On] chan 8 note 25 vel 127
124: 97 1A 7F [Note On] chan 8 note 26 vel 127
125: 97 1B 7F [Note On] chan 8 note 27 vel 127
126: 97 1C 7F [Note On] chan 8 note 28 vel 127
127: 97 1D 7F [Note On] chan 8 note 29 vel 127
128: 97 1E 7F [Note On] chan 8 note 30 vel 127
129: 97 1F 7F [Note On] chan 8 note 31 vel 127
130: 97 20 7F [Note On] chan 8 note 32 vel 127
131: 97 21 7F [Note On] chan 8 note 33 vel 127
132: 97 22 7F [Note On] chan 8 note 34 vel 127
133: 97 23 7F [Note On] chan 8 note 35 vel 127
134: 97 24 7F [Note On] chan 8 note 36 vel 127
135: 97 25 7F [Note On] chan 8 note 37 vel 127
136: 97 26 7F [Note On] chan 8 note 38 vel 127
137: 97 27 7F [Note On] chan 8 note 39 vel 127
138: 97 28 7F [Note On] chan 8 note 40 vel 127
139: 97 29 7F [Note On] chan 8 note 41 vel 127
140: 97 2A 7F [Note On] chan 8 note 42 vel 127
141: 97 2B 7F [Note On] chan 8 note 43 vel 127
142: 97 2C 7F [Note On] chan 8 note 44 vel 127
143: 97 2D 7F [Note On] chan 8 note 45 vel 127
144: 97 2E 7F [Note On] chan 8 note 46 vel 127
145: 97 2F 7F [Note On] chan 8 note 47 vel 127
146: 97 30 7F [Note On] chan 8 note 48 vel 127
147: 97 31 7F [Note On] chan 8 note 49 vel 127
148: 97 32 7F [Note On] chan 8 note 50 vel 127
149: 97 33 7F [Note On] chan 8 note 51 vel 127
150: 97 34 7F [Note On] chan 8 note 52 vel 127
151: 97 35 7F [Note On] chan 8 note 53 vel 127
152: 97 36 7F [Note On] chan 8 note 54 vel 127
153: 97 37 7F [Note On] chan 8 note 55 vel 127
154: 97 38 7F [Note On] chan 8 note 56 vel 127
155: 97 39 7F [Note On] chan 8 note 57 vel 127
156: 97 3A 7F [Note On] chan 8 note 58 vel 127
157: 97 3B 7F [Note On] chan 8 note 59 vel 127
158: 97 3C 7F [Note On] chan 8 note 60 vel 127
159: 97 3D 7F [Note On] chan 8 note 61 vel 127
160: 97 3E 7F [Note On] chan 8 note 62 vel 127
161: 97 3F 7F [Note On] chan 8 note 63 vel 127
162: 97 40 7F [Note On] chan 8 note 64 vel 127
163: 97 41 7F [Note On] chan 8 note 65 vel 127
164: 97 42 7F [Note On] chan 8 note 66 vel 127
165: 97 43 7F [Note On] chan 8 note 67 vel 127
166: 97 44 7F [Note On] chan 8 note 68 vel 127
167: 97 45 7F [Note On] chan 8 note 69 vel 127
168: 97 46 7F [Note On] chan 8 note 70 vel 127
169: 97 47 7F [Note On] chan 8 note 71 vel 127
170: 97 48 7F [Note On] chan 8 note 72 vel 127
171: 97 49 7F [Note On] chan 8 note 73 vel 127
172: 97 4A 7F [Note On] chan 8 note 74 vel 127
173: 97 4B 7F [Note On] chan 8 note 75 vel 127
174: 97 4D 7F [Note On] chan 8 note 77 vel 127
175: 97 4E 7F [Note On] chan 8 note 78 vel 127
176: 97 4F 7F [Note On] chan 8 note 79 vel 127
177: 97 50 7F [Note On] chan 8 note 80 vel 127
178: 97 51 7F [Note On] chan 8 note 81 vel 127
179: 97 52 7F [Note On] chan 8 note 82 vel 127
180: 97 53 7F [Note On] chan 8 note 83 vel 127
181: 97 54 7F [Note On] chan 8 note 84 vel 127
182: 97 55 7F [Note On] chan 8 note 85 vel 127
183: 97 56 7F [Note On] chan 8 note 86 vel 127
184: 97 57 7F [Note On] chan 8 note 87 vel 127
185: 97 58 7F [Note On] chan 8 note 88 vel 127
186: 97 59 7F [Note On] chan 8 note 89 vel 127
187: 97 5A 7F [Note On] chan 8 note 90 vel 127
188: 97 5B 7F [Note On] chan 8 note 91 vel 127
189: 97 5C 7F [Note On] chan 8 note 92 vel 127
190: 97 5D 7F [Note On] chan 8 note 93 vel 127
191: 97 5E 7F [Note On] chan 8 note 94 vel 127
192: 97 5F 7F [Note On] chan 8 note 95 vel 127
193: 97 60 7F [Note On] chan 8 note 96 vel 127
194: 97 61 7F [Note On] chan 8 note 97 vel 127
195: 97 62 7F [Note On] chan 8 note 98 vel 127
196: 97 63 7F [Note On] chan 8 note 99 vel 127
197: 97 64 7F [Note On] chan 8 note 100 vel 127
198: 97 64 7F [Note On] chan 8 note 100 vel 127
199: 97 64 7F [Note On] chan 8 note 100 vel 127
200: 97 64 7F [Note On] chan 8 note 100 vel 127
201: 97 64 7F [Note On] chan 8 note 100 vel 127
202: 97 64 7F [Note On] chan 8 note 100 vel 127
203: 97 64 7F [Note On] chan 8 note 100 vel 127
204: 97 64 7F [Note On] chan 8 note 100 vel 127
205: 97 64 7F [Note On] chan 8 note 100 vel 127
206: 97 64 7F [Note On] chan 8 note 100 vel 127
207: 97 64 7F [Note On] chan 8 note 100 vel 127
208: 97 64 7F [Note On] chan 8 note 100 vel 127
209: 97 64 7F [Note On] chan 8 note 100 vel 127

Wow, and there's no way to change it in some kind of editor? Who came up with this? It's probably an attempt to be compatible with the restrictions of Cubase.

Combining source "Note number" with glue mode "Make relative" should work ... but only little bit. The main challenge here is the change in channel. I will need to think about this and make some experiments.

[blinddrew]

Originally Posted by helgoboss

Wow, and there's no way to change it in some kind of editor? Who came up with this? It's probably an attempt to be compatible with the restrictions of Cubase.

Yep, it was designed to work with Cubase, I'm abusing the designer's intent! :¬)

Originally Posted by helgoboss

Combining source "Note number" with glue mode "Make relative" should work ... but only little bit. The main challenge here is the change in channel. I will need to think about this and make some experiments.

I could probably live without the change in channel, it's not often I'm dealing with more than about 60 channels so I'd still have a lot of slack on the first channel.
I'll have a look at the combo you've suggested.
Thanks again.

[Rockum]

I am using a Novation Remote Zero with Automap. Realearn works great in conjunction with Automap for both control and feedback of knobs, faders, and buttons. I would also love to be able to set the display, but after experimenting for a few hours, I can't figure out how. Since it is not one of the supported display types, I didn't use the display source. I tried sending MIDI sysex commands.

Unfortunately, I may not be sending the right ones. Finding technical documentation for the abandoned Automap is difficult. Here are the few resources I was able to uncover.

https://web.archive.org/web/20110923...s/automap_sdk/

There are two downloadable versions of the SDK there:

https://web.archive.org/web/20110923...ile.php?id=731

https://web.archive.org/web/20110923...ile.php?id=345

I read in the discussion below that the newer of these SKD's is corrupted. Someone in the conversation also stated that an even newer version was later released fixing the problem. Unfortunately, it does not seem to have been captured by Web.Archive.org's Wayback Machine.

I requested the author who mentioned the latest update send me a copy if he still has it. I will provide it if he does.

https://www.kvraudio.com/forum/viewtopic.php?p=6014868

I also found a discussion on changing the display using Max here:

https://cycling74.com/forums/novation-automap-external

However, I was unable to adapt any of the commands and successfully use them as sysex commands in Realearn.

I also tried wrapping Realearn with Automap just like any other VST, but that also didn't work. Any help appreciated.

[7enz]

@Helgoboss
i have been modifying my template with my realearn instances...
and what i picked up on.. based on the Poll use

is that if you have a send that is polled and then decide to remove the send from using Reapers internal routing matrix ...
it would naturally come up with a error message in the console.. as the polling is relying upon there being a existing send by which it can gather the state

however removing it... goes through the error and
deny's access to realearn instance to remove the offending poll midi source... forcing you to close down and reload which isnt a bad thing..

but i think this is something that should be mentioned in the userguide perhaps??
from memory polling option can sometimes be a default in some options, thus people not being aware of the issue of poll and what it does will be oblivious to any removal of what the poll tickbox does and is tied with... and how it can error out.. if the poll is reliant upon a event being still in existence even though i have removed it

in my case, i was using the poll as a send... so that i know a hardwareout-send is in use& a toggling LED is lit (a very useful option in my view)
upon removing the hardware send within Reapers routing matrix for modification purposes... the reaconsole kicks in alerting me to a send type error message.

i dont know what can be done at the point of the reaconsole error message showing as it goes in a continous loop(understandably)

but i do think a userguide mention of the occurrence might be in order?? *shrugs

[helgoboss]

Originally Posted by Rockum

I am using a Novation Remote Zero with Automap. Realearn works great in conjunction with Automap for both control and feedback of knobs, faders, and buttons. I would also love to be able to set the display, but after experimenting for a few hours, I can't figure out how. Since it is not one of the supported display types, I didn't use the display source. I tried sending MIDI sysex commands.

Unfortunately, I may not be sending the right ones. Finding technical documentation for the abandoned Automap is difficult. Here are the few resources I was able to uncover.

https://web.archive.org/web/20110923...s/automap_sdk/

There are two downloadable versions of the SDK there:

https://web.archive.org/web/20110923...ile.php?id=731

https://web.archive.org/web/20110923...ile.php?id=345

I read in the discussion below that the newer of these SKD's is corrupted. Someone in the conversation also stated that an even newer version was later released fixing the problem. Unfortunately, it does not seem to have been captured by Web.Archive.org's Wayback Machine.

I requested the author who mentioned the latest update send me a copy if he still has it. I will provide it if he does.

https://www.kvraudio.com/forum/viewtopic.php?p=6014868

I also found a discussion on changing the display using Max here:

https://cycling74.com/forums/novation-automap-external

However, I was unable to adapt any of the commands and successfully use them as sysex commands in Realearn.

I also tried wrapping Realearn with Automap just like any other VST, but that also didn't work. Any help appreciated.

In order to implement your own display sysex source, you need to use the MIDI script source in Lua mode. The mini editor which you can open by pressing the dots button should contain a link to some more or less helpful documentation.

[helgoboss]

Originally Posted by 7enz

@Helgoboss
i have been modifying my template with my realearn instances...
and what i picked up on.. based on the Poll use

is that if you have a send that is polled and then decide to remove the send from using Reapers internal routing matrix ...
it would naturally come up with a error message in the console.. as the polling is relying upon there being a existing send by which it can gather the state

however removing it... goes through the error and
deny's access to realearn instance to remove the offending poll midi source... forcing you to close down and reload which isnt a bad thing..

but i think this is something that should be mentioned in the userguide perhaps??
from memory polling option can sometimes be a default in some options, thus people not being aware of the issue of poll and what it does will be oblivious to any removal of what the poll tickbox does and is tied with... and how it can error out.. if the poll is reliant upon a event being still in existence even though i have removed it

in my case, i was using the poll as a send... so that i know a hardwareout-send is in use& a toggling LED is lit (a very useful option in my view)
upon removing the hardware send within Reapers routing matrix for modification purposes... the reaconsole kicks in alerting me to a send type error message.

i dont know what can be done at the point of the reaconsole error message showing as it goes in a continous loop(understandably)

but i do think a userguide mention of the occurrence might be in order?? *shrugs

Oops, that would actually be a bug. Could you please open an issue on GitHub. Since it's a bug, I would look at it asap.

[7enz]

Originally Posted by helgoboss

Oops, that would actually be a bug. Could you please open an issue on GitHub. Since it's a bug, I would look at it asap.

done!

[7enz]

@Helgoboss
im unsure if the control transformation option in realearn would help solve a problem im trying to sort.

basically im trying to find a way of dealing with 3 audio-sends from the same source..(replicating audio x3)
in which i want to get the average of the 3 sends as a volume... so that the output volume on the receiving side wont double or triple in volume output

i should also mention the 3 sends come in on 3 separate tracks...
so im wanting a method of taking the average of 3 track volumes(receiving the send) and have them average out.

hopefully that makes sense

[helgoboss]

Originally Posted by 7enz

@Helgoboss
im unsure if the control transformation option in realearn would help solve a problem im trying to sort.

basically im trying to find a way of dealing with 3 audio-sends from the same source..(replicating audio x3)
in which i want to get the average of the 3 sends as a volume... so that the output volume on the receiving side wont double or triple in volume output

i should also mention the 3 sends come in on 3 separate tracks...
so im wanting a method of taking the average of 3 track volumes(receiving the send) and have them average out.

hopefully that makes sense

Mmh, REAPER's track grouping doesn't solve this, right? It only can be used for track volumes.

You might have some success with ReaLearn's group interaction set to "Inverse target value" but that only works for averaging out 2 send volume faders. How should it even behave with 3?

[7enz]

Originally Posted by helgoboss

Mmh, REAPER's track grouping doesn't solve this, right? It only can be used for track volumes.

You might have some success with ReaLearn's group interaction set to "Inverse target value" but that only works for averaging out 2 send volume faders. How should it even behave with 3?

my use case... is tied with realtime manipulation of audio and creating variations of the 3 or more audio-sends... and avoiding the need to adjust pre-fader or each post fader to mask the output sound difference when another send is introduced or removed.

its okay... ill test a couple of alternative scripts... to see if there is a workaround
cheeRs

[KennyG5000]

Originally Posted by helgoboss

x < 0.5 ? (
  y = 1 - 2*x;
) : (
  y = 2*x - 1;
);

This should result in a V shape.

Thanks for this Helgoboss, this is exactly what I needed, greatly appreciated!

[7enz]

@Helgoboss

just curious about the poll element being ticked...

knowing that it tends to stress the cpu because its constantly updating

i wondered if selections of polled elements could be filtered or set into 2 different categories..
some for constantly always polled
others for polled for x amount of seconds?

so that if a toggle button is pressed the poll element kicks into action over for a set period of time.... as opposed to continously

would this in anyway lessen the cpu load??

[helgoboss]

Originally Posted by 7enz

@Helgoboss

just curious about the poll element being ticked...

knowing that it tends to stress the cpu because its constantly updating

i wondered if selections of polled elements could be filtered or set into 2 different categories..
some for constantly always polled
others for polled for x amount of seconds?

so that if a toggle button is pressed the poll element kicks into action over for a set period of time.... as opposed to continously

would this in anyway lessen the cpu load??

Did you really experience CPU issues related to this? It shouldn't actually matter. REAPER runs in a loop anyway and does hundreds of things on each loop cycle. Adding one send state query to the mix should be nothing compared to that. Extensions such as CSI even use polling all over the place, they don't use REAPER's notification system at all, they still don't have performance issues as far as I know.

[7enz]

Originally Posted by helgoboss

Did you really experience CPU issues related to this? It shouldn't actually matter. REAPER runs in a loop anyway and does hundreds of things on each loop cycle. Adding one send state query to the mix should be nothing compared to that. Extensions such as CSI even use polling all over the place, they don't use REAPER's notification system at all, they still don't have performance issues as far as I know.

no i'm not experiencing any cpu issues...
the thinking was related to if a track was selected, and had 2 specific FX's on it, a script would execute.. and was thinking that polling existing tracks was the first step to going about it?? The idea of polling all the tracks would not be a good idea... given i have 250+ tracks
The script is already tied to a "invoke reaper action"

to be honest i dont even know if polling a track/s would help...

im thinking now maybe just manually execute the script, once track is selected

[helgoboss]

Originally Posted by 7enz

no i'm not experiencing any cpu issues...
the thinking was related to if a track was selected, and had 2 specific FX's on it, a script would execute.. and was thinking that polling existing tracks was the first step to going about it?? The idea of polling all the tracks would not be a good idea... given i have 250+ tracks
The script is already tied to a "invoke reaper action"

to be honest i dont even know if polling a track/s would help...

im thinking now maybe just manually execute the script, once track is selected

ReaLearn doesn't iterate over all tracks in each cycle of the loop, no worries.

Don't worry about the "Polling" checkbox, it's not going to be a problem in most cases.

[foxAsteria]

Anyone else have a totally blank UI for ReaLearn? I've removed all traces and reinstalled, but every version is the same; blank window that says Status 1 Status 2 at the bottom.

[helgoboss]

Originally Posted by foxAsteria

Anyone else have a totally blank UI for ReaLearn? I've removed all traces and reinstalled, but every version is the same; blank window that says Status 1 Status 2 at the bottom.

Did you update REAPER, maybe even to a pre-release?

[foxAsteria]

Originally Posted by helgoboss

Did you update REAPER, maybe even to a pre-release?

No but I had to delete all the realearn and "helgoboss" folders to recover it. Fortunately I was doing most of the programming on a different computer so I didn't lose my data.

[helgoboss]

Released ReaLearn 2.15.0-pre.2 (ReaPack installation instructions)

Changes:
- #840 Added new option "Consider target invocations" to targets "ReaLearn: Modify mapping" and "Global: Last touched", e.g. in order to make it possible to ignore target invocations that were caused by ReaLearn itself
- #840 Improved global target capturing (via ReaLearn REAPER actions) by also adding support for learning transport controls and REAPER action invocations
- #840 Improved UI-triggered target learning (doesn't pick up target touches anymore that are caused by another ReaLearn instance)
- #744 Improved targets "ReaLearn: Modify mapping" and "Global: Last touched" by including all target types by default (otherwise users can have the impressions it doesn't work at all)
- #841 Fixed issues with new REAPER v6.78+ dev builds (was totally broken)
- #835 Fixed glue section user interface inconsistency
- #838 Fixed possible errors with send targets when removing a hardware output send from a track

[Bassman002]

Originally Posted by helgoboss

Released ReaLearn 2.15.0-pre.2 (ReaPack installation instructions)

- #841 Fixed issues with new REAPER v6.78+ dev builds (was totally broken)

Fantastic Thank you very much!

Bassman.

[Rockum]

Thank you for the updates.

I appreciate your help regarding Automap displays. However, I'm not sure it is possible from a user standpoint using only sysex messages. If you don't mind taking a look, I've researched and found the final Automap SDK. I posted it on my website for you and would appreciate if you could skim over the included docs and consider supporting its library. Either way, Realearn is a wonderful tool. Thank you again.

http://rockkennedy.com/files/AutomapSDK.zip

[Sound asleep]

I was gonna ask this, but then figured I may as well try it, and it worked, so I figured I may as well mention it for others that may come across this.

For target tracks being "named" you can use "*" to designate "anything".

So, for me, whatever track I call "keys R" that will put record arm on my Keys fader on my nanokontrol. if I set target as "Keys R" it needs to be named only that. If I set target as "*Keys R*" Then I can call the track "kontakt Keys R" and that will work, or like "Rhodes Keys R Pre-chorus" whatever.

[mozart999uk]

Hi all, Wondering if this is possible.

I have waves scheps omni channel mapped to my midi fighter twister via realearn.

When you use a mouse on the knobs, they display a value in a little box above the knob. However, when turning the knob via my MFT they don't.

Also on the EQ section, if I use the mouse to adjust a knob and hold control down, it solos just that frequency, which again it doesn't do if I just move knobs on my MFT.

Is there anyway to get realearn to simulate a mouse press when I turn one of the MFT knobs as well as actually turn the knob in the gui of omni channel?

[Kickaxe]

Hi helgoboss, I'm having an issue with Realearn when using a SysEx knob on my device to control the master volume fader in Reaper. Everything seems to work when learning the source (SysEx knob) and target (master volume fader in Reaper). However, it doesn't seem to work properly. The source learn is correctly identified as Midi, type Raw MIDI/SysEx and the character as Range element (knob fader, etc). But when I go to use it, it puts the fader to 100% only. I'm guessing I need to put the whole range of SysEx codes for the knob into the pattern box. In midi-ox, when I rotate the SysEx knob, it shows a range of values from F0 41 10 00 00 00 05 12 20 01 18 01 00 46 F7 (min) to F0 41 10 00 00 00 05 12 20 01 18 01 64 62 F7 (max) with many other codes in between. What is the correct syntax to enter SysEx codes between these two ranges into the pattern box? Thanks for your help.

Edit: I read the manual section on Extracting and encoding a value but I don't really understand it. I realize I need to replace the last two patterns before the ending F7 with bracketed letters eg [00nm lkji] [hgfe dcba] but can't seem to get it to work properly. Any help would be appreciated.

[Rockum]

Two days of experimentation. Was able to figure out how to do quite a few very cool things. The Launchpad is determining the function of the endless encoders on another controller. It also now sends itself sysex to change its custom mode.

After the session, I wondered if there was a way to add a couple of target track selection options options. I want to control the FX by name as long as it is the focused FX, but I don't have the option to have this happen without selecting a track. Could we have any <any> option? Perhaps the option <parent track of focused FX> would also be nice.

Looking forward to working more on this and diving deeper in the coming weeks.

[BenjyO]

Is there a way to get textual feedback for {{target.track.index}} but one-based? I want to see the track number as it is shown in Reaper's TCP or MCP which is not zero-based.

[7enz]

Originally Posted by Kickaxe

Hi helgoboss, I'm having an issue with Realearn when using a SysEx knob on my device to control the master volume fader in Reaper. Everything seems to work when learning the source (SysEx knob) and target (master volume fader in Reaper). However, it doesn't seem to work properly. The source learn is correctly identified as Midi, type Raw MIDI/SysEx and the character as Range element (knob fader, etc). But when I go to use it, it puts the fader to 100% only. I'm guessing I need to put the whole range of SysEx codes for the knob into the pattern box. In midi-ox, when I rotate the SysEx knob, it shows a range of values from F0 41 10 00 00 00 05 12 20 01 18 01 00 46 F7 (min) to F0 41 10 00 00 00 05 12 20 01 18 01 64 62 F7 (max) with many other codes in between. What is the correct syntax to enter SysEx codes between these two ranges into the pattern box? Thanks for your help.

Edit: I read the manual section on Extracting and encoding a value but I don't really understand it. I realize I need to replace the last two patterns before the ending F7 with bracketed letters eg [00nm lkji] [hgfe dcba] but can't seem to get it to work properly. Any help would be appreciated.

have you tried entering the sysex values into the Source area... in the type dropdown box
Raw midi/sysex
edit: sorry... i just re-read your post and noticed you attempted this

[drummerboy]

Hi!

I‘m using Realearn to control my SSL Sigma via OSC. Works great!
I‘m using Reaper‘s channel faders of tracks named „Sigma*“ to do this.
In order to send automation to the Sigma, the fader needs to be in Read mode.
Id there any way to send the actual volume automation when the fader is in Trim/Read mode instead of Read?

Best,
Frank

[Kickaxe]

Originally Posted by 7enz

have you tried entering the sysex values into the Source area... in the type dropdown box
Raw midi/sysex
edit: sorry... i just re-read your post and noticed you attempted this

Thanks 7enz. I got it to work finally. This may help someone else. What I had to do was substitute the two values before the F7 with [0nml kjih] [0gfe dcba] and that made it work but I wasn't able to get the full range on the fader. When I reduced the Source max to around 12000, then I was able to get the full range.

[7enz]

Originally Posted by Rockum

Two days of experimentation. Was able to figure out how to do quite a few very cool things. The Launchpad is determining the function of the endless encoders on another controller. It also now sends itself sysex to change its custom mode.

After the session, I wondered if there was a way to add a couple of target track selection options options. I want to control the FX by name as long as it is the focused FX, but I don't have the option to have this happen without selecting a track. Could we have any <any> option? Perhaps the option <parent track of focused FX> would also be nice.

Looking forward to working more on this and diving deeper in the coming weeks.

put a separate instance of realearn on the inputFX and then tick Fx must focus or however you want to work it
note: the track must be armed for the midi to be received(i think)

[Nick Morris]

Originally Posted by drummerboy

Hi!

I‘m using Realearn to control my SSL Sigma via OSC. Works great!
I‘m using Reaper‘s channel faders of tracks named „Sigma*“ to do this.
In order to send automation to the Sigma, the fader needs to be in Read mode.
Id there any way to send the actual volume automation when the fader is in Trim/Read mode instead of Read?

Best,
Frank

As it stands the automation/fader position being sent to Sigma relies on the fader moving in Reaper. So Trim/Read will NOT send anything. I do not see any way to have the VOLUME ENVELOPE transmit its value. And further thought, I can't see how this would work with the Sigma if you want to have the automation play back but still use those faders to trim. If you were able to send the trim fader positions and automation data, which positions would the Sigma use? You would want the automation data to be merged then, the tracks fader position plus the trim fader position since the Sigma has only one absolute fader per track. Ideally, you would want REAPER to trim the actual Volume Fader, rather than have its own trim envelope lane, and altering the volume fader envelope that controls the Sigma fader. Not seeing a way that this is possible at all.

Maybe there is a complex way of reading the data of two instances of realearn and combining it? No clue.

Trimming envelopes by mouse over here using the trim volume lane and the "Track: Apply trim envelope to volume envelope, clear trim envelope" action for now.

Realearn and Sigma are awesome together, much nicer than the SSL plugins for control of the Sigma.

[drummerboy]

Originally Posted by Nick Morris

As it stands the automation/fader position being sent to Sigma relies on the fader moving in Reaper. So Trim/Read will NOT send anything. I do not see any way to have the VOLUME ENVELOPE transmit its value. And further thought, I can't see how this would work with the Sigma if you want to have the automation play back but still use those faders to trim. If you were able to send the trim fader positions and automation data, which positions would the Sigma use? You would want the automation data to be merged then, the tracks fader position plus the trim fader position since the Sigma has only one absolute fader per track. Ideally, you would want REAPER to trim the actual Volume Fader, rather than have its own trim envelope lane, and altering the volume fader envelope that controls the Sigma fader. Not seeing a way that this is possible at all.

Maybe there is a complex way of reading the data of two instances of realearn and combining it? No clue.

Trimming envelopes by mouse over here using the trim volume lane and the "Track: Apply trim envelope to volume envelope, clear trim envelope" action for now.

Realearn and Sigma are awesome together, much nicer than the SSL plugins for control of the Sigma.

Agree, Sigma and Realearn beats the SSL Plugins out of the park.
For instance, I have mapped Track-Width to Sigma Stereo/Mono switch and a normal Reaper Send to map to Mix A and Mix B. Works perfectly!

Before Realearn I controlled the Sigma via Parameter Modulation (I used a sine wave generator to determine the volume of Reaper Tracks (Post Trim/Read) and used that to control the Sigma Faders. It came with a slight performance penalty due to allowing feedback-routing). Any way to do this with Realearn? Maybe it's worth a try.

[moribund]

Is it possible to use more than 1 button to execute the same mapping in ReaLearn without actually creating another identical mapping? I'd like to do something like this:

Push Button 1 OR Button 2 on MIDI controller => execute action A (e.g., bypass FX A) in Reaper.

Thanks

[indigomirage]

Potential issue with ReaLearn and Auto-load with CLAP plugins?

Hi there - I've been mapping my plugins so that they auto-load with presets. In this case, I was trying to configure Surge XT (CLAP format), however I could not find it in the list of FX based on last focus, and when I tried setting Auto-load Based on instance FX< I got the following message...:

Since my other plugins (VST3) had no issue, I'm making a guess that this is an issue with CLAP plugins... (?)

Grateful for any help (or pointers if I'm on the wrong track here).

Cheers!

--- cut ---
REAPER version: 6.78/x64
Module name: ReaLearn
Module version: v2.14.3/x86_64 rev 68c524 (2023-01-13 17:18:04 UTC)
Module base address: 0x7ffb1d030000
Module size: 0x1b63000

Message: already mutably borrowed: BorrowError

0: 0x7ffb1e13f135 - cpp_to_rust_ProjectStateContext_SetTempFlag
1: 0x7ffb1e13d989 - cpp_to_rust_ProjectStateContext_SetTempFlag
2: 0x7ffb1e04b7ff - DllMain
3: 0x7ffb1e163032 - cpp_to_rust_ProjectStateContext_SetTempFlag
4: 0x7ffb1e162dbd - cpp_to_rust_ProjectStateContext_SetTempFlag
5: 0x7ffb1e16082f - cpp_to_rust_ProjectStateContext_SetTempFlag
6: 0x7ffb1e162a80 - cpp_to_rust_ProjectStateContext_SetTempFlag
7: 0x7ffb1e38b825 - cpp_to_rust_ProjectStateContext_SetTempFlag
8: 0x7ffb1e38b9a3 - cpp_to_rust_ProjectStateContext_SetTempFlag
9: 0x7ffb1d6b5d18 - VSTPluginMain
10: 0x7ffb1d2c9e9c - NSEEL_HOSTSTUB_LeaveMutex
11: 0x7ffb1da60150 - VSTPluginMain
12: 0x7ffb1d6b6a92 - VSTPluginMain
13: 0x7ffb1e148ee1 - cpp_to_rust_ProjectStateContext_SetTempFlag
14: 0x1409710bb - <unknown>
15: 0x140989f19 - <unknown>
16: 0x1403f3e37 - <unknown>
17: 0x14041de49 - <unknown>
18: 0x14041dd2c - <unknown>
19: 0x1408bea14 - <unknown>
20: 0x14060bc1b - <unknown>
21: 0x14060d1ef - <unknown>
22: 0x14060e669 - <unknown>
23: 0x7ffb1e041c55 - DllMain
24: 0x7ffb1e052d42 - DllMain
25: 0x7ffb1e025691 - DllMain
26: 0x7ffb1e03934b - DllMain
27: 0x7ffb1e039d8e - DllMain
28: 0x7ffb1d9a1068 - VSTPluginMain
29: 0x7ffb1d9a0923 - VSTPluginMain
30: 0x7ffb1dbeed69 - DllMain
31: 0x7ffb1dbe4ec3 - DllMain
32: 0x7ffb1d4f9163 - VSTPluginMain
33: 0x7ffb1e07ddaf - cpp_to_rust_IReaperControlSurface_Run
34: 0x140306b44 - <unknown>
35: 0x1401fcae5 - <unknown>
36: 0x1401fc048 - <unknown>
37: 0x14046aa4d - <unknown>
38: 0x7ffbc53195e6 - GetMenuItemCount
39: 0x7ffbc5318ed7 - GetMenuItemCount
40: 0x7ffbc5332bc9 - DrawTextA
41: 0x7ffbc5318231 - DispatchMessageW
42: 0x7ffbc5317cf1 - DispatchMessageW
43: 0x140461a89 - <unknown>
44: 0x1409d7e41 - <unknown>
45: 0x7ffbc5e3269d - BaseThreadInitThunk
46: 0x7ffbc6e4a9f8 - RtlUserThreadStart
--- cut ---

[Kickaxe]

Does anyone know if there is a way to use a midi cc from a foot controller to go to a specific region on a track? I'm thinking of having several songs on the same track and wonder if there is a way to play them in any order I want using regions. I know you can trigger automation from a marker or region that I found in my research but I was not able to determine if it's possible to do the opposite.

Thanks