I have SPL Crimson 1 sound interface and I am experiencing too much RT CPU usage, over 100% and the project isn't that heavy.
The normal CPU is like 5% and the RT is over 100%
I have tried to put maximum latency in Asio settings of the interface, like 4096 and all but I still have nasty playback with audio dropouts spikes and clicks etc
I think lately is worse, I only put few plugins, and the CPU usage summing of plugins
is very low as well but the RT usage is over 100%
What could I do here? I am not experiencing so much usage in FL Studio for example.
Location: Near Cambridge UK and Near Questembert, France
Posts: 22,754
FL doesn't use ASIO as far as I remember. Try downloading resplendence.com's latency checker & see what it says about your computer with Reaper running.
You might also want to try going back down to something like 512 or even 256 ASIO buffer and see what happens.
You haven't mentioned your computer specs but having an internet browser open can definitely affect CPU usage and, as I recall, that Diva plug is pretty CPU hungry.
FL doesn't use ASIO as far as I remember. Try downloading resplendence.com's latency checker & see what it says about your computer with Reaper running.
You might also want to try going back down to something like 512 or even 256 ASIO buffer and see what happens.
Hi Ivan,
Yes they do, and indeed they recommend it. I remember reading this a few years ago when I was checking if my X-Fi internal card was good enough for DAW work and it turned out to be a recommended card: https://www.image-line.com/support/f...s_asio4all.htm
Its better at 1024 or 512, but with 2048 and 4096, instead of better playback it creates pops and clicks.
Lately Reaper seems to have high RT CPU usage than it used to be.
I used to put millions of plugins without problem, what could be the case here?
Sometimes I put U-He Diva and with 1 instance the RT Cpu is on 100%
I don't know what to do.
Maybe it is OK? And I just use heavy plugins?
The driver for the connected audio interface can have a max value (often 1024 samples) where if you increase the block size more it creates more CPU work than it saves.
One thing you can try with the suspect plugin is disabling anticipative fx processing on just the track it's inserted on. (Right-click the track panel and select disable AfxP from track processing menu.) Disable per track for plugins that don't support it. Do not disable AfxP globally in preferences!
Quote:
Originally Posted by SBK
Noticed that google chrome has big impact on the pops and clicks on playback
Is your system output (for media player, internet browser, etc audio) set to the same sample rate as your Reaper project? If not you will have conflicts and a clicking and popping mess is pretty expected. This is why you usually get the quicker comment of "Don't have any other audio using apps like an internet browser running at the same time as your audio project."
Location: Near Cambridge UK and Near Questembert, France
Posts: 22,754
SBK: Obvious answer is don't use google chrome when you are recording!
And it might be interesting to see how your performance is with even lower buffer settings than 512.
I run a 32 or a 64 buffer all the time - even when mixing I seldom run more than 126.
And that is on a 4th generation i7 quad running Win10 64bit.
At least if you have all green lights (surprised you aren't even seeing any reds on page faults!) you dont have to worry about trouble shooting your actual computer.
As has already been noted, Diva IS a bit of a cpu hog so it would probably be a good idea to freeze and unfreeze when using that particular plugin.
P.S. Softsyth - never been interested in trying Fruity Loops out but several on here have praised it before. Might have to see if there is a demo version.
The 'set it and forget it' block size of 1024 samples for mixing will ensure you always have max headroom. Also it might be a PITA to be switching between different recording offset values for different block sizes if you were having to up the value for some projects. (The offset you set based on block size, sample rate, and the interface base latency to make overdubbed audio align to the project.) An 'auto' setting may work well enough for this to be sight unseen in some scenarios, but when it doesn't... (What the? Why is my overdub all of a sudden out of time?!)
That's why I leave mine set to 1024 samples for studio work anyway. YMMV.
Also it might be a PITA to be switching between different recording offset values for different block sizes if you were having to up the value for some projects.
I don't remember my loopback test showing a need for different record/playback offsets with the changing of buffer size. Sample rate changes however, yes.
__________________ Music is what feelings sound like.
What would hav been interesting is the Processes tab.
And yes, close ALL the other programs when you are recording. Only Reaper must be running. Especially, Web browsers are known to use up whole CPUs.
P.S. Softsyth - never been interested in trying Fruity Loops out but several on here have praised it before. Might have to see if there is a demo version.
Coincidence. I had looked for general purpose DAW advice from multiple sources, not specifically their software at all.
I had tried it briefly when I got into DAW music production. I didn't find it intuitive, unlike Reaper (for the most part).
Try downloading resplendence.com's latency checker & see what it says about your computer with Reaper running.
Mine keeps telling me to disable CPU throttling, which is already disabled. It also says to disable it in BIOS setup and Control Panel. You can disable CPU throttling in Control Panel?????
Location: Near Cambridge UK and Near Questembert, France
Posts: 22,754
Hard page faults in general are nothing much to worry about unless they impinge on whatever you are using in your audio chain.
In this case I would say you are fine with svchost errors.
Jeff Control panel allows you to alter your power profile since about win7 or maybe even earlier.
Dont confuse specific comments about cpu throttling as being the only place to look. I just nipped out into Win10 settings control panel and in the advanced power settings once you have set everything to run flat out and nver switch off, there are several options covering cpu drives etc. Max them all.
What it is suggesting is that you ALSO go into your bios and turn off any CPU throttling set there as well.
I am a bit rusty on this stuff' since you generally only have to do it once and my computers are both well over 7 years old!
But its worth holding down the appropriate key or key combination when you system starts and having a look at what is going on in the current bios setup. You won't need to do anything scary like re-flashing it, just change settings which are in any case re-settable on the next reboot if you do cock something up..
I will do so tomorrow AM and let you know what MY computer bios contains.
What are the system specs, and what's your definition of a project that "isn't that heavy".
Could it be that whatever you are running just uses more cpu power than you have? Unless it is the fault of a very problematic ASIO driver chewing all your CPU power, something in your project is using enough CPU to put your RT usage over 100%.
Getting fx off the master track can have a very big effect on the RT cpu useage.
Try putting a dummy track as Track 1 (call it Pre master) - make it a folder track, and make your last real track the end of the folder (or like a programmer, stick another dummy track at the end of all your live audio tracks, and make that the last track in the folder - a bit like bracketing your audio tracks).
Move all your master fx onto the new pre-master track (the parent folder).
By using a folder solution you don't have to worry too much about the routing as all children of course go to the parent - and the parent just sends to the real MASTER track.
Worth a go. I've seen even a simple 4.5% RT on my BIG beast of an audio box go down to 0.1% simply by doing this trick.
Hi SBK,
Maybe there is real time Sample Conversion going on? Did you check if there is a sample rate mismatch in your project?
Yeah, definitely check that.
Reapers resampling system is brilliant, but it can also prevent you from noticing that your sample rate is not optimal for the audio you are processing bceause it just works with whatever sample rate material you throw at it. Reaper will use CPU power to resample on the fly any source audio that is at a different sample rate to what your project is running at.