Go Back   Cockos Incorporated Forums > Projects > Deprecated REAPER issue tracker > Closed Issue

Extreme high CPU usage during automation Issue Tools
issueid=983 08-18-2009 03:12 PM
Human being with feelings
Extreme high CPU usage during automation

Why does envelope writing uses so much CPU?

-> empty project
-> add one track
-> set automation mode to "Touch"

-> play
-> tweak the volume fader (in the TCP!) of the track fast (maybe even via CTRL+Drag - fine tune)

=> Fader response is extremely slow and CPU usage extremely high (watch the Taskmanager):

http://www.outburst-audio.com/maik/a...-cpu-usage.png


This is without any media and without any FX! Tweaking the Fader in the Mixer (instead of the TCP) gives much better (smooth) display! CPU usage still is extremely high.


Conclusion:

1. Make TCP faders and Mixer faders work synchronous (same display update rate)

sluggish TCP faders vs. the non-sluggish MCP faders


2. Make automation more (much more) CPU friendly


System:
- Intel Core2 Duo E6700
- RME HDSP 9632 at 48000Hz, 256 Samples Buffer
Issue Details
Issue Type Closed Issue
Project Deprecated REAPER issue tracker
Category Arcana
Status Fixed
Priority 2
Affected Version 3.102
Closed Version (none)
Yes votes 4
No votes 1
Assigned Users (none)
Tags (none)

08-18-2009 06:26 PM
Super Moderator (no feelings)
 
Cannot reproduce. I'm getting some CPU load by the intensive knob twiddling (while writing as many automation points as possible to the track) but that happens also without writing automation, the automation itself doesn't seem to change the load.
Reply
08-18-2009 06:35 PM
Human being with feelings
 
The fader "hangs" don't occur during normal operation here. But tweaking the fader during automation causes "hangs" of the fader.


Btw: This only happens when tweaking the fader on the TCP. Tweaking it in the Mixer is much better (visual wise - CPU usage is still going nuts)!

Just imagine this on a large heavy loaded project ...
Reply
08-21-2009 03:31 AM
Human being with feelings
 
Quote:
Originally Posted by Steindork
Cannot reproduce. I'm getting some CPU load by the intensive knob twiddling
What do you mean with "some CPU load"?
Reply
08-21-2009 04:04 AM
Human being with feelings
 
I see similar here - but I reckon that is the graphics updates that cause the CPU load, not Reaper Automation specifically. Try opening an Explorer window on top of Reaper and moving that around quickly too - that gives a similar level of CPU load here.

Or dragging a track height up/down quickly.
Reply
08-21-2009 04:11 AM
Human being with feelings
 
Ok, but what about the sluggish TCP faders vs. the non-sluggish MCP faders?
Reply
08-21-2009 04:45 AM
Human being with feelings
 
TCP faders - not slugigsh here. I can move them as fast as the MCP faders - I do see a little "after image" but that may be my eyes.
Reply
08-21-2009 04:53 AM
Human being with feelings
 
yeah, i confirm it.
I was able to replicate the problem but i have no clue what could be the cause, anyway while doing it CPU usage of one of the cores goes up 20-80%
I can make a video to show it if needed.
Reply
08-21-2009 04:57 AM
Human being with feelings
 
Quote:
Originally Posted by DarkStar
TCP faders - not slugigsh here. I can move them as fast as the MCP faders
While recording automation? By default they are not sluggish. But in automation mode the TCP faders are sluggish here (extremely)!


Here similar slugghish behaviour described: http://forum.cockos.com/showthread.php?p=361425
Reply
08-21-2009 08:25 AM
Human being with feelings
 
Yep, clicked Play and jiggled the fader quickly (on the TCP, EnvCP and MCP).
Reply
05-03-2010 03:57 PM
Human being with feelings
 
This is related to the REAPER window size. 1920x1200 gives jumpy faders when automating them. Really not funny to work with. Reaizing REAPER to a small window (say 300x200) and the faders are smooth during automation writing.


Shall I throw away my 1920x1200 screen?
Reply
05-07-2010 04:46 AM
Human being with feelings
 
Still not happy with it in 3.52pre1! At 1920x1200 automating faders is still lagging.


I would say with REAPER window up to 1024x768 it's ok. Window sizes above causes slow fader movements (fader behind mouse movement when dragged fast).


With "faders" i means faders in the TCP. MCP movement is ok!


And that'S just with single track/envelope. Two envelopes -> even smaller window required for smooth fader movement (and so on) ...
Reply
07-29-2010 06:56 AM
Human being with feelings
 
Ok, more investigation in 3.66pre14 tells me that the REAPER's window size doesn't matter that much.



What really matters is this: The height of the envelope track(s) on the track to be automated.


Envelope track height = smallest => no sluggish TCP fader movement
Envelope track height = largest => sluggish TCP fader movement


It doesn't matter which envelope track height is maximized. Say I have the Panorama-envelope track maximized and I'm just writing Volume-envelope (which is minimzed) => sluggish TCP volume fader movement.


Btw: This is just with single empty track! No plugins used at all!
Reply
07-29-2010 07:26 AM
Human being with feelings
 
+1
Confirmed here (v3.651, on a 1280 x 1024 screen) with a tall envelope lane
Reply
07-29-2010 12:36 PM
Human being with feelings
 
i got sluggish fader movement in TCP, but automation is writting exactly as i moved the mouse
Reply
08-05-2010 08:27 PM
Administrator
 
This should be improved in 3.66.
Reply
08-05-2010 09:45 PM
Human being with feelings
 
Not really.


Quote:
What really matters is this: The height of the envelope track(s) on the track to be automated.


Envelope track height = smallest => no sluggish TCP fader movement
Envelope track height = largest => sluggish TCP fader movement


It doesn't matter which envelope track height is maximized. Say I have the Panorama-envelope track maximized and I'm just writing Volume-envelope (which is minimzed) => sluggish TCP volume fader movement.


Btw: This is just with single empty track! No plugins used at all!
Reply
Reply

Issue Tools
Subscribe to this issue

All times are GMT -7. The time now is 05:16 AM.


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