Hey guys. This phenom is not new but ran across it again recently. I am using Reaper 7.19 Win 10 on a I5 dual core laptop.
The culprits in the past and still are Waves Codex and Elements. Now the latest....Primo amp sim.
Is there a setting somewhere that can eliminate this?
Gui off....2-3% open gui 20-30%
Cpu incrases 10x with vst gui open
-
Scrubbing Monkeys Scrubbing Monkeys https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=397259
- KVRAF
- 1837 posts since 21 Apr, 2017 from Bahia, Brazil
We jumped the fence because it was a fence not be cause the grass was greener.
https://scrubbingmonkeys.bandcamp.com/
https://sites.google.com/view/scrubbing-monkeys
https://scrubbingmonkeys.bandcamp.com/
https://sites.google.com/view/scrubbing-monkeys
- KVRian
- 991 posts since 24 May, 2024
I don't know how to affect VSTi CPU use, but I do know that the more Reaper meters there are, the more CPU use.
So I turn off all the meters except for simple channel LEDs. And I don't need all of the all the time.
Most of the time I'm in arrange mode instead of mix mode. Also I turn off some meters for the master stereo track. It actually helps me on my Linux system to do this. I ran some tests also. A few other things that I do:
* freeze to audio ASAP (audio seems to use less CPU than VSTi MIDI)
* turn off internet while working
* even set monitor to 40 Hz instead of 60 Hz (not sure if it helps or not)
* avoid VSTi's with 96 kHz audio samples
I hope this is helpful.
So I turn off all the meters except for simple channel LEDs. And I don't need all of the all the time.
Most of the time I'm in arrange mode instead of mix mode. Also I turn off some meters for the master stereo track. It actually helps me on my Linux system to do this. I ran some tests also. A few other things that I do:
* freeze to audio ASAP (audio seems to use less CPU than VSTi MIDI)
* turn off internet while working
* even set monitor to 40 Hz instead of 60 Hz (not sure if it helps or not)
* avoid VSTi's with 96 kHz audio samples
I hope this is helpful.
-
Scrubbing Monkeys Scrubbing Monkeys https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=397259
- KVRAF
- Topic Starter
- 1837 posts since 21 Apr, 2017 from Bahia, Brazil
Yeah this only hapens when opening the gui of the plugin......and only in Reaper
We jumped the fence because it was a fence not be cause the grass was greener.
https://scrubbingmonkeys.bandcamp.com/
https://sites.google.com/view/scrubbing-monkeys
https://scrubbingmonkeys.bandcamp.com/
https://sites.google.com/view/scrubbing-monkeys
-
- KVRAF
- 7094 posts since 22 Jan, 2005 from Sweden
Have a look at various settings for threads, plugins and stuff in Reaper, don't remember all what they were called.
- run plugin in separate thread/process or similar
- anticipative thread allocations or various things, whatever name was
If it is particular plugins there might be a cure like that.
Just try some of these kind of settings.
- trial and error
I ran Reaper last a bit at v4.7 which is a long time ago, so might be even more to pick from these days.
- maybe target individual plugins too
- run plugin in separate thread/process or similar
- anticipative thread allocations or various things, whatever name was
If it is particular plugins there might be a cure like that.
Just try some of these kind of settings.
- trial and error
I ran Reaper last a bit at v4.7 which is a long time ago, so might be even more to pick from these days.
- maybe target individual plugins too