I think I've found a bug in MultiSampla.
I was making a drum kit with velocity layers and noticed there are gaps in the velocity layers.
Example.
Layer 1: Low Vel: 0.0, High Vel 80.0
Layer 2: Low Vel: 81.0 High Vel: 127.0
Any note played with velocity 80 will be silent. Could it be the decimal that is the culprit?
Setting both velocities to 81.0 yields the desired result although it would seem like an overlap.
Bug: MultiSampla Velocity layer gaps (MUX VSTi)
-
- KVRist
- 427 posts since 24 Feb, 2015 from Stockholm, Sweden
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
In the above example there indeed is a gap between 80.0 and 81.0, hope you see what i mean.
Solution is to set layer 1 high vel to 80.4 and layer 2 low vel to 80.5.
I agree there is an uncomfort zone due to the decimal point.
I'll finetune that by removing the decimal point from the Low/High Vel properties.
Solution is to set layer 1 high vel to 80.4 and layer 2 low vel to 80.5.
I agree there is an uncomfort zone due to the decimal point.
I'll finetune that by removing the decimal point from the Low/High Vel properties.
-
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
A very minor and almost always inconsequential point (but to avoid the unexpected) -- do note events in the sequencer have integer velocities? If not, once layer bounds are integer, would they round to the nearest integer (80.49 being within 0 to 80, 80.5 being too large), truncate (80.99 being within) or straight compare (80.1 being too large)?
-
- KVRAF
- 13865 posts since 24 Jun, 2008 from Europe
Note velocities are floats. The multisampler layer bounds will be integers. The float to integer conversion will use round to nearest. So in above example the converted velocity range will be [0-80] and [81-127]