In other words, the mezzo ranges are different from the forte ranges.
Example
Code: Select all
<region>
sample=Mezzo.wav
lovel=0 hivel=74
lokey=C4 hikey=A4
<region>
sample=Forte.wav
lovel=75 hivel=127
lokey=F4 hikey=C5
Code: Select all
Forte ├F4──────────C5─┤
Mezzo ├C4─────────────A4─┤
Code: Select all
Forte ├F4──────────C5─┤
Mezzo ├C4────E4┤
After some experiments I found that when key ranges are congruent, SynthMaster will behave correctly:
Code: Select all
<region>
sample=Mezzo.wav
lovel=0 hivel=74
lokey=C4 hikey=C5
<region>
sample=Forte.wav
lovel=75 hivel=127
lokey=C4 hikey=C5
Code: Select all
Forte ├C4───────────────────C5─┤
Mezzo ├C4───────────────────C5─┤
Code: Select all
<region>
sample=Mezzo.wav
lokey=C4 hikey=E4
lovel=0 hivel=74
<region>
sample=Mezzo.wav
lokey=F4 hikey=A4
lovel=0 hivel=74
<region>
sample=Forte.wav
lokey=F4 hikey=A4
lovel=75 hivel=127
<region>
sample=Forte.wav
lokey=A#4 hikey=C5
lovel=75 hivel=127
Code: Select all
Forte ├B4─C5─┤
Forte ├F4────A4┤
Mezzo ├F4────A4┤
Mezzo ├C4────E4┤
It's the only substitute for Alchemy (I find it even better than that), since the PC version has viciously been stopped by Apple.
And it's the only VST that can reproduce all of the 90's digital synth workstations, because it has 2 Sample-playing oscillators (in opposition to the thousands of "virtual analog" crap VSTs).
So I started virtualizing all my hardware synths and adopting my SFZ library, but this bug (and the loop interpretation bug*) stopped me for the moment.
Is there any chance that these 2 guys will be fixed soon?
*) Loop Interpretation Bug:
"SynthMaster's interpretation of sample loop info"
