Section 12 — Sequencer and Audio Track Concepts
ASR-10 Musician’s Manual
50
About Audio Tracks
How Existing Sequence Commands Affect Audio Tracks
Sequencer commands only affect the Audio Trigger events, and do not affect the associated
AudioSamples. Only the following functions will affect the AudioSamples:
• Punching-in on an Audio Track
• Command/Seq•Song, ERASE ALL AUDIOSAMPLES
• Command/(audio) Track, DELETE AUDIOSAMPLE
• Command/(audio) Track, ERASE AUDIO TRACK
• When the SAVE SONG + ALL SEQS command is invoked, the SONG + ALL SEQS file type
can now be saved across multiple disks. It may be very large if it contains large RAM
AudioSamples.
• After performing the Command/Seq•Song, APPEND SEQUENCE, CHANGE SEQUENCE
LENGTH, and EDIT SONG STEPS Commands on Sequences that have data recorded on their
Audio Tracks, the “PREPARING AUDIO TRACKS” message will be displayed as Audio
Tracks are cued up for Playback.
Caution:
Most sequence commands only affect the Audio Triggers, and not the
AudioSample data. Remember, the same AudioSample can be triggered
by many different sequences as a result of using the COPY SEQUENCE
or COPY AUDIO TRACK Commands. If you punch in on an
AudioSample that is used elsewhere, it will be modified elsewhere as
well. We recommend performing sequence commands before recording
any data to Audio Tracks.
• The DELETE SEQUENCE and ERASE SONG + ALL SEQS Commands will
NOT
delete the
AudioSamples that are triggered by Events on the Sequence’s Audio Tracks.