Japanese
SOUND Manual

Collection of errors related to sequences


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

(SndSimulator Ver.1.25 or later)

  1. could not open song file.
  2. could not open output file.
    Disk error. Check the hard disk using NORTON UTILITY.

  3. seek error.
    Seek error. Please respond in the same way as you would for a disk error.

  4. there is more than 32 tracks.there is XX tracks (including tempo track ).
    The standard MIDI file has too many tracks. The maximum number of sequence tracks for Saturn is 32, including the tempo track.

  5. resolution is written as absolute time.
    Resolution is written in absolute time. Please switch the options when saving the sequencer's standard MIDI file.

  6. unknown event in out file.
    An unknown event exists. The data may be corrupted, so please try saving the standard MIDI file again.

  7. distance of 2 events is over XX ,too far to reference other events and omit. turn ' find same data ' option off.
    There is too much data in the file for repeated detection. Please turn off repeat detection and convert.

  8. not enough memory.
    Not enough memory. Try closing any applications that are running at the same time. If this error still occurs, try restarting your Macintosh.

  9. could not release memory space.
  10. memory access error.
    A memory problem has occurred. 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 standard MIDI file format is other than TYPE1. Please save TYPE1 on 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.
    The data may be corrupted, so please try saving the standard MIDI file again.

  16. too many events.there is more than XX events"
    There are too many events. Please 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 your sequence should be between 40 and 300.

  19. Loop command must appear 0 or 2 times. it appeared %d times.
    There is one or more loop commands for control change number 31.

  20. Tempo event appeared after other event.tempo event must appear in top of song.
    A tempo event exists after other events. Correct the data using 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 bank change (Control change#32= bank select) position 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 program change position at the beginning of the track is too late.

    *Basic data arrangement at the beginning of each track (standard specification since version 1.25)

    1/1/000 (measures/beats/clock)
    Tempo event (usually inserted automatically by the sequencer), bank change (#32)

    1/1/001 (measure/beat/clock)
    Program change, control change (MAIN VOLUME#7, loop command #31 when looping, etc.)

    1/1/002 (measure/beat/clock)
    note on

    The number of clocks in one beat varies depending on the resolution of each sequencer. Also, set 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 displayed on the sequencer screen and the order written to the Standard MIDI File may change. If you want the order of events to be clear, shift the data by one clock.
    Saturn's sound driver processing is based on 2msec, so even if you create sequence data that treats one beat as 480 clocks, when converted playback, one beat will have a resolution equivalent to 250 clocks (if the tempo is 120). It will be played as if it were quantized.

  23. Note on appeared without note off pitch 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.
    Between NOTE-ONs of the same pitch, please shift at least 2 clocks depending on the resolution of the sequencer.

  25. there is too many songs. must less than 300 songs in a same folder.
    Full Auto CNV conversion is limited to 300 in a folder.

  26. There is too many tempo events.
    Too many tempo events. There can be up to 8190 tempo events in one sequence.


■About errors when creating sequence banks

  1. Couldn't open temporary file
    Unable to create temporary work file.
    This happens when another application is already using a file with the same name as Song collector temporary file in the current folder (almost unlikely).

  2. Couldn't open output file
    Unable to create output file.
    If a file with the same name already exists, it will be overwritten, but if another application is opening a file with the same name, this error will occur.

  3. Couldn't open song file
    Song file does not exist.
    The song file may have been moved or deleted after the settings were made (it can be opened read-only, so even if the song file is open in a sequencer, you can still view it in Song Collector).


SOUND Manual
Copyright SEGA ENTERPRISES, LTD., 1997