disable velocity when creating a program?

[lalexander2025]

Hi folks,

a question for you, as this is now driving me mad...

I can easily achieve this on my stage 4, but my wave 2, that's a different kettle altogether.

On my stage 4, if I'm using a sample as an example, I can turn off the velocity sensitivity, so it just runs a single velocity throughout. but on the wave 2, I can't seem to find that.

I'm trying to program a set of sounds where there's no velocity needed but regardless, velocity is still there.

Could someone guide me please as to how to solve this. I can't even find this in the user manual and it seems daft not to be able to remove velocity on sample trigger, etc.

any thoughts?

lew

[DJKeys]

If I load a sample into my Wave 2, velocity sensitivity is not enabled by default. If you enable the filter for the loaded sample, you also turn velocity on or off.

Could you provide a little more information on the workflow? Seems to work fine for me.

-dj

[lalexander2025]

solved the headache but it leads to a bug in NSM by the sound of it.

I have an old sample in original nsmp format which has to be converted to .nsmp3 format by NSM, now the weird thing is this, this same sample goes in to my stage 4 fine after converting and velocity is fixed by default ready for me to change if I need to, but that sample isn't one I want to have a velocity profile to.

I've tested other samples, no issues, but this one seems to be doing something it shouldn't do when converted to .nsmp3 format and it seems to be a possible bug with NSM itself, or maybe a potential firmware issue but I doubt that, although nord is not issuing firmware updates for this anymore, as if it's being killed off.

oh well.

just seems odd that this same sample I've had for some time works fine on my stage 4 after converting, yet the wave 2 is treating it with velocity applied although it's not active on the wave 2. the velocity curve setup indicates it's off, turn it between 1 and 3 and it changes the velocity range, turn it off, the velocity curve like it's being treated by the filter envelope is being done somehow, although OFF. this is just odd.

but it's not terating other samples like this.

oh well.... gremlins....

lew

[DJKeys]

If only one sample is doing this, then sounds like an isolated anomaly.

-dj