NRTDRV MAN EN KNOWNPROBLEMS
Contents
Known issues (or specifications)
Problem of loading
Software LFO or OPM tone definitions are high-loaded processes. If you use software LFO in some channels simultaneously or change tones only for only attack every time key on, it causes slowness in real machines.
We recommend load balancing in data, such as reducing software LFO or shifting 1 or 2 counts. We wish repair it as soon as ideas about optimization is found.
Problem of relative values
Relative volumes or relative octaves are changed to absolute value while compiling and then output data. Since only first one is effected in looping or repeating.
For example, "v15o1[8cv->c]" means "v15o1[8cv14o2c]" in real data. If you want use relative value repeating same phrases, don't use repeating but but use compiler macro.
Problem of folders
Folders of hoot, Pasmo, 7-Zip and ASLPLY cannot be specified freely. All of them should be placed appropriate folders.
Problem of pitches
Standard pitch of OPM is 438Hz, so if you need pitches based on 440Hz, set "5" for #DETUNE_OFFSET_OPM.
Problem of software LFO in key on non-synchronized mode
When using the SSP command (software LFO asynchronous mode), the center of the software LFO may deviate if the note head and software LFO folding timing overlap.
Note, it is specification related to designing driver.
Problem of end detection
NRDSEL cannot detect end after playing in only few music data. Conditions or repeatability is not clear, if experience it please send report to us. We are ready to research and fix it.
