Bug: Key Range and Velocity Layers not supported correctly

Official support for: kv331audio.com
Post Reply New Topic
RELATED
PRODUCTS

Post

I've got many SFZ with complex velocity layers in which the key ranges per velocity are not congruent.
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
Expected behaviour (working correctly in all other SFZ players)

Code: Select all

Forte          ├F4──────────C5─┤
Mezzo ├C4─────────────A4─┤
Actual behaviour of SynthMaster

Code: Select all

Forte          ├F4──────────C5─┤
Mezzo ├C4────E4┤
The mezzo layer's key range is truncated by the forte layer, although the should be independent.

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─┤
So I derived the following (not really appropriate) workaround: I separated the intersecting ranges and created redundant ranges for the Mezzo/Forte sample:

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┤
This is extremely sad, because I wanted SynthMaster to be my final and only VST to use as live instrument on stage, because it's perfect in so many ways.
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"

Post Reply

Return to “KV331 Audio”