Old 08-07-2011, 09:42 AM   #1
typewriter
Human being with feelings
 
Join Date: Jun 2007
Posts: 528
Default CPU use & visible outputs

I realized that Reaper's CPU use rises significantly with the number of in the GUI visible VSTi outputs even when nothing is happening on most of the channels.

I first thought the cause is the sheer number of connected outs but meanwhile I think it depends on the number of visible channels in TCP and Mixer.

In some projects switching of the mixer decreases the cpu load up to 16%.

Not sure if this is a OSX only problem but I am wondering if sonething can be done about that. I am using the actual prerelease on leopard.
typewriter is offline   Reply With Quote
Old 08-07-2011, 09:58 AM   #2
piperboy
Human being with feelings
 
piperboy's Avatar
 
Join Date: Mar 2010
Posts: 59
Default

I get that on windows as well.
piperboy is offline   Reply With Quote
Old 08-07-2011, 11:30 AM   #3
musicbynumbers
Human being with feelings
 
musicbynumbers's Avatar
 
Join Date: Jun 2009
Location: South, UK
Posts: 14,219
Default

Could be certain graphics cards or just meters take up a lot of cpu, you can lower their refresh rate in prefs.
musicbynumbers is offline   Reply With Quote
Old 08-07-2011, 12:47 PM   #4
typewriter
Human being with feelings
 
Join Date: Jun 2007
Posts: 528
Default

Quote:
Originally Posted by musicbynumbers View Post
Could be certain graphics cards or just meters take up a lot of cpu, you can lower their refresh rate in prefs.
Can't be the meters. This happens even if you do not hit play and no meters are moving.

If I fold several channels in the mixer to one single visible channel (Reaper is not playing anything at all) I have an clear reduction of CPU use in Reaper.
typewriter is offline   Reply With Quote
Old 08-07-2011, 12:55 PM   #5
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 15,823
Default

It probably is the meters. Even if the project is processing silence, REAPER needs to look at every sample that passes to know whether to show anything on the track meter.

(REAPER's meter calculation/drawing is highly optimized, but any time you need to look at every sample, it costs something. In a heavy benchmark/profiling project with several hundred tracks, the meters typically account for about 1/8 of the total CPU cost.)

If you are near the limit on CPU, hiding tracks in the TCP and mixer should get you some CPU back.
schwa is offline   Reply With Quote
Old 08-07-2011, 01:06 PM   #6
typewriter
Human being with feelings
 
Join Date: Jun 2007
Posts: 528
Default

I see. Thanks Schwa!
typewriter is offline   Reply With Quote
Old 08-07-2011, 03:07 PM   #7
Mercado_Negro
Moderator
 
Mercado_Negro's Avatar
 
Join Date: Aug 2007
Location: Caracas, Venezuela
Posts: 8,687
Default

Quote:
Originally Posted by schwa View Post
If you are near the limit on CPU, hiding tracks in the TCP and mixer should get you some CPU back.
Interesting. I've mixed 80+ tracks projects where 50% or more of them are hidden and REAPER is not that fast when it comes to drawing elements. Only by moving these hidden tracks out of the project I can go back to Speedy REAPER Gonzalez.
__________________
Pressure is what turns coal into diamonds - Michael a.k.a. Runaway
Mercado_Negro is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 01:58 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.