Toolbar Reference
Every toolbar control - device pill, buffer size, latency readout, device menu and app menu.
The toolbar carries live engine state on the left and commands on the right.
Full toolbar with a device open, showing the latency readout.
toolbar-connected Routling │ ⬤ Focusrite Scarlett 18i20 ⌄ │ 512 smp ⌄ │ 10.7 ms ······· ⋮With no device open#
Only the brand and a single Open Device button. Everything else appears once the engine is running.
Brand#
The Routling wordmark. Tinted when you are on a paid tier, neutral on Free. Not a button - Preferences has its own control on the right. On a narrow window the wordmark drops and only the logo remains.
Device pill#
Shows the open device with a pulsing dot - the engine is running on it. Click to open the device menu.
Device menu#
| Item | Does |
|---|---|
| Sample Rate | 44.1 kHz or 48 kHz, reopens the device |
| Stream Format | Float32 or Int32, reopens the device |
| ASIO Settings | Opens your driver's own control panel (ASIO devices only) |
| Change Device | Pick a different primary device |
| Close Device | Stop the engine |
The device menu expanded.
toolbar-device-menuBuffer size#
Samples per callback, on the bar beside the latency readout.
32, 48, 64, 96, 128, 192, 256, 384, 512, 768, 1024, 1536, 2048, 3072, 4096
Smaller = lower latency, higher CPU, more dropout risk. See Latency and Buffers.
Latency readout#
One number: total latency through the longest path your audio takes. With no FX Modules that is the device buffer alone; otherwise it includes the worst FX Module on the canvas.
Hover for the breakdown:
App menu (⋮)#
The app menu expanded, showing the Session and App groups.
toolbar-app-menu| Group | Item | Does |
|---|---|---|
| Session | New | Clears everything. Asks twice - becomes Discard? |
| Save | Save the current graph under a name | |
| Load | Load a saved session | |
| App | Preferences | Settings, 5 tabs |
| Activity log | Engine and app messages |
Status messages#
Below the toolbar, transient confirmations and errors - device opened, node added, connection made. They fade; the full history is the activity log.
Related#
- Latency and Buffers - buffer and latency in depth
- Preferences - the settings dialog
- Sessions and State - Save, Load and New