Been thinking a 10 … Something that may not have been apparent to all… Around the time of C8.0.20, there seems to have been a change in the compiler used. I have a MacPro system with dual quad XEON CPUs and a MacBookPro with a core i5 CPU. Problem: real-time CPU reacts heavily to any kind of on-screen activity. Tap the CPU / Polyphony meter to toggle between two modes: CPU: Shows the total CPU consumption of the audio rendering process in real-time. I read somewhere that going above 14 cores with Cubase is a bad idea. If, on the other hand, you're maxing out ASIO usage (the meter in Cubase) then the dual-Xeon is also likely to be worse because it's built for CPU power, not the real-time performance you want in a DAW: once you add a second processor, you've added latency because of the overhead associated with coordinating RAM/disk/USB/whatever transfers. 1.0.2: - RMS: Integration time changed to 600ms - VU: Needle movement smoothed

All versions of Cubase share the same pristine sound quality and ease of use that make Cubase one of the world’s most popular recording and production solutions. HP Envy J130ea i7 4700MQ 12 GB DDR HD4600 Integrated GPU nVidia GeForce 740m 2 GB Windows 10 64-Bit Cubase 8.5 Pro 64-Bit NI Komplete Audio 6 USB Interface. As of Windows 10, the amount of real-time processing threads with Multimedia Class Scheduler Service (MMCSS) priority is limited to 32 per process - 4 of which are blocked by non-audio-threads already running. 1.0.3: - RTAS/AAX/VST3: GUI fully restored after project load - WaveLab VST3: resize crash fixed - 2 new themes: retro and deluxe. Basically I just decided on a CPU for a PC build and there's no point in buying anything unless Cubase is going to be rock solid. which cpu load you looking at ? Tried all render method such as offline full speed, offline 1x and online render, with both case of enabling or disabling the "allow anticipative FX processing", even tried to change the performance options on individual track, the problem still occurs.

sx2.2 on a xp2200 + 1gig ram here and task manager says 99% usage when nothing happening, but loads of available horsepower - At the same time, cubase's performance meter shows 3-4 % usage, if you see what i mean ... [can happily run upto 50 audio tracks + plenty vst]. Just wondering about CPUs and Cubase. Cubase 10 is automatically adapting the amount of real-time threads to the system. Compare the versions of Cubase. 1.0.4: - RTAS fix. Empty project, drag a selection rectangle, real-time meter …

- VU ballistics changed to ideal VU Meter - CPU load reduced - Instance label 1.0.5: - VST3 resize fix - VST2 resize fix. CPU / Polyphony meter. When rendering a track with multiple vst, the midi note either having drop out issue, or not playing on time in render. If rendering takes longer than the buffer duration (which is determined by the latency in the setup), audible glitches occur.