Old "issue" : Reaper just isn't optimized for a huge amount of empty tracks. Pretty high CPU use here too with 2000 empty tracks when the transport is running. The process is using about 70% of a 6 core Intel i7 machine, Windows 7 64 bit, measured with Process Explorer. When the transport is stopped, the whole process CPU use is about 2%. Scrolling and selecting the tracks isn't hugely laggy, but it's definitely noticeable.
If you get the huge CPU use even when the transport is stopped, maybe check if you have some control surface or other extension plugin or ReaScript running that is somehow scanning the tracks all the time.
__________________
I am no longer part of the REAPER community. Please don't contact me with any REAPER-related issues.
Last edited by Xenakios; 05-10-2019 at 11:29 AM.
|