FAQSound related
BackForward
FAQ / Sound related

Tone editor



I would like materials for header information other than PCM.

Q)
I would like to know the details of the header information part other than the PCM waveform that is attached to the binary data output from the tone editor.
I'm researching how to have sound data as compressed data on memory.

A)
There is no more detailed material than the one described in the "SOUND MANUAL" tone editor user's manual.
Please study based on this material. If you have any questions, in each case the question is accepted you.

Do not read loop points.

Q)
When a Loop created with Infinity, SD2, WaveEditor, etc. is converted to AIFF and read with ToneEditer,

"LoopPoint could not be obtained correctly"

Message appears, ignoring Loop's StartPoint and EndPoint, and looping from the beginning to the end of the sound data.
Currently, only one piece of data has the correct looppoint, and the others do not read the looppoint as described above.

A)
First, in the tone editor, make sure that the "Check for 3 or more markers" check box in [Function]-> [Initial Settings] is selected.

If this is OFF, loop point acquisition may not be successful when editing loop points between multiple waveform editing tools.

Another possible cause of the error is that the loop start and end points are not one-to-one.
Also, the waveform editing tool you are using is "WaveEditor" provided by us, but please do not use this tool because it has a bug related to the generation of loop point ID information.

When an AIFF file created with a commercially available waveform editing tool is read into "Wave Editor" and output, the loop point is not set correctly due to the above bug.


I can't get the loop point of the data I got from the waveform editor in 2.07.

Q)
Is it a bug or a specification that makes it impossible to obtain loop points from data processed on the waveform editor in Tone Editor 2.07? (Although it was possible with Tone Editor 1.00)
If it is a specification, I want the latest version to be able to handle the data processed by the waveform editor.

A)
It is a specification.
The waveform editor needs to be modified to support this, but this tool has not been upgraded at this time.
I'm sorry, but please use a commercially available waveform editing tool (SD, Infiniti, etc.).

How to check the waveform size accurately?

Q)
There is a part that shows the size on the tone editor, but this depends on whether the sampling rate is 16 bits or 8 bits.
What does it mean to double the size of what was taken in 16 bits on the wave editor and brought to the tone editor?
Where should I look to check the waveform size most accurately with the capacity of Hexa?

A)
On the tone editor, all size notations are done in bytes.
In the wave editor, the size is expressed by the number of samples, so in the case of 16 bits, it is 2 bytes, and in the tone editor, it is double the size.

Currently, the waveform size can only be viewed in Voice units under "Size" in the Voice window. This includes the waveform size + header size for each layer.

In the next release of Tone Editor (Ver3.0), it will be improved to indicate the size for each layer.


What is the AIFF waveform size that can be assigned?

Q)
If you assign an AIFF waveform whose size exceeds 10000 on the tone editor, Mackintosh will stop.
If you forcibly terminate the application while the mackintosh is stopped, the screen will collapse.
If you assign an AIFF waveform whose size does not exceed 10000, it will work normally, and the sample song for sound check will sound properly.

A)
The upper limit of the waveform size that can be assigned in the tone editor is hexadecimal, which is the FFFFH sample.
If the numbers above are in hexadecimal, it's probably because you're simply over the upper limit.
Also, when viewed in the standard I / O dialog, the size is 131070 (= 65536 * 2) for 16 bits and 65535 for 8 bits.

It seems strange only when the parameter change of BendRange is 13.

Q)
You can set the "Bend Range" parameter in the Voice window of the tone editor from 0 to 13, but from 0 to 12, it goes up by a semitone, while at 13, it goes up by 2 octaves.
Is this such a specification?

A)
Values such as 0 to 12 and 24 are set inside the driver, and there are no plans to change this method in the future.
It is confusing to display 13 in the tone editor, so we will fix it so that it will be displayed as 24 in the next release (Ver3.0).

I'm changing the rate of the AIFF waveform to be assigned, is that okay?

Q)
The sampling rate is usually 44kHz, 16bit, but if this is set to 22kHz, it will be one octave lower, so the point has been changed from 60 to 72. What is the problem?
Is there any problem even if 16bit is changed to 8bit?

A)
No problem.

Hang when sending

Q)
When I send it with the TONE editor, it hangs with the clock icon.

A)
Please check the following items.


The MASTER VOLUME change is invalid at the next load.

Q)
Even if you change the MASTER VOLUME of the tone editor to adjust the volume balance of the entire song, it seems that it will be cleared at the maximum value the next time you load it.
How can I adjust the volume of the entire song?

A)
The "MASTER VOLUME" setting in the tone editor is information that is not saved in the tone bank data.
It is the program side, not the data side, that actually sets the volume balance of the entire song.
Please think that only simulation can be done on the sound production side.

How to set portamento parameters?

Q)
Setting portamento parameters in the tone editor has no effect. If you change the play mode from POLY to PORTA, the sound will not be output. How do I set up portamento?

A)
The voice window PORTAMENT TIME is not working.
It is wise not to set it as it will cause trouble.
Future support is undecided.

No sound

Q)
When assigning the waveform with the tone editor, there is no particular sampling rate instruction, so I incorporated it with 18.9KHz Mono described in the ADPCM converter document.
I tried setting the master volume and velocity, but there is no sound.

A)
There is no particular limit to the sampling rate of the waveform to be assigned in the tone editor.
Since Sega Saturn's sound chip (SCSP) processes uncompressed PCM data, it is usually assigned 44KHz, 16bit waveforms with an emphasis on sound quality, and dropped to 22KHz etc. only when it is necessary to save memory usage. increase.
If you don't hear any sound, check the following items.

Check on the sound simulator:

Check on the tone editor:

What is displayed in the viewfinder

Q)
In many cases, the file size becomes large even though the file size is reduced by removing the tone layer etc. using the tone editor.

(When using the viewfinder) When I look at the tone editor, a file of 96,456B is displayed as 117K in the viewfinder.

A)
The size display function of the viewfinder is simple and not accurate.

Parameters for Verocity Edit

Q)
Regarding VELOCITY EDIT of the tone editor, there are items such as V0, L0, V1, L1, V2, L2, L3, but I can't understand what they mean by reading the manual.

A)
V0, V1 .. correspond to the Verocity Level when received by MIDI.
L0, L1 .. correspond to the actual output level.
V0, V1, V2 can be used to set three curve change points, and L0, L1, L2, and L3 can be used to adjust the output level to control the actual output Verocity.

BackForward
FAQSound related
Copyright SEGA ENTERPRISES, LTD ,. 1997