The Green average load is sitting in the 15% range for most and the Blue is barely on…like 5%. Project I was just working on has about 20 instruments loaded: Halion Symphonic, several (were very CPU intensive in the old days!) Stradivarius Violins and Gofriller Cello (Kontakt based) Halion 5 Mellotrons and a Grand Piano plus 20 or so audio tracks. Running mostly UAD Plugins (Quad Apollo at 65% load) and low latency. My audio is playing from an external Thunderbolt drive, Samples loaded on internal. I just installed C8 on a new iMac 3.2Ghz Quad with 16GB Ram. ![]() I know that over the years I used to get ‘out of memory’ related overloads and if I restarted Cubase and sometimes had to reboot the computer it would fix it. I just don’t want other people to get stuck thinking it’s their systems, tearing their hair out in frustration looking for false problems, which they’ll of course never find, but be blamed for still. I’ve grown stark in my posts about these things, and I do understand it can leave an acrid taste in ppls mouth. This is Cubase’s personality, that causes this problem that the OP describes - though not every single case, naturally. ![]() If this was the system condition or config, then the same exact problems would show up in other DAWs on the same system/installation. Don’t matter how much we chase imaginary mice around our own systems, it never fixes this - with or without official support. I used to believe it was true too.īut it doesn’t work. Did you optimize? Got the latest drivers for everything?”-policy. I’ve felt like a prisoner in this “ It’s gotta be something wrong with your system. So I wrote what I feel certain is the general cause for that, in Cubase. I saw he wrote “My Real time peak is going to max (red colour) about every 10 seconds”, without putting any considerable load on the computer. In most cases and with some trial and error, you’ll get to know your hardware and how it works, its pro’s and cons, and in the end it youwill probably get it fixed. Don’t do things if you are not sure on how to recover from it if you break something. I would try to find the driver that is causing the issue in OP’s system. It’s sad that this isn’t the case in your system. Luckily most users experience the same behaviour every time a project is loaded. It’s an open forum so every opinion is there for free, but in this case OP has been telling clearly what his issue is, and imho this is not what you are describing Seraglio. There are idiots like me who tries to do that and people have been trying to find this for over a decade and not found anything conclusive. Or, if you’re unlucky, it will not.ĭon’t waste your time trying to find some reasonable or technical explanation or fix for it. If not, you can make a new blank project, and import the data from the first project (MIDI data, Kontakt instruments/multis etc) and it might work like it should again. Sometimes, all you need to do is to restart Cubase, load the same exact project again, and the CPU load will be realistic again. Sometimes it locks the CPU to 100% load, although you just loaded one small instrument or plugin. But sometimes, what you do or load gets translated by Cubase to load the CPU much much more than it should. Most of the time the CPU meter shows fairly correct load - although wobbly. In the project I worked on today I had two instances of PLAY with silk/ra and an instance of kontakt with emotional piano. You just hope for the best and keep going and solve things as they come up, roll with the punches.īut I’m no where near using the computer to Max. Overall, there’s no consistency to be found. It can also depend on the combination of plugins in the chain. The same plug without a plugin chain, can work just fine. Next time you try the same thing, nothing may happen. In Cubase 5 you couldn’t go much above 60-65% load, the wobbling CPU load would then reach 100% too often and produce ear-piercing crackles and dropouts.Ī single plugin, at the end of a chain, can cause the CPU load to get stuck on 100%, at one time. Version 8 is the the most CPU-stable and CPU-efficient version of Cubase I’ve seen though. No other DAW does this - but Studio One (which is made by former Steinberg programmers). It’s rather unique to Steinberg’s software. ![]() You will see that the CPU meter in Cubase, and the water in the glass, moves quite similarly - kindof wavy, surging. Look at the CPU meter, while you stop Cubase. Play a bit of music with high CPU load in Cubase. Look at the surface level in the glass, wavering around. Move the glass back and forth in the air, and suddenly stop moving it. Take a glass, fill it to half with water. This is the CPU load character of Cubase, and it is wobbly, has been ever since SX1 - on both Mac and PC.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |