Glicol BPM is set at launch with `-b` and cannot be changed in-file during a session

The global tempo in Glicol CLI is a launch-time flag (-b 120), not a parameter that can be set or changed inside the .glicol source file. Changing tempo within a live session requires either relaunching the CLI with a new -b value, or restructuring patterns with speed multipliers relative to the fixed BPM. The speed node is the in-session tempo tool: speed 2.0 doubles the rate of whatever follows it.

Examples

glicol-cli -b 140 mytrack.glicol // sets 140 BPM at launch // In-file: speed 2.0 >> seq 60 _ 60 _ — doubles internal rate

Assessment

A performer wants to move from 120 to 140 BPM mid-set without relaunching the CLI. Describe two workarounds available within the session.