Cubase 7 CPU maxed out but activity monitor only shows 20% usage...help?
-
- KVRAF
- 2725 posts since 19 Dec, 2010 from North America
Just to be sure, download ASIO4ALL, and use your motherboard soundcard if possible and set up cubase to run from ASIO4ALL instead of your current audio interface.dtm7272 wrote:Ok thanks for the info
In Asio4All, set the buffer to 2048
That way we'll know for sure
**oh wait... maybe it's not for mac?**
One Synth Challenge: https://sites.google.com/site/kvrosc/about
- KVRAF
- 12615 posts since 7 Dec, 2004
bjporter wrote:Each plugin or part of software in a chain requires a certain amount of ms to do an effect or DSP... if it takes too much your buffer won't handle it
Actually, you need to look at it in terms of generating any number of samples.
The software needs to execute a certain number of instructions to generate the output. Regardless of which software you have, in a chain, whatever, if the total time it takes to execute the instructions is greater than the length of one sample, you can't generate the sample fast enough to fill any size buffer regardless of length.
You'll always end up having the sound card needing the buffer before it is filled up, and that means you'll get silence or repeats of the old buffer until the new one is ready, depending upon how the hardware is configured.
I'm loving how this is suddenly oh so "weird" to people these days. Does this never happen? This never doesn't happen for me, I'm always dialing things back a notch no matter what I'm doing and keeping track of exactly how much process cost applies to what I'm working on.
To get anywhere near the stuff I can do with my analog gear in software is unthinkable. Today's CPUs are still absolutely children's toys.
Free plug-ins for Windows, MacOS and Linux. Xhip Synthesizer v8.0 and Xhip Effects Bundle v6.7.
The coder's credo: We believe our work is neither clever nor difficult; it is done because we thought it would be easy.
Work less; get more done.
The coder's credo: We believe our work is neither clever nor difficult; it is done because we thought it would be easy.
Work less; get more done.
-
- KVRAF
- 2725 posts since 19 Dec, 2010 from North America
aciddose wrote:bjporter wrote:Each plugin or part of software in a chain requires a certain amount of ms to do an effect or DSP... if it takes too much your buffer won't handle it![]()
Actually, you need to look at it in terms of generating any number of samples.
The software needs to execute a certain number of instructions to generate the output. Regardless of which software you have, in a chain, whatever, if the total time it takes to execute the instructions is greater than the length of one sample, you can't generate the sample fast enough to fill any size buffer regardless of length.
You'll always end up having the sound card needing the buffer before it is filled up, and that means you'll get silence or repeats of the old buffer until the new one is ready, depending upon how the hardware is configured.
I'm loving how this is suddenly oh so "weird" to people these days. Does this never happen? This never doesn't happen for me, I'm always dialing things back a notch no matter what I'm doing and keeping track of exactly how much process cost applies to what I'm working on.
To get anywhere near the stuff I can do with my analog gear in software is unthinkable. Today's CPUs are still absolutely children's toys.
Thanks for explaining it to the laymen like me!
One Synth Challenge: https://sites.google.com/site/kvrosc/about