Most advice for weak machines is folklore. The actual cost in a music session is concentrated in three places - voice count, effect stacking and disk streaming - and almost everywhere else is noise. Understand those three and a six-year-old laptop with four gigabytes of RAM will happily carry a full arrangement. Stress-test the synth below and see where your own ceiling is.
Each held note is one voice: two oscillators, a filter and an envelope. Play one note, then three, then hold as many as your fingers allow. If the sound stays clean at six, your machine has more headroom than you think - and you have just measured the single thing that actually determines whether a session runs, on any computer.
Optimising the wrong one is how people spend an evening and gain nothing.
Every held note is a full signal chain running in real time. Sixteen voices is sixteen times one voice, and long release times mean voices keep running after you let go. Shortening release and reducing polyphony is the biggest single win available on a weak machine.
Reverb is convolution, which is expensive. Delays hold buffers. Putting a reverb on every instrument instead of one shared send is the most common way to waste a slow computer, and it also sounds worse.
Big sample libraries move data continuously and are punishing on a spinning disk. Synthesis generates sound from maths instead, which is why a synth-led session runs comfortably where a sample-led one stutters.
Waveform displays and meters run on the graphics path, not the audio thread. Turning them off feels productive and changes almost nothing.
A four-minute arrangement costs the same per instant as a four-bar loop. Only what is sounding right now is being computed.
Twenty muted tracks are twenty tracks doing nothing. What matters is how many are producing sound simultaneously, which is a different number and usually a much smaller one.
Neither is free. They spend the machine differently.
| Resource | Installed DAW | Browser studio |
|---|---|---|
| Disk space | Several GB, more with libraries | None |
| Boot and scan time | Plugin scan on every launch | Page load |
| RAM at idle | Moderate to high | Browser overhead, then modest |
| Audio processing | Native code | Native code - same kind of cost |
| Background load | Updaters, licence services | None |
| Where it struggles | Large plugin chains, big libraries | Very high voice counts, many tabs |
| Offline | Works | Does not load |
| Cost of trying it | Download, install, uninstall | Open a tab |
Boring, and by far the largest single gain on a machine with four gigabytes of RAM. A browser with thirty tabs open is competing with itself for memory.
A two-second release means voices keep computing for two seconds after you let go. Cutting that to half a second can halve the number of simultaneous voices in a busy part.
Convolution reverb is the most expensive common effect. One send that several instruments feed costs a fraction of six separate instances, and it makes the mix sound more coherent as a bonus.
Generated sound costs CPU; streamed sound costs disk and RAM. On an old machine with a spinning disk, the second is much more likely to be your ceiling.
Laptops throttle aggressively on battery, and audio dropouts that appear halfway through a session are very often this and nothing else.
Render a busy synth part to audio and mute the instrument. This is how people made records on machines far weaker than yours, and it still works.
Synthesis rather than streaming, and modest voice counts by design.
The processing a synthesizer needs has not grown much in fifteen years - an oscillator, a filter and an envelope cost roughly what they always did, while processors got several times faster. What grew is everything around them: sample libraries measured in gigabytes, plugin suites that scan for a minute on launch, project templates that load forty instruments before you have played a note. A 2018 laptop can run a great deal of music software. It struggles with the accumulated weight of a modern installation, which is a different problem.
No installer, no disk footprint, no plugin scan, no background updater, no licence service. Audio processing itself runs in the browser's native audio code, so the cost of an oscillator or a filter is comparable to a desktop instrument doing the same job - the saving is in everything that is not audio. On a machine where disk space and boot time are the real constraints, that is most of the problem removed. The engineering detail is on the browser-based DAW page.
A browser has its own memory overhead, and if the machine is already at its limit from open tabs, adding a studio to them will not go well. Very high voice counts will find the ceiling faster than a native application would. And nothing loads without a connection. If the machine is weak and usually offline, an installed lightweight DAW is the better answer and several good ones cost nothing. The full set of trade-offs is on the make music anywhere hub.
Yes. Voice count, stacked effects and large sample libraries are what actually cost you - manage those three and a modest machine handles a full arrangement. Track count and project length cost far less than people assume.
For browser-based or lightweight production, yes, provided you close other applications and keep tab count low. Large sample libraries are where four gigabytes stops being enough.
Less disk, no plugin scan and no background services. Audio processing itself costs about the same, because it runs in native browser code either way. The browser does add its own memory overhead.
Usually two things: too many voices sounding at once, and the machine throttling on battery power. Plug it in and shorten your release times before changing anything else.
Synthesis. Generated sound costs CPU, which modern processors have plenty of; streamed samples cost disk and RAM, which old machines usually lack.
No. Audio work does not use one. Waveform displays and meters run on the graphics path and cost almost nothing on integrated hardware.
For everyone the installed DAW leaves out: locked-down laptops, Chromebooks, school labs and machines that were never going to run a 4 GB installer.
Producing with no installer, no admin rights and no licence file - what that actually takes.
Read it → GuideChromeOS runs no DAW installer. It runs a very good browser - which is the whole point.
Read it → GuideThirty machines, one URL, no per-seat licence and nothing for IT to deploy.
Read it →All 20+ apps, no disk space used and nothing installed. Seven days free with everything unlocked and no card required.
Already subscribed? Launch the Analog Synth →