I think if you were running a dedicated DAW, you'd not be having these issues. With an off the shelf machine and especially one that's used for work, among other things, there's no telling what programs are loading and running in the background, all of which use processing power. I assume that you loaded the plugs to your machine and use the dongle to authorize their use. I did that test right after I built it and got it operational just to see what it could do. I have loaded this baby up with quite a few heavy load plugs and never was able to get it to choke.
I went from running 50% or more on the processor on my lappy to under 20% load when I built my new DAW box using the i5 chip and XP pro 32 with 4GB RAM. You will likely need to find a work around until you can get a machine capable of handling the heavier load. By selecting only the things I need, I lighten the load. but in Ozone, for example, if all I need and want in the EQ or the compressor, I can shut off the other modules and they don't require the same amount of processing power to run as the fully functional Ozone with all the modules on and set to default. I don't know how the Slate Digital plugs work. 99% of the time it goes into the master buss, and occasionally it ends up in a sub buss or two. With Ozone, I rarely put it into a track. However, I also like to run Ozone and Melodyne, both of which use considerably more processing power to function properly. I tend to use a lot of the default cakewalk plugs/FX such as compressors and EQ and reverb and other such things. where are you inserting these plugins? Are they going into tracks? How many instances are you trying to run at the same time? Have you considered putting the plugs into busses rather than tracks? Have you tried using a DAW other than Real Band to see how well it might handle the same situation? Having your music on a "work machine" probably isn't the best place to run it.įirst off. That's the specs for my current studio DAW and it runs lean and fast. The i5 chip in your machine should give you the speed and 4GB should let it run nicely from RAM. My solution to that was to "FREEZE" the track(s) and it would temporarily process the plug into audio. I could load a few instances of some of my heavier plugs and watch the DAW bog down and the processor percentage go upwards of 60% or more. It is taking a age to open up the files and adding new plugins to individual tracks grinds the whole thing to a halt.I have a Dell Laptop i5 with 4 MB of ram which works quite well for the stock PG Music plugins. I am trying out the plugins from Slate Digital and am wondering if anybody has any tips for using processing power hungry plugins with Realband.