Chapter 1 Basic Overview

• " Sound Driver Ver.2.20 Programmer's Guide " is a technical document for programmers. Please take a look. It contains important information about sound processing.

• Be sure to use the latest sound driver (Ver.2.04 or later ) except for the project that is just before the release. If you have to use an earlier version due to data compatibility issues, you can only use version 1.33B.
  Match the driver version when creating the data and when incorporating it into the game.
  The version of the sound driver you are using is written in ASCII code when you dump 1020h or later in hexadecimal from the beginning of the driver.
  To determine from the SndSimlator, open "About this SndSimlator" in the Apple menu.

• If the sound doesn't work the way you want it to, or if something goes wrong, there are three things to look for.
  1. Command history
  2. Error status bits
  3. Other sound WORK RAM information such as mode, status, etc.
  For details on these, refer to "Sound Driver Ver.2.20 Programmer's Guide".

• Trouble with submissions in case of sound trouble,
  1. Trouble that can be reproduced on Mac tools
  2. It is normal on the tool, but troubles that occur when it is incorporated into the game
  Roughly divided into, the submission in case of trouble in case 1 is a set of development data on the Mac.
  1. Sound simulator map file
  2. TONE editor tone file (if there is a .bin file)
  3. DSP Linker .YLI file (with .EXB file)
  4. STANDARD MIDI FILE (Type1) output by the sequencer
  5. Explanatory documentation
  In case of 2, in addition to A, B, C, D, E

  6. Explanation of CD-ROM that can reproduce the phenomenon and its reproduction method
  I would like to have.

• 3 ways to control sound from SH2
  1. Use SBL (including PCM and ADPCM playback library) library functions
  2. Use SGL library functions
  3. Write commands directly in the command area without using the sound library

• Basically, the sound tool does not cause any abnormal operation depending on the model of Macintosh regardless of PowerMac or 68x00Mac. The biggest cause of sound tool trouble is SCSI related. To avoid troubles as much as possible, connect the Macintosh and Sound Box with the shortest possible SCSI cable, and do not connect unused SCSI devices. Also, in the Cart Dev. Environment, if MIDI signals and SCSI transfers are performed frequently at the same time, it is easy to freeze, so avoid it as much as possible.

• The TONE editor and DSP linker will not work until after the sound map is transferred by SndSimulator and the sound driver is started. This is because the TONE editor and DSP linker are functioning by referring to the set address and size of the transferred map tone BANK and DSP work RAM.
  The Waveform Editor only uses the RAM of the Soundbox as a work area, so there is no need to transfer a soundmap or start a sound driver. While using the Waveform Editor, some of the LEDs 1 through 8 on the back of the soundbox remain lit, which is normal. The waveform editor uses address 10000H and above as its work area and destroys it. If you want to use the Tone editor or DSP linker again, transfer the data again if necessary.

• Since the PCM stream playback of the sound simulator is also transferred and simulated by SCSI, it may sound different from the actual machine. Think of this feature as simple.

• In Sound Box (Sound Board System), Start up only applies Go to the sound driver, and the sound driver is transferred when the Snd Simulator is started.

• SndSim 2.0 or later works only with Driver 1.29i or later. Earlier sound drivers cannot be used.

• The four sets of LEDs (32K, 44.1K, 48K, PARITY, DE-EMP display) of the Sound Box (Sound Board System) do not affect the operation of the sound tool in any lighting state. For 32K, 44.1K, and 48K, it lights up corresponding to the sampling rate of the optical input of the sound box. Inputs other than 44.1kHz are possible, but operation is not guaranteed, so please stop.

• LED specifications on the back of the Sound Box (Sound Board System) When the boot ROM is started, it moves and blinks while shining from LEDs 1 to 8. During the period when data is transferred using SCSI, this operation is stopped for a moment, but it is restored after the transfer is completed.
  After transferring the driver to the target, when the program is executed, LED1 blinks and you can confirm that the CPU is operating normally.

  The meaning of blinking of other LEDs when LED1 is blinking (CPU is operating normally) is as follows.

  LED2: CPU processing capacity MAX

  LED3: BGM decompression interrupt is being driven (normally blinking).

  LED4: no care

  LED5: no care

  LED6: no care

  LED7: MIDI input from MIDI-IN2 on the board.

  LED8: MIDI input from MIDI-IN1 on the board.

  In addition, blinking of other LEDs when LED1 is off means the following error (if it remains lit, it means that SCSI communication is in progress or the driver is HALT).

  LED number 12345678	meaning
  	YM3802 (MIDI-1) IRQ vector error
  	// (MIDI-2) //
  	MIDI data error
  	YM3802 (MIDI-1) MIDI out error
  	// (MIDI-2) //
  	MIDI Control change $ 60 ~ $ 7F input
  	HOST I / F Commnd execute error
  	...........
  	...........
  	Map change error
  	BANK change error
  	MIXER change error
  	EFFECT change error
  	68k un-deffinition vector event
  	...........
  	68k buss error
  	68k address error
  	...........
  	68k level-3 event
  	68k level-4 event
  	68k level-7 event

• 68EC000 with 16Bit and 11.3MHz clock controls SCSP as a dedicated CPU for sound control. The 68EC000 is directly connected to the SCSP and operates independently of the SH2. You can also access SCSP from SH2. Neither SCSP nor 68000 will stop at the time of access, but the processing capacity of 68000 will decrease if the amount of access from SH2 is large due to time division processing.

• The clock of the SCSP chip is 22.58MHz, and the clock of 68000 is 11.3MHz.
  Regarding the CPU execution unit time of the sound driver,

  The execution unit time of software DSP control is 8 msec.

  The execution unit time of software PLFO is 4 msec.

  The execution unit time of other target programs is 2 msec.

• PCM data size blister knowledge
  88kbyte per second at 16bit 44.1kHz (about 5 seconds at 450kbyte, which is almost the maximum of sound RAM).
  11kbyte per second at 8bit 11kHz (about 40 seconds at 450kbyte, which is almost the maximum of sound RAM).
  Since one waveform is up to 64ksample in SCSP, it takes 0.72 seconds at 44.1kHz and 2.9 seconds at 11kHz for both 16bit and 8bit.