View Single Post
Old 01-25-2016, 08:38 PM   #2080
mrelwood
Human being with feelings
 
mrelwood's Avatar
 
Join Date: Nov 2006
Location: Finland
Posts: 1,528
Default

As an addicted user of the SWS Auto Color, I have managed to bring it down on it's knees...

IN SHORT:
Dragging several Auto Color rules takes too much CPU. Possible solution: recalculate track colors and save changes only after mouse button is released.

IN DETAIL:

At around 50 filtering rules and a project with 20 empty Auto-Colored tracks, even scrolling the SWS Auto Color window with a trackpad is veeery sticky. But trying to select and drag ten (new) rules for proper positioning, I first get nothing, then the beachball, then my computer's fans running at full blast, and then the selection is lost and the order of the new (plus a few adjacent and sometimes the few topmost) rows are found in somewhat random order.

(Relaunching Reaper and opening Auto Color window on an empty project fixes the sticky scrolling, but dragging the rows behaves the same.)

As the track colors in the Reaper project seem to be updated on a per row basis when moving a single row, I would guess that moving 10 rules at a time calculates each new rule condition (or saves the changes to the .ini) at each dragged pixel. If this is the case, I would think that calculating the colors at the release of the mouse button (or after one second) would solve the issue without drawbacks.
__________________
______Announcing__mrelwood plugins______
.. MacBook Pro 16" Late '19 .. Scarlett 6i6, Saffire Pro 24 DSP (+ADA8000) .. FCA610 .. EVE SC207 .. Focal: Shape 65, Alpha 65, CMS 40, Listen Pro ..
mrelwood is offline   Reply With Quote