Hello! I’m trying to run Cubase on a Macbook pro 19 i9, and it gets very hot on the downside. I’m worried about my mac. Maybe there’s something I could change in settings?
Hi,
On macOS, Cubase performance mostly depends on low-latency audio settings, clean background system, and disk/sample layout. Here is a focused checklist you can apply step by step.
1. Core macOS tweaks
- Turn off or limit live backups during sessions: disable Time Machine automatic backups and pause cloud sync tools (iCloud Drive, Dropbox, OneDrive, Google Drive) while working, as they constantly touch the disk and can cause audio dropouts.
- Quit everything non‑essential: browsers with many tabs, mail, messaging apps, Adobe updaters, etc., so Cubase and your audio engine have maximum CPU headroom.
- Plug your MacBook in: on laptops, run on power with “Low Power Mode” disabled so macOS does not throttle CPU or GPU during heavy Cubase sessions.
- Use wired where possible: avoid heavy Wi‑Fi/Bluetooth traffic during tracking (Wi‑Fi file sync, Bluetooth headsets) which can cause DPC‑like spikes on macOS audio.
- Watch Activity Monitor: check for processes that randomly spike CPU (cloud sync, browser helpers, indexing) and quit or reconfigure them if they interfere during sessions.
2. Audio interface and Cubase device setup
- Connect your audio interface directly to the Mac, avoid daisy‑chaining through displays or cheap hubs.
- Choose realistic buffer sizes: track at 64–128 samples for live input if your machine allows it, then raise to 256–512 (or higher) for mixing and large templates to avoid CPU peaks.
- Match sample rates sensibly: if you do not need 96 kHz, stick to 44.1/48 kHz for lower CPU and disk load per plugin and track.
- Keep the interface’s driver and firmware current: many stability issues and crackles are resolved by driver updates rather than DAW tweaks.
3. Disk, RAM and samples
- Ensure plenty of fast internal storage free: Apple silicon systems heavily use fast SSD for swap; when free space drops very low (e.g., ~20 GB remaining) users report glitches and dropouts in Cubase exports.
- Use external NVMe or SSD for large libraries: put orchestral/sample libraries and big projects on fast external NVMe or SSD drives rather than slow USB HDDs.
- Get enough RAM for your workload: orchestral and film templates benefit from 32–64 GB or more so you are not constantly swapping sample content.
- Avoid running sessions off spinning disks: mechanical drives are much more prone to causing dropouts under high track counts and many streaming instruments.
Specificaly for Intel:
On Intel Macs the focus is: keep the CPU clocks up and make Cubase’s audio engine work in the most “predictable” way (buffers, ASIO‑Guard, multiprocessor, etc.). Here are Mac‑Intel‑specific points plus concrete Cubase settings you can try.
1. macOS considerations for Intel
- Expect steeper limits than Apple silicon: even 9th‑gen Intel i5/i7/i9s run Cubase fine, but you hit CPU headroom earlier with big VI or amp‑sim projects, so buffer and project strategy matters more.
- Keep the machine cool and plugged in: thermally stressed or laptop Intel CPUs will throttle; a cool, always‑plugged‑in Intel Mac runs Cubase sessions more consistently.
- Be realistic with project size: users with 2019 Intel iMacs report Cubase 14 is “almost unusable” when pushing very high track counts with many instruments and amp sims; freezing and rendering become mandatory on such hardware.
If you’re willing to tweak deeper: disabling aggressive energy‑saving features in macOS (where possible), using a clean boot for sessions, and keeping background apps minimal helps Intel more than M‑series because Intel wastes more time ramping clocks up and down.
2. Core Cubase audio system settings
Go to Studio → Studio Setup → VST Audio System and then into Advanced Options.
- Processing precision
- 32‑bit float is usually enough and lighter on Intel CPUs.
- 64‑bit float can increase CPU load and memory usage and is only really needed for extreme headroom or some mastering workflows.
- Activate Multi Processing
- Leave this enabled on any multi‑core Intel Mac; disabling is only for troubleshooting odd issues.
- ASIO‑Guard
- Keep ASIO‑Guard activated; it shifts non‑realtime work off the realtime thread and usually gives a more stable system.
- Try Medium first; if you use lots of heavy VI and offline‑friendly FX, High can help. If specific plugins misbehave, test Low or off and/or exclude them from ASIO‑Guard in the Plug‑in Manager.
- Audio buffer / latency
- For Intel, the buffer size matters a lot: use 64–128 samples for tracking only if the project is light, then 256–512 (or even 1024) for mixing or large templates.
- Combine higher buffers with ASIO‑Guard High for big mixes or orchestral stuff to avoid real‑time spikes.
3. Project‑level tactics that help Intel
- Sample rate
- Use 44.1 or 48 kHz unless you absolutely need higher; 96 kHz on Intel can cut your effective track/plug‑in count roughly in half in real projects.
- Freeze and render workflow
- On Intel Mac, track freezing is not optional for big projects. Freeze heavy VI tracks and amp‑sim chains you are not currently editing so the CPU only runs light audio playback.
- Render complex FX buses to audio if they combine multiple CPU‑hungry plugins (linear‑phase EQ, oversampling limiters, convolution reverbs) that cannot be frozen directly.
- Plug‑in placement & types
- Avoid super‑CPU‑hungry plugins on groups and FX buses, because those often end up on hot real‑time paths and cannot be frozen easily.
- Be aware of which plug‑ins are worst offenders: amp sims, oversampling limiters, certain vintage compressors, and heavy virtual instruments; consider lighter variants while arranging, then switch to the final ones for printing.
- Test with a vanilla project
- Users and testers recommend building a simple project using only Cubase stock plug‑ins at 256–512 samples to confirm the base performance on your Intel Mac.
- If that’s smooth but your real projects are not, the bottleneck is almost always specific plug‑ins or sample libraries, not Cubase or the Mac itself.
4. Troubleshooting Intel‑Mac performance issues in Cubase
- Identify problematic plug‑ins
- Bypass plug‑ins one by one or use Cubase’s performance meter to see which channel is spiking; Reddit and FB users report one rogue plug‑in (or a corrupted instance) often being the cause of severe lag.
- Version and compatibility checks
- Cubase 14 in particular has reports of being much heavier on some Intel Macs compared to Cubase 13, especially with high track counts; some users stick with 13 on older Intel hardware.
- Check that your audio interface drivers are up to date and officially tested on your macOS version; instability often comes from drivers rather than Cubase itself.