CPU headroom: a practical priority stack

Treat CPU like a finite pool. Allocate it to elements that define the record · vocals, lead synths, unique textures · and convert everything else to audio once you are no longer iterating. Sends and reverbs should be shared, not duplicated per channel.

Oversampling is powerful and heavy on the CPU. Use it where artifacts are audible, not everywhere by default. If you are mastering inside the same session, consider a dedicated mastering project to keep production playful and the final stage controlled.

PDC (plugin delay compensation) keeps timing honest but can hide which insert suddenly doubled your latency stack. When a project “gets heavy” after one new plugin, check whether that plugin introduced lookahead or heavy oversampling on a hot path; moving it to a frozen stem or a parallel send often buys back the headroom you were about to pay for with a bigger buffer.

• Freeze tails-complete: bounce a bar past the last audible note so reverb and delay do not chop.
• One convolution reverb on a send beats four instances with slightly different rooms.
• Before buying a new machine, profile a single drop where all vocals are frozen · vocals plus pitch/tune stacks are usual suspects.
• Offline stem renders on a thermal laptop often succeed where live playback fails · use them to finish tonight’s idea, then optimize tomorrow.

Multiple heavy instruments on the same core-heavy thread tell the same story: the mixer meter looks fine while the playhead jitters. Spread the damage · freeze completed stacks, delete silenced MIDI lanes, and question whether that fifth open-editor tab was ever earning its keep.

Duplicate the project file before a “freeze everything” night: aggressive rendering feels brave until the hook synth needed one more filter sweep. Keep a `_working` and `_frozen` sibling in the same parent folder · courage and regret insurance cost one extra save.

Muted tracks with editors left open still cost GUI and sometimes DSP · hide what you are not auditioning. Automation hunting CPU spikes often finds one lonesome LFO sync’d to the wrong PPQ, not a “bad” synth.

RAM pressure masquerades as audio glitches: streaming huge sample libraries from a nearly full system drive thrashes both disk and page file. Free twenty gigabytes, move bulk packs to a fast secondary disk, or consolidate RAM-heavy instruments before you blame the DAW version.

Some vendors still ship “single-core” wrappers around old binaries · one charismatic synth can peg a thread while Task Manager pretends the machine is bored. Freeze that hero first; CPU graphs lie politely too.

Split “performance mode” mentally: live playback for feel, offline render for proof. Auditioning ideas at 64-sample buffers while refusing to freeze anything is a personality conflict your laptop did not sign up for.