Quote:
Originally Posted by JamesPeters
I just realized you're right. Although it doesn't seem to take much CPU displaying video.
|
playing back video is fine, even on my core2 quad dinosaur of a machine. doing any sort of heavier manipulation in real time will be very choppy and generally just crash my system if I get real aggro with adjusting most any parameter. Playing back with automation is fine. (i suppose this is due to buffering)
I can crash my system at will by loading up the "blitter feedback" and making repeated fast moves with the rotation parameter in real time, for example. Monitoring CPU usage, GPU usage, and memory usages while doing this shows a good increase in cpu usage only, but I'm still not pegging the cores here. Interesting.
I am overclocked quite a bit, as the Q9650 loves to take a beating, so I'm not that surprised I can bring everything to it's knees.
I have a sense, however, that what I'm attempting here isn't likely all that much better with some top of the line processor. In real time, without utilizing the GPU at all, sweeping the parameter knobs on some of these presets is probably quite choppy on even the beefiest of systems (surprise me here, and someone tell me that they have no problems with this)
Now, I'm NOT saying that REAPER needs to be super optimized for this, It's a DAW, not a video editor, but the fact that it seems to use 0% of the GPU for it's video effects is a bit unfortunate.