What is velocity?

[Robert Puza]

@d-healey exactly that's a fixed solution. But yes.. that's the same effect. exactly

[Robert Puza]

@d-healey but you actually solved it.

I can create multiple sample maps and give the option to switch between them

Thank you

[d.healey]

@Robert-Puza Why do you need multiple sample maps?

[Robert Puza]

@d-healey in one there will be the quietest velocity layer, for example HiVel 50, and in the other sample map HiVel 53. If I make 3 sample maps, I have 3 velocity curves.

[d.healey]

@Robert-Puza Put all your samples in one sample map. Let's say you have 3 dynamic layers. Map dynamic 1 to the velocity range 1 - 42, dynamic 2 to 43 - 84, and dynamic 3 to 85-127.

HISE will automatically trigger the correct sample based on the incoming velocity. If the user change the velocity curve of their keyboard then a different velocity will be sent to HISE and the correct sample will trigger.

[Robert Puza]

@d-healey Yes. I understand you. And by creating more sample maps I could change this constellation. (1 - 42, dynamic 2 to 43 - 84, and dynamic 3 to 85-127)

[d.healey]

@Robert-Puza said in What is velocity?:

(1 - 42, dynamic 2 to 43 - 84, and dynamic 3 to 85-127)

That was just a suggesting as it provides equal range for each layer, but you can skew it to a different range if you prefer. You can also remap the velocity dynamically using a script.

[Robert Puza]

@d-healey

[Robert Puza]

@d-healey For a user of a Hise based virtual musical instrument, the ability to set the velocity, which is replaceable by the velocity setting in the midi keyboard (usually 3 curves), is MORE IMPORTANT than having the ability to set the velocity modulator.

That's true

and for example 3 samplemaps can solve this. I hope it will be easy to switch on the interface

[d.healey]

@Robert-Puza Why not add a velocity curve editor to your UI, it's very simple to make.

[Robert Puza]

@d-healey I like it. but Can I set it to trigger a sample from the loudest velocity layer with a soft hit?

[d.healey]

@Robert-Puza The X axis is input velocity, the Y axis is output velocity. So the curve you set controls the output and gives you complete control over the whole velocity range.

[Robert Puza]

@d-healey and which processor id do you assign to it? velocity modulator1?

[d.healey]

@Robert-Puza There is no built in processor for this. You need to write a script that takes the incoming velocity and uses the table to send out the modified velocity.

However if you're releasing this project as GPL you can use the one I have already written (I should probably relicense this anyway as CC0 since it's such a simple script) - https://codeberg.org/LibreWave/RhapsodyBoilerplate/src/branch/main/modules/VelocityScaler.js

[Robert Puza]

@d-healey
This looks great
Thank you

[Lindon]

@d-healey said in What is velocity?:

@Robert-Puza There is no built in processor for this. You need to write a script that takes the incoming velocity and uses the table to send out the modified velocity.

isnt this the inbuilt processor he's looking for - or am I missing the point here?

[d.healey]

@Lindon that uses velocity to control the parameter you've assigned it to, in this case volume. It doesn't change the actual velocity value entering the sampler.

[Lindon]

@d-healey gotcha

[Robert Puza]

@Lindon Velocity modulator is a very useful tool.
But is "only" volume.
The setting option that David wrote in his script is the most important. (Velocity input setting )

[Lindon]

@Robert-Puza said in What is velocity?:

@Lindon Velocity modulator is a very useful tool.
But is "only" volume.
The setting option that David wrote in his script is the most important. (Velocity input setting )

yes, but no.... create a global modulator for velocity like this:

and apply it anywhere you can apply a GM...

Here it is being applied to an envelope attack: