So&are Notes
l Press
EnteraYes.
The display shows KEYBOARD VERSION ZZZ. For the Rack, this will
always show 1.
Version 1.25 disk (released 8 FEB 93)
For ASR-10 Keyboards ONLY.
This disk is only compatible with 1.00 ROMS. This is not
u
typical O.S. Release?
This
OS.
update is intended for customers who have a keyboard with 1.00 ROMs but do not need or want the SCSI kit. (When they buy
SCSI, they automatically get 1.50 ROMs if they don’t have them.) This release provides them with a method of upgrading their operating
system without the expense of a ROM change. Because this was a patch to the existing 1.20 O.S. disk, there are some known problems
that still exist in this release. The purpose of this release is to address the serious problems that can cause a crash or corrupt data. No new
features are added.
SEQUENCER
Loading SINGLE sequences from disk corrupted parameters of sequence that was currently selected. The selected sequence inherited the
following parameters from the sequence being loaded: loop switch, tempo, time signature, sequence length in bars. Symptoms that would
show include: keeping new after track edit results in no data left on track or extra events on track, tempo mysteriously changing on
sequence, bar counters looping prematurely or beyond the actual end of the sequence data. Auto-locate malfunctioning on specific
sequence. This problem has been in existence since
1
.OO. It has been addressed in version 1.25.
QUANnZE
track had a problem that caused track cleaner to erase the track. Symptom will be that user quantizes, track auditions tine.
but
is erased on a keep new. Not extremely likely, but you will get some calls about this. The quantize problem has been around since the
EPS days, but the track cleaner (which was introduced in version 1.20) makes the problem much more visible. In version 1.05, an
improperly quantized sequence may have played tine but subsequent track edits or overdubs could crash the system or destroy other
sequence data. The quantize problem has been fixed in version 1.25, the track cleaner is still in place.
Attempting to change the length of a song track through the CHANGE SEQUENCE LENGTH command resulted in ERROR 129. This
command is not available for song tracks. The only way to change the length of a song is to edit song steps. If user attempts to run the
change sequence length command when a song is selected, version 1.25 now displays SELECT SEQUENCE FIRST message.
WAVESAMF’LE EDITS
l
Performing a command like FADE IN on a Stereo sample with STEREO LAYER LINK ON caused the ASR to stop recognizing WS
numbers when you play the keyboard.
Inc/dec
keys do not function properly for wavesample selection. This is a BIG problem introduced
in version 1.20 that can happen when you do any stereo wavesample command that gives you an audition. Wavesamples may appear in
both layers or may have “moved” from one layer to the companion layer. The only way to recover your instrument is to “rebuild” the
instrument layer/wave maps by creating a new instrument and copying over the wavesamples to the new instrument, then deleting the old
instrument. If you suspect this problem, here’s how you can check your stereo instruments for valid layer/wave maps:
1. With STEREO LAYER LINK ON, select the left layer, then select the wavesample field.
2. Use the up-arrow to scroll through all wavesamples. Verify all the wavesamples for that layer exist.
3. Repeat this on the same layer using the down-arrow. Any discrepancies indicate a bad layer map.
4. Select the right (companion) layer and repeat steps 2 and 3.
This problem has been addressed in version 1.25.
Also verify that no wavesample appears in both the left and right layer.
MISC
l
A low-level bug existed that could cause the system data to be corrupted. Due to the nature of this bug, the exact circumstances that would
cause a problem and the symptoms that would show up are entirely unpredictable. This has been addressed in version 1.25.
KNOWN PROBLEMS
J.N
VERSION 1.25:
The following problems are known to exist in version 1.25. If a customer has 1.00 ROMs and is reporting any of the following problems,
the 1.25 O.S. disk will
NOT
solve his problem. The only recourse is for the customer to upgrade to I .50 ROMs.
MERGE TRACK COMMAND incorrectly allows you to specify ranges. The ranges are ignored when the command executes and the
merge is performed over the entire track.
exists in version 1.25.
Version 1.50 no longer allows ranges to be specified for this command, but this problem still
AUDIO GLITCHES (distortion, loss of stereo phase) that occur intermittently when all sequencer tracks are playing. It is NOT voice
stealing or effects related. This is due to OTTO losing sync of the beginning of the sample. Low probability. NOT addressed in version
1.25.
TIME COMPRESS/EXPAND is still not 100% reliable. Some portions of samples may not compress or expand at all. Other sections
may compress too much. Particularly noticeable with jam loops. It appears that experimenting with the quality value can correct the
problem. (For example, a sample that would not compress at quality of 25 would compress at a quality of 26.) The algorithm is being
reviewed. A change should be forthcoming that at least reduces the chances of failure. (Note that the audition gives you an accurate
picture of what the compression/expansion has done, and keeping the old will leave the original wavesample intact.)
Also note that time
compression/expansion of stereo samples may result in loss of phase. (That’s the way it is.) Still a problem in version in 1.25
and
1.50.
Attempting to edit the KEY RANGE with the data slider for samples that have STEREO LAYER LINK=ON results in LAYER EDIT
NOT ALLOWED. Not addressed in version 1.25, use
incfdec
buttons or keyboard to set wavesample key ranges.
MACRO files will not load. Still a problem in version 1.25.
MACRO files will not save correctly. Saving a macro file to floppy disk results in display saying “SAVING ASR-10 OS.” This is a
display anomaly only, the O.S. is not being overwritten. Still a problem in version 1.25.
A problem exists in the logic that waits for Enter or Cancel to be hit. A typical example would be some floppy disk commands (COPY
OS DONE. ANOTHER?). We found that if the user does nothing for 60-seconds, the system will timeout and the timeout logic could
lockup the display. Still a problem in version 1.25.
ENTER PLAYS KEY feature does NOT exist in version 1.25.
ASR Service Manual
27
To Next Page
Loading...
Need help?
General
