Section 12 — Sequencer and Audio Track Concepts
ASR-10 Musician’s Manual
42
About Audio Tracks
• See the punch-in examples below for more details.
☞
Note about Auditioning DiskTracks: If punching in on an existing AudioSample, the Audition
playback requires much more disk activity than what it would after a KEEP=NEW. (This is
because selecting KEEP=NEW converts the two separate AudioSamples into one AudioSample,
eliminating disk fragmentation if possible.) Therefore, you are more likely to experience missed
audio playback during Audition.
Amalgamation
Amalgamation is the way the ASR-10 automatically tries to unite all punched-in AudioSamples
into one AudioSample, which helps to avoid disk fragmentation.
Amalgamation of SCSI-based AudioSamples may require free disk space to build the
amalgamated AudioSample. This means that you might encounter a scenario wherein there is
enough room on disk to record, but not enough room to amalgamate. In this case, keeping NEW
after a punch-in will keep the NEW AudioSample without amalgamating it.
Punch-In Cases for Audio Track Overdubbing
Examples 1-5 describe the most common punch-in situations:
PUNCH-IN TABLE
In the following examples:
Audio Trigger event:
▼
Original data of AudioSample 1:
ABCDEFGHIJKLMNOPQRSTUVWXYZ
Audio Trigger event:
▼
Data that you punch-in (AudioSample 2):
abcdefghijklmnopqrstuvwxyz
PUNCH-IN Example 1:
(Punch-in and out occur during AudioSample 1)
Audio Trigger event:
▼
Original data of AudioSample 1:
ABCDEFGHIJKLMNOPQRSTUVWXYZ
Data that you punch-in (AudioSample 2):
..........abcdef..........
What you audition:
ABCDEFGHIJabcdefQRSTUVWXYZ
Audio Trigger event:
▼
What you keep:
ABCDEFGHIJabcdefQRSTUVWXYZ
Note: AudioSample 1 data has changed. It is the same size.
