Score

resources(...) --- How Hard the Machine Is Working

resources() puts a tiny line of numbers in a corner of the screen, to see the machine filling up before it shows in the sound: when the audio starts dropping out, it is already too late.

Syntax

resources() resources(at:tl) resources(stop)

Run it again to hide it.

Parameters

param required description
at ✖ The corner: br (default), bl, tr, tl.
stop ✖ Hide it (resources(stop)).

What it shows

cpu The machine's processors, all of them, and in brackets the busiest one. Sound is worked on one core: that one maxes out long before the total looks high.
mem The machine's memory in use.
fps How many times a second the page draws. Low: the animation stutters.
audio ok, or late: the sound's clock falling behind real time -- it is dropping out.
voices The sounds running: every synth and audio voice.
paused Sounds let go with gate(s, 0): silent, but still running. Shown only when there are any.
heap The page's own memory (in Chrome and the app).
stalls Moments the page froze for more than 50 ms in the last second, when there were any.

Each turns amber, then red, as it nears its limit. cpu and mem come from the Oscilla server, which runs on the same machine; a performer's phone or another laptop shows the server machine's. The HUD is not shown on the projector window, and it does not catch the pointer.

See also

Tip: use ← → or ↑ ↓ to navigate the docs