■ About errors that occur when converting STANDARD MIDI FILE and how to deal with them

1. could not open song file.
2. could not open output file.

   There is a disk error. Check your hard disk using NORTON UTILITY, etc.

3. seek error.

   Seek error. Take the same action as a disk error.

4. there is more than 32 tracks. There is XX tracks (including tempo track).

   There are too many tracks in a Standard MIDI File. The maximum number of sequence tracks for Saturn, including the tempo track, is 32.

5. resolution is written as absolute time.

   The resolution is written in absolute time. Toggle the options for saving a standard MIDI file on the sequencer.

6. unknown event in out file.

   There is an unknown event. You may think that the data is corrupted, so please save the standard MIDI file again.

7. distance of 2 events is over XX, too far to reference other event and omit. Turn'find same data' option off.

   There is too much data in the file to detect repeatedly. Turn off repeat detection off and convert.

8. not enough memory.

   Not enough memory. Try closing the applications that are running at the same time. If you still get this error, try restarting your Macintosh.

9. could not release memory space.
10. memory access error.

    There was a memory problem. Try restarting your Macintosh.

11. illegal block type in header block.
12. could not find'MThd'.

    The data may be corrupted, so try saving the Standard MIDI File again.

13. can not convert this type of SMF "this program require'FORMAT 1'.

    The format of the standard MIDI file is other than TYPE1. Save TYPE1 with the sequencer.

14. illegal block type in track block.could not find'MTrk'.
15. illegal event in SMF "" track No = XX

    An unknown event exists on track XX.
    You may think that the data is corrupted, so please save the standard MIDI file again.

16. too many events.there is more than XX events "

    There are too many events. Reduce the data to 65536/1 sequence.

17. tempo <xx.xx bpm.

    The tempo is too slow.

18. tempo> xx.xx bpm. This song is xx.xx bpm.

    The tempo is too fast.
    The tempo of the sequence should be in the range 40-300.

19. Loop command must appear 0 or 2 times. It appeared% d times.

    There is one or three or more loop commands for control change number 31.

20. Tempo event appeared after other event. Tempo event must appear in top of song.

    The tempo event exists after the other events. Correct the data with the sequencer.

21. Note off appeared before 1st bank change (= bank select).
    Note on appeared before 1st bank change (= bank select).
    Poly --Key Pressure appeared before 1st bank change (= bank select).
    Ch --Pressure appeared before 1st bank change (= bank select).
    Program change appeared before 1st bank change (= bank select).

    The position of bank change (Control change # 32 = bank select) at the beginning of the track is too late.

22. Note off appeared before 1st program change.
    Note on appeared before 1st program change.
    Poly --Key Pressure appeared before 1st program change.
    Ch --Pressure appeared before 1st program change.

    The position of program change at the beginning of the track is too late.

    * Basic data layout at the beginning of each track (standard specifications after Version 1.25)

    1/1/000 (bar / beat / clock)

    Tempo event (usually the sequencer inserts automatically), bank change (# 32)

    1/1/001 (bar / beat / clock)

    Program change, control change (MAIN VOLUME # 7, loop command # 31 at the time of loop, etc.)

    1/1/002 (bar / beat / clock)

    Note on

    The number of clocks per beat depends on the resolution of each sequencer. Also, set the MAIN VOLUME of Control change # 7 at the beginning of each track.
    Depending on the sequencer, if multiple event data are placed in the same measure / beat / clock, the order in which they are displayed on the screen of the sequencer and the order in which they are written to Standard MIDI File may change. If you want to clarify the order of the events, shift the data by one clock.
    Satan's sound driver processing is based on 2 msec, so even if you create sequence data that treats one beat as 480 clocks, if you perform convert playback, one beat will have a resolution equivalent to 250 (when the tempo is 120). It will be played as if it was quantized.

23. Note on appeared without note off Interval in track X,

    The data may be corrupted, so try saving the Standard MIDI File again.

24. Note on must be more than 2 clocks distant from same-pitch-note on. \ N Or, gate time is too short. Pitch in track% d,% ld clocks from end of song.

    Please shift at least 2 clocks with the resolution of the sequencer between NOTE-ON and NOTE-ON of the same pitch.

25. there is too many songs. Must less than 300 songs in a same folder.

    Full Auto CNV conversion is up to 300 in the folder.

26. There is too many tempo events.

    There are too many tempo events. Up to 8190 tempo events in a sequence.

■ About errors when creating a sequence bank

1. Couldn't open temporary file
   I can't create a temporary file for work.

   This happens when another application is already using a file with the same name as the Song collecter temporary file in the current folder (almost impossible).

2. Couldn't open output file
   I can't create an output file.

   If there is already a file with the same name, it will be overwritten, but if another application has a file with the same name open, this error will occur.

3. Couldn't open song file
   The song file does not exist.

   It is possible that the position of the song file was moved or deleted after the setting (since it can be opened read-only, the song collecter can be viewed even if the sequencer etc. is open).