ReaLearn: Target "Track: Set automation touch state" laggy?

[helgoboss]

Mike reported a laggy behavior of that target, backed with a screen recording. The automation touch state is applied delayed.

[mikekravets]

Hello and Thank You for a quick support !!!

I did update to v2.17.0, and issue is still there, but quite strange(Honestly, I did not test these two scenarios on a previous ReaLearn version):

• When I just touch the fader without movement, it works, and showing state change only in TCP;
• When I touch and move the fader, it behaves with delay, and showing state change in TCP and MCP.

I'm doing this test on a clean portable Reaper installation, stock configuration.
Hope you're able to reproduce it, if no - I'll try to check it on the other computer, maybe bug is on my side.

Very short video to show you what I mean.

Best Wishes ! :)

[helgoboss]

Hi, good that you write here. I think you have missed a couple of emails from me, maybe they ended up in your spam folder?

I also noticed that the MCP doesn't change the color, only the TCP. But that appears to be a visual bug in REAPER and not have any implications on automation writing. It's better to ignore that for now.

Concerning automation writing: I tested quite throughly that start (press) and stop (release) happened instantly. I didn't use a preset to test it (e.g. Mackie Control and DAW control). I tested by using the targets "Track: Set volume" and "Track: Set automation touch state" (two mappings) with global automation mode "Touch". Can you try that with your setup? I will not be able to test anything for over a week or so.

[mikekravets]

Hi, probably I have missed some of your emails, I see the only one, information about update few days ago, spam folder is empty, strange ... well, never mind ;)

Yes, you're right about MCP color changing, bug of a Reaper, not a big deal to be honest
(It corresponds only for fader move, not fader touch).

I found where we have this problem - I made just these two mappings(tried it via controller compartment and straight in the main compartment):

• If you turn off "Track: Set volume" mapping, "Track: Set automation touch state" works perfect like it should, but no volume changes of course;
• If you turn off "Track: Set automation touch state" mapping, "Track: Set volume" start work instantly when you move the fader, and here we have this laggy delay after we leave the fader, or just stop moving it(of course because touch is turned off).

So problem is in that particular module, is this a bug of Reaper or you can do something with it - that's the question.

(Maybe when we use only volume change without touch, Reaper behaves like we have some cheap controller with no motors. But since via MCU it's working ok, should be a way to solve this, there are just my thoughts).

I got a copy of your comment on my mail via github service, so our communication should be fine, anyway I have these tabs open in browser.

No rush with the tests at all, and if you need me to check something on my side - just ping, I'm always happy to help you, ReaLearn is the BEST tool I've ever used ! :)

Regards!

[helgoboss]

Thanks for the feedback!

If you just use the "Track: Set volume" target, stopping the fader movement will feel laggy. That's natural. Because there's no way for REAPER to know when you lift your hand from the fader. So it just keeps writing automation for half a second or so and then stops writing.

That's where the "Track: Set automation touch state" target comes in. It must be mapped to your fader's "touch" interaction. That's not the same as the "move" interaction. Your fader (if touch-sensitive) transmits a "touch on" event when you touch it and a "touch off" event when you release it.

If you have automation mode "Touch" enabled in REAPER, both mappings (fader move interaction to "Track: Set volume" and fader touch interaction to "Track: Set automation touch state") combined should result in the desired behavior :

1. Touching the fader starts overwriting existing automation (even if you don't move the fader yet)
2. Moving the fader will create an envelope
3. Stopping to move the fader will still overwrite existing automation
4. Releasing the fader will stop overwriting existing automation

So for the fully story, you need to test both in combination. And it only works if your fader is touch-sensitive (however, you could also use a second button to tell REAPER when to start/stop writing automation).

[mikekravets]

Hello!

Yes, you're right and it makes sense :) "Track: Set automation touch state" should be a main trigger to change the state. Yet I see that somehow "Track: Set volume" override it when you start move the fader and Reaper ignore "touch off" after movement is done.

I did a test on my laptop, fresh portable Reaper install, only one MIDI port is in use, and compared it with MCU, so looks like this bug is not happen only on my main PC(no beep sound because it is recorded via team viewer, sorry).

Regards!

[helgoboss]

The best way to investigate this is to turn on logging via Menu => Logging:

• Real control
• Target invocation

Then touch the fader, wait a moment, move the fader up a bit, wait a moment, release the fader.

Post the logs here.

[mikekravets]

Let me do this now, only I don't see target invocation here:

[mikekravets]

Target control probably, here it is:

===
7116.767 | ReaLearn 0 | Target control | Mapping 1: Hit target successfully [invocation = 19, target = 1, control value = 1] (normal control)
7116.767 | ReaLearn 0 | Real control | [90, 68, 7F] = [144, 104, 127] = NoteOn { channel: Channel(0), key_number: KeyNumber(104), velocity: U7(127) } at 320.372715262s (matched)
7117.800 | ReaLearn 0 | Target control | Mapping 2: Hit target successfully [invocation = 25, target = 1, control value = 0.51171875] (normal control)
7117.800 | ReaLearn 0 | Real control | [E0, 40, 41] = [224, 64, 65] = PitchBendChange { channel: Channel(0), pitch_bend_value: U14(8384) } at 321.432569276s (matched)
7117.926 | ReaLearn 0 | Target control | Mapping 2: Hit target successfully [invocation = 26, target = 1, control value = 0.5107421875] (normal control)
7117.926 | ReaLearn 0 | Real control | [E0, 30, 41] = [224, 48, 65] = PitchBendChange { channel: Channel(0), pitch_bend_value: U14(8368) } at 321.533343854s (matched)
7117.927 | ReaLearn 0 | Target control | Mapping 2: Hit target successfully [invocation = 27, target = 1, control value = 0.509765625] (normal control)
7117.927 | ReaLearn 0 | Real control | [E0, 20, 41] = [224, 32, 65] = PitchBendChange { channel: Channel(0), pitch_bend_value: U14(8352) } at 321.569097988s (matched)
7117.958 | ReaLearn 0 | Target control | Mapping 2: Hit target successfully [invocation = 28, target = 1, control value = 0.5087890625] (normal control)
7117.958 | ReaLearn 0 | Real control | [E0, 10, 41] = [224, 16, 65] = PitchBendChange { channel: Channel(0), pitch_bend_value: U14(8336) } at 321.576765209s (matched)
7117.958 | ReaLearn 0 | Target control | Mapping 2: Hit target successfully [invocation = 29, target = 1, control value = 0.505859375] (normal control)
7117.958 | ReaLearn 0 | Real control | [E0, 60, 40] = [224, 96, 64] = PitchBendChange { channel: Channel(0), pitch_bend_value: U14(8288) } at 321.587346263s (matched)
7117.958 | ReaLearn 0 | Target control | Mapping 2: Hit target successfully [invocation = 30, target = 1, control value = 0.5048828125] (normal control)
7117.958 | ReaLearn 0 | Real control | [E0, 50, 40] = [224, 80, 64] = PitchBendChange { channel: Channel(0), pitch_bend_value: U14(8272) } at 321.594895092s (matched)
7118.022 | ReaLearn 0 | Target control | Mapping 2: Hit target successfully [invocation = 31, target = 1, control value = 0.50390625] (normal control)
7118.022 | ReaLearn 0 | Real control | [E0, 40, 40] = [224, 64, 64] = PitchBendChange { channel: Channel(0), pitch_bend_value: U14(8256) } at 321.623413126s (matched)
7118.022 | ReaLearn 0 | Target control | Mapping 2: Hit target successfully [invocation = 32, target = 1, control value = 0.501953125] (normal control)
7118.022 | ReaLearn 0 | Real control | [E0, 20, 40] = [224, 32, 64] = PitchBendChange { channel: Channel(0), pitch_bend_value: U14(8224) } at 321.631060587s (matched)
7118.022 | ReaLearn 0 | Target control | Mapping 2: Hit target successfully [invocation = 33, target = 1, control value = 0.498046875] (normal control)
7118.022 | ReaLearn 0 | Real control | [E0, 60, 3F] = [224, 96, 63] = PitchBendChange { channel: Channel(0), pitch_bend_value: U14(8160) } at 321.64140043s (matched)
7118.022 | ReaLearn 0 | Target control | Mapping 2: Hit target successfully [invocation = 34, target = 1, control value = 0.4951171875] (normal control)
7118.022 | ReaLearn 0 | Real control | [E0, 30, 3F] = [224, 48, 63] = PitchBendChange { channel: Channel(0), pitch_bend_value: U14(8112) } at 321.649305932s (matched)
7118.022 | ReaLearn 0 | Target control | Mapping 2: Hit target successfully [invocation = 35, target = 1, control value = 0.4921875] (normal control)
7118.022 | ReaLearn 0 | Real control | [E0, 00, 3F] = [224, 0, 63] = PitchBendChange { channel: Channel(0), pitch_bend_value: U14(8064) } at 321.659748315s (matched)
7118.177 | ReaLearn 0 | Target control | Mapping 2: Hit target successfully [invocation = 36, target = 1, control value = 0.4912109375] (normal control)
7118.177 | ReaLearn 0 | Real control | [E0, 70, 3E] = [224, 112, 62] = PitchBendChange { channel: Channel(0), pitch_bend_value: U14(8048) } at 321.78575066s (matched)
7118.178 | ReaLearn 0 | Target control | Mapping 2: Hit target successfully [invocation = 37, target = 1, control value = 0.494140625] (normal control)
7118.178 | ReaLearn 0 | Real control | [E0, 20, 3F] = [224, 32, 63] = PitchBendChange { channel: Channel(0), pitch_bend_value: U14(8096) } at 321.803614918s (matched)
7118.538 | ReaLearn 0 | Target control | Mapping 2: Hit target successfully [invocation = 38, target = 1, control value = 0.4951171875] (normal control)
7118.538 | ReaLearn 0 | Real control | [E0, 30, 3F] = [224, 48, 63] = PitchBendChange { channel: Channel(0), pitch_bend_value: U14(8112) } at 322.134882011s (matched)
7118.538 | ReaLearn 0 | Target control | Mapping 2: Hit target successfully [invocation = 39, target = 1, control value = 0.49609375] (normal control)
7118.538 | ReaLearn 0 | Real control | [E0, 40, 3F] = [224, 64, 63] = PitchBendChange { channel: Channel(0), pitch_bend_value: U14(8128) } at 322.145207206s (matched)
7118.573 | ReaLearn 0 | Target control | Mapping 1: Hit target successfully [invocation = 20, target = 1, control value = 0] (normal control)
7118.573 | ReaLearn 0 | Real control | [90, 68, 00] = [144, 104, 0] = NoteOn { channel: Channel(0), key_number: KeyNumber(104), velocity: U7(0) } at 322.177980123s (matched)

[mikekravets]

Hm, it should be "Note Off", right?

This is just controller and MIDI OX:

[mikekravets]

Oh I remember I had some troubles with Icon I-Control long time ago and written to their support, now the same probably with Platform M+.

Note Off should be 0x80, but it sends always 0x90 but with 00 velocity(If it matters).