In any case, perhaps the following experiences might be of use. The primary grunt issue here being 4k video production. This is also in light of the fact that I’ve worked with mac os systems for many years, but now on a windows workstation because of the horsepower that is not available on Apple systems. Maybe it’s the processes being maxed out.ĭoes doing the “audioengine.properties workaround” mean that the processes in cubase are no longer limited and the bridge workaround is no longer required?įWIW, I have been through all of these mods and troubleshooting in search of better performance, less drop-outs etc on Windows 10. Projects slow down even if my CPU is still only around 50-60%. I get a spike in the hard drive performance meter when I stop playback and the mouse turns into an hourglass for 2-10 seconds. But like before the workaround, I still locked up in larger projects. I did the “audioengine.properties workaround” and initially it seemed to help things run smoother (projects would seem to load more quickly). Is that the same issue that’s being discussed in this thread? As a workaround, I’ve been using JBridge to bridge 64 bit plugins onto processes outside of Cubase. I’ve been aware of the issue with Windows 10 where it limits the number of processes that any single application can run. I have hyper-threading turned off on my machine in the Bios, and am overclocking from 3.0 to 4.2 on each core. I’m on a 圆950 (10 cores, 20 threads) with Windows 10, Cubase 9.0.30, 32 GB of RAM, and a UA Apollo Interface. I am doing my best to understand all the info in this thread. I know patches can be ugly, but can they also have bugs? Hmmm. PS, the Omnisphere patch glitching is almost identical in the free version of Ableton. Running other software also slightly raises the Cubase cores, but only about 10% each.Īnd the mix sounds better without that stupid patch! It hitch hiked in starting with a first approximation and was forgotten. Will I get problems from localized CPU heating? I dunno. The only downside I can see is that the two cores not available to Cubase (1 hardware core and 1 hyperthreaded core) get hammered hard when other programs are running. And that’s on a 5+ year old, generation one i7 that is probably 1/3 the speed of current models. I don’t know how useful that reduction will be in the long run, but I am now running this browser, Photoshop, my weekly backup, and few other things on 1/4 of my cores, while my lovely project loops along with zero glitches no matter what I do. I also limited my quad core CPU to 3 hardware cores (or 6 cores counting the hyperthreads), and that reduced the patch glitching by a lot, but it was still there. I just checked about a hundred Omnisphere patches, nothing else raises the cpu more than a few percent. Adding a single “Light As Air” patch brings in glitches, even if it’s the ONLY patch. I have a project with 7 Omnisphere patches and 10 EW Hollywood patches that runs fine at 30% CPU usage. I discovered the source of my glitching problem was a particular Omnisphere patch!Ī project with a single track of “Light As Air” will put my CPU speed up to max and the CPU usage to 100%, with glitches every 10 seconds. This article provides an overview of the CPUSets API new to the Universal Windows Platform (UWP), and covers the core information pertinent to game and application development. Cubase should use the new method “CPU Sets” for several processors under Windows 10.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |