Renardo startup files run automatically on launch to pre-configure the session environment

Startup files are Python files that Renardo executes at launch before the user types anything. They are used to set a default scale and root, define shared rhythm patterns, set Clock.bpm, and load any session-specific configuration. Multiple startup files can exist; one is designated as the default. Startup files appear as special tabs in the web editor and must be saved explicitly (distinct from session code). The recommended practice is to keep startup files small and modular — one per project type — and test them before saving to avoid startup errors that block session launch.

Examples

# my_setup.py — a startup file
Root.default = 0
Scale.default = Scale.minor
Clock.bpm = 120
d_pat = P[1,0,0,1,0,1,0,0]

Assessment

What is the difference between a startup file and regular session code? What happens if a startup file contains an error? Name two things that should always go in a startup file.