Gaps/glitches in processing FX param changes when CPU load high or when windows being dragged

[robotronald]

Using Realearn to automate FX parameters, e.g. Realearn instance on a MIDI track, input = FX input, output = none, with mappings to change the parameters of a JSFX on the same track (via MIDI cc input to the track).

Often when the CPU load is high (or when I drag any Reaper window across the screen) then the FX parameters stop changing for a while, it's as if Realearn stops processing. Reaper's native MIDI link responds fine in the same scenario. I'm not 100% sure but I don't think any messages are being 'lost', just pausing which is most noticeable on any rhythmic/musical parameter changes.

I can recreate this issue consistently by dragging any Reaper window (e.g. FX chain, MIDI editor, etc.) around the screen at any time while a project is playing - Realearn stops making any changes to the FX parameters until I stop dragging the window. This isn't a big issue by itself but the interruptions/glitches when CPU goes over 50% is more of a problem.

Using Reaper 7.07x64 on Windows 10 with the latest (pre-release) version of Realearn.