Put the right change
on the right beat.
The timeline is where saved sounds become a performance: place discrete changes, shape continuous ones, and rehearse the result.
The illustration plays when it comes into view. Pause it, drag the timeline, or pan the overview. Section titles stick at the leading edge until the next section takes over. Illustration only; no MIDI or audio is sent.
Read the timeline.
The playhead shows your current position against the song’s section and beat structure. Event markers represent discrete changes. Ramps represent a control changing over a span of time.
Use the timeline editor to work with sections, events, and ramps. Playback view and edit view have different jobs: rehearse in playback, then return to editing when you need to change the song.
Place preset and patch events.
Add a preset or patch event at the musical position where you want the change. Use a device preset for a single-device instruction, or a patch when the cue needs a combination of saved presets.
Rehearse the lead-in and the moments after the event. A cue can be sent at the intended position while the receiving hardware still takes time to switch sounds. Verify the audible result, not only the onscreen marker.
Shape changes with ramps.
A ramp changes a device control across a duration rather than sending a single fixed value. Choose the device and control, then configure the available range, duration, and curve settings.
Use a ramp for an illustrative gradual effect change, such as increasing a delay amount over a phrase. The receiving device must support the selected MIDI control and values.
Define the device’s controls first. The ramp editor needs a control to target; a device name alone does not tell Petal which MIDI CC to change.
Test the transitions.
- Play through the cue from an earlier position.
- Pause and resume around the change.
- Seek or navigate between sections and confirm the rig reaches the expected state.
- Try the same song again after loading a different song.
Event notifications produce a ripple on the timeline. Use the visual feedback as a cue that an event was reported, then listen to the connected hardware to confirm the actual result.