TOO MUCH CPU

[ChrisBlue]

If just opening Reaper makes the CPU reading on your computer jump from 3% to 40% without you even pressing play is there something wrong? PRESSING PLAY THEN LEADS TO 75,80% cpu AND CRACKLES, EVEN THOUGH NO INDIVIDUAL TRACK IS SHOWING MORE THAN 3.5% AND MOST ARE BETWEEN 0 AND 1%, Summing to <20% (sorry about capitals, caps lock was on)

[sonicowl]

Maybe your audio buffer is too low?

[ChrisBlue]

I've already tried different values it doesn't seem to be that.

[Meo-Ada Mespotine]

You need to give more uncapslocked information like:
Which Reaper version?
Which operating system?
Which audiohardware are you trying to use?

[lunker]

It would also be helpful if you told us your CPU specs.

If you're using an older single- or dual-core CPU, then you might just be running into CPU limitations. On the other hand, if you're using a recent 6+ multi-core Intel or Ryzen, it should handle what you're doing with no problem.

[TonE]

I recognized exact same thing, wrote about it before but somehow got not much reaction there. My guess is after version 6 or so, at some updates something was added which is causing this behaviour, but so far nobody could tell after which update and which feature is soo important eating around fourty percent cpu. My guess is something with 4k updates, not sure.

If I could know the exact Reaper version after which this problem started, I could use just the version one before that. This behaviour is from my point of view and my laptop a show stopper. And I do not want to buy a new laptop just Reaper got some new feature which I am not knowing and not using anyway, but eating constantly fourty percent cpu.

[nicholas]

Originally Posted by ChrisBlue

If just opening Reaper makes the CPU reading on your computer jump from 3% to 40% without you even pressing play is there something wrong? PRESSING PLAY THEN ...

This implies that you're not "just opening Reaper" but opening it with a project in situ? Otherwise, why would you then press play? I'm wondering if it might be something in that project.

Try opening Reaper without a project (Hold Shift while opening).

Does it still happen then?

[bigjoe]

Originally Posted by nicholas

This implies that you're not "just opening Reaper" but opening it with a project in situ? Otherwise, why would you then press play? I'm wondering if it might be something in that project.

Try opening Reaper without a project (Hold Shift while opening).

Does it still happen then?

It can be also something in Monitoring FX (which are global and not per-project)

[StrumminSteve]

maybe way off base here ...but I was curious if the option to allow projects to override device sample rate maybe involved? I was wondering why that would be preferred and notice I have it checked on my projects anyhow. Sorry if this is way off but am curious of both situations...thanks all . )

[ChrisBlue]

Thanks for replies. When I opened to an empty project the CPU was very low around 0.7%
I have an i5(6600) processor and it's worked ok for the last 3 years or so. I'm using Reaper 5.61 and hoping not to update as that's just asking for more computer hassle and there is nothing in the new versions I need. I'm using 16GB and 1TB storage. Using Windows 10

[domzy]

Time-stretch, pitch shift & resampled audio can all be CPU hogs - are you doing any of these things in your project?

I don't think you've mentioned what buffer size you are using & whether increasing it helped?

[TonE]

My Reaper version is always latest, 32 bit windows, used inside wine, inside linux. (For this scenario at least, I can use also the linux version directly but this would be another story then.)

My Settings, Device, Audio device settings, Buffers were: 8 X 1024 samples. using 30..40% cpu, on empty project, this was not the case in the past.

Now changed Buffers to: 16 x 1024 samples, and cpu went down to 8..9 %, which is a nice improvement. I will keep these settings then. (latency: 341 ms)
Input device: Pulseaudio
Output device: Pulseaudio
Sample format: 16 bit
Input channels: 2
Output: 2
Samplerate: 48000 Hz
Buffers: 16 x 1024 samples
(latency: 341 ms)
Audio thread: ASIO Default ...

CPU consumption on empty project: 8..9%

System info:
Ubuntu 18.04 bionic (x86-64)
Cinnamon Version: 3.6.7
Linux-Kernel: 4.15.0.101-generic
Processor: Intel Core i5-4200U CPU @ 1.6 GHz x 2
Graphics card: Intel Corporation Haswell-ULT Integrated Graphics Controller
(Laptop model is: Lenovo X240)

Project was totally empty:
0 tracks
0 fx in master

Thanks for the hint with the buffer size. But somehow I had same settings in the past, thus same buffer size but with less cpu. Anyway, it is as it is.

[TonE]

Is there any way to analyze which components inside of Reaper.exe is using how much cpu? Any recommended tools?

[nicholas]

Originally Posted by ChrisBlue

Thanks for replies. When I opened to an empty project the CPU was very low around 0.7%

It's possible there's a particular VST that's causing this problem.

Open the project.

Select all tracks. Run the action Set all FX off line for selected tracks
Select all media items. Run the action Set all take FX offline for selected media items.
Select the Master. Open FX chain. Select all FX listed in panel on left, press Ctrl Alt B to set these offline.

Now play. You should find CPU usage is very low.

Now bring FX back on line one by one, by selecting the FX in the track FX window and pressing Ctrl Alt B.

After each one comes back on line, play and see if anything significant happens to CPU.

When you find the one that's doing it, there's your problem.

[ChrisBlue]

But if each individual track is showing low CPU and the sum of those individual values is around 20% how can any of the plugins on the tracks be the problem ?