Sessions and State
Saving and loading sessions, what opens at startup, and what happens when a device is missing.
new user
A session is the whole canvas: nodes, connections and gains, groups, the device and its settings, and plugin settings.
| Do | How |
|---|---|
| Save | ⋮ → Save, name it. Every tier |
| Load | ⋮ → Load (Pro) |
| Clear | ⋮ → New - click twice to confirm |
At startup#
Free starts with an empty canvas every time. Pro chooses in Preferences → General → When Routling starts:
| Choice | Opens |
|---|---|
| Resume where I left off | Everything as it was when Routling closed, tray panel changes included |
| Load a session | A saved session you pick |
| Start empty | An empty canvas |
If the last run ended with a driver crash, Routling starts empty and names the driver.
When something is missing#
| Missing | What happens |
|---|---|
| The session's ASIO device | You pick another ASIO device or the built-in clock (which leaves out the ASIO channel nodes) |
| A secondary device or app | Kept as a placeholder; reconnects when it returns |
| A network stream's sender | The Network In waits and connects when the sender is back |
| A plugin | Removed from its chain |
Files#
All in %APPDATA%\Routling: sessions\ (named sessions), session.json (what Resume reopens), preferences.json, window-state.json.