SUPER SLOWDOWN , Midi CC->send x volume change on multiple tracks (FIXED)

[airon]

Reaper version 5.?? - 5.80 (at least since 5.70)

Problem:

Multiple tracks selected (10-30 for example, the more the worse it gets)
midi CC controls Adjust track send 1 volume (MIDI CC/OSC only)
Play or Stop doesn't matter

Send Volume is exceptionally slow to react to the midi cc input
(unlike ANY plugin parameters across several tracks, track volume, pan, send mutes)

This is actually an almost-dealbreaker., because "selected track" send volume changes via OSC does , not , work on selected tracks, unlike the midi cc. That OSC comand only works on one track.

Replicating

Download sample session (365kB)

Open session, bind a MIDI CC controller to the action Adjust track send 1 volume (MIDI CC/OSC only).

Select all SOURCE tracks. Switch to LATCH mode.

Run playback, turn the midi knob.

I've placed two markers in the session. The first marks the moment I twist my knob quickly four times. The second marks where I stopped turning the knob. The automation shows what Reaper actually did with the input.

I hope you can fix this. The slowdown is dramatic. Fun bonus is that Reaper accepts NO INPUT AT ALL while it's pondering what to do with the MIDI CC input.

[Justin]

Hmm odd, it works fine here (only negative thing I see is it adds one undo point per envelope that gets auto-added, which isn't ideal).

Maybe the undo point for every track is causing the slowdown for you?

[airon]

The envelopes are all already activated and armed. This could be an artifact of my system of course. I just hope not :P .

When I'm setting up basic reverb send levels for anything from 5 to 50 dialog tracks, I'll often use LATCH PREVIEW, since it doesn't write anything yet.

Same thing. Perhaps I need to send in my Reaper.ini too.

I've taken a screenshot of (almost) the same activity, the upper track shows what happens when I have all the SOURCE tracks selected, the second when I have one track selected. It's all in LATCH mode.



My undo memory is set to 3072 MB, but setting that to 1024 did nothing differently

Here are Licecap recordings demonstrating the problem at up to 15fps.

Endless knob CC (Relative 2 mode) controlling send 1 on selected tracks(5.3MB) I trace the movement of the knob with the mouse cursor to illustrate the delay in reaction.


Absolute mode knob CC controlling send 1 on selected tracks. (2 MB)
This second one might be more revealing, due to how fast you can go from minimum to maximum values with a standard midi knob.

Hope that helps.

[airon]

To compare, I did a test using the same gear controlling the frequency of an EQ band.

FX track, one send from the source track, instantiated a ReaEQ instance on the source track, bound the low and hipass frequencies to one endless and one absolute knob, had those two frequency parameters show up as parameter knobs on the mixer(and TCP if I'd expanded the track heights), duplicated the track to an alltogether count of 10.

The tracks were all selected, switched to Preview. Transport in stop mode.

The ReaEQ parameters were fine. One frequency ran on an endless knob, one on an absolute knob. Pretty quick, all good in both GUI and response.

The send volume has that lead ball tied to its ankle.

Licecap of the whole thing, including the session

[airon]

One additional note.

I tried this in Read/Trim mode, with the send NOT being activated and armed.

That responded just fine.

[azslow3]

My slow computer indicates that something strange is going on behind the scene with many armed automations (as in your project).

"Usual" mapping (with MIDI->control path):
* track volume is more or less responsive
* send volume is "jumpy", with several seconds delay when goes from min to max

With my "stop MIDI leaks" csurf (independent MIDI->VKb control path), the result is horrible:
* track volume is "jumpy", with several seconds delay
* send volume is smooth (???), but it take like 1 minute (!) to go from min to max

Also in both cases track routing dialog parameter labels are annoying blinking all the time. Only "dB" for master track volume, "Send to track 32 FX", and a bit "Pan:". All other labels are steady...

I repeat, I have 10 years old CoreDuo. But for operations I normally use the response is instant, f.e. I can play SoftSynthes throw "stop MIDI leaks" csurf without any noticeable delay.

I have checked system CPU consumption with automations armed: ~1% in idle, ~7% with transport play. That does not looks like a bottleneck for me.
So something is a kind of "looping" inside Reaper, flickering a part of GUI and blocking/slowing control MIDI processing.

[Justin]

Try 5.81pre2?

[airon]

Will do.

My specs just in case: i7 6700k, Win7x64, Reaper x64, GTX1070, 32GB RAM.

[airon]

Just gave 581pre3 a quick test.

It's running well now. I tried it on one of the larger dialogue sessions (42 fully automated tracks of over 100 parameters each) and the send volume levels are running with very low lag(100s of ms or so) now, which works great for me.

If nothing shows its ugly head, this is fixed for me.

Thank you for fixing this.

azslow3 , how about you ?

Sidenote: the OSC command from my Reaper.osc config TRACK_SEND_VOLUME n/track/send/@/volume
should controll all selected tracks, just like a midi CC or OSC command bound to send x volume actions are. But it does not, yet.

[Justin]

Originally Posted by airon

Just gave 581pre3 a quick test.

It's running well now. I tried it on one of the larger dialogue sessions (42 fully automated tracks of over 100 parameters each) and the send volume levels are running with very low lag(100s of ms or so) now, which works great for me.

If nothing shows its ugly head, this is fixed for me.

Thank you for fixing this.

azslow3 , how about you ?

Sidenote: the OSC command from my Reaper.osc config TRACK_SEND_VOLUME n/track/send/@/volume
should controll all selected tracks, just like a midi CC or OSC command bound to send x volume actions are. But it does not, yet.

Those OSC actions aren't for selected tracks, but for the last-touched track.

[azslow3]

I have done some tests.

Reaper 5.81pre3, undo set to 0 (disabled), just one track selected:
* MIDI direct Volume - instant smooth
* MIDI direct Send Volume - +3 sec slope, smooth
* MIDI -> VKB Volume - instant jaggy
* MIDI -> VKB Send Volume - +3 sec slope, smooth

So, not 1 min, but still not what I expect.
Interface is still flickering (sometimes main menu).

Just to check MIDI -> VKB timing:
* MIDI -> VKB CC MIDI recording (so the same schema as for control, but sends as normal MIDI) - instant smooth

For general performance check, the same controller, Sonar MIDI remote / my plug-in: all automations instant.

[airon]

Originally Posted by Justin

Those OSC actions aren't for selected tracks, but for the last-touched track.

Thanks for clarifying.

That means I have bind to custom OSC commands to the actions then. But I can't actually do that, because I'd lose all feedback.

I suppose a feature request is in order, together with support for send mutes in the OSC config, so I can tell at a glance what sends are unmuted when I operate the level controls of the Lemur application on the iPad.

-edit-
To my surprise I had already posted this feature request two months ago.It's as good a location to point at it as any I guess.
https://forum.cockos.com/showthread.php?t=203630


Sidenote, I operate sends to effect tracks with send mutes, because it's the quickest way so far. Always saving time .