Quote:
When rendering new tracks or takes, or when encoding into a new format, when I could be taking advantage of my processor, it pegs at 25%.
|
Ususally that means your CPU is NOT the bottleneck. ...Your hard drive or databus is probably holding things up.
Most likely it's your hard drive. The hard drive interface has a "speed limit" and if the read/write head is jumping back-and-forth between reading your source file(s) and writing your output files, there is an additonal "seek time" delay.
Sometimes you can almost cut the rendering time in half by reading from one drive and writing to another. Same thing if you copy a file... Copying to the same drive usually takes almost twice as long as copying to a different drive.
Think about what happens when you simply make a copy of a large file... It takes almost zero CPU power, but of course it still takes some time, and a faster CPU (or a more CPU cores) wont' make it go any faster.
Quote:
This wouldn't be a huge issue, except that this occasionally causes stability issues and "frozen" windows only for reaper.
|
That's probably not related to CPU usage.
I always suspect a plug-in or a 3rd-party CODEC, because REAPER itself is pretty solid. But that's just a
guess, and you never really know what a computer problem is/was until is't solved.