Fripp States During Ad-hoc Recording

When you first launch the application, or when you stop sequencer playback, Fripp enters the Ad-hoc Recording state. If you begin an ad-hoc recording, Fripp will end it when you've been silent for some interval (called the MaxSilenceInterval). During Ad-hoc Recording, the length of the MaxSilenceInterval is the value of the MaxAdhocRecordingSilenceInterval setting, which defaults to 2 seconds, and is user-configurable.

The following diagram represents the various states that occur during Ad-hoc Recording.

As Ad-hoc Recording begins, Fripp creates a new sequence, and transitions immediately to the PendingFirstAdhocInput state. When Fripp receives its first MIDI input in this state, it sets the start time of the sequence to the exact time of that input, records that input, and enters the PendingMoreAdhocInput state.

Upon entering the PendingMoreAdhocInput state, Fripp sets a Silence Timer that will go off after the MaxSilenceInterval. If you provide any MIDI input before the Silence Timer goes off, Fripp (not shown here) records the input, and resets the Silence Timer.

If the Silence Timer does go off, Fripp ends the sequence, saves it to history, and transitions to the Coordinating Recording State, passing along the "MaxSilenceElapsed" signal. As we've seen from the overview, the Coordinating Recording State handles that signal by setting Fripp immediately back into Ad-hoc Recording.

So what happens if you quit Fripp, or press the play button while you're holding a note down? Either of those signals the end of the ad-hoc sequence, and (not shown here) Fripp manufactures the end for you by simulating whatever MIDI signals it is waiting for, such as note-offs. It then transitions to the Coordinating Recording State, passing along either the SessionEnd or StartPlayback signal, as appropriate.

Next: Fripp States during Ad-hoc Overdubbing