Solved Impact XT velocity issue.

[Jacelane]

Hi there,

I'm having an issue with Impact XT where after I load a sample, when adjusting the velocity in the piano roll editor, it does not change the volume of the sample at all. When I load the same sample in SampleOne XT, as long as "amp" is enabled, you can hear the sample increase and decrease in volume as I adjust the velocity parameter in the piano roll editor. No clue how to get this to work on Impact XT

I'm using Studio one Pro 6 and windows

Any help would be appreciated.
Thank you

 

[lokeyfly]

If the sample isn't changing in volume in Impact XT, but does so in Sample One with Amp enabled, it's likely an envelope setting. Try the different AHD settings in Impact. Particularly keeping A (attack) down, and moving H and D around (hold & release). Otherwise, the sample is only acting and on Amp which encompasses ADSR being switched on or off, along with its settings.

It also might pay to check the device or controller that you're triggering the sample from, and that it's not set to full on velocity. That might be overriden when using Sample One's Amp on setting.

There is also the outside chance the patch, that the sample has some velocity limits.

Alao, and very helpful would be if you could specify the sample so that I could check and verify. Thanks.

 

[Jemusic]

Can you let is know the exact name of the sample/preset and even what library it came from. If its from a Studio One Soundset that is. We can then load it up and see what might be going on. Velocity many not be being routed to the amp volume in Impact XT.

 

[lokeyfly]

..... Just asked that. ; )

 

[Jemusic]

Yes you did and its a good question too. I thought it good to start with Studio One Soundset? then Patch name. Sample is a third name. We may or not have that library too but its a good start. But if its a random sample imported into Impact then I have done this here. This control as pointed out sets the amount of velocity control. It actually defaulted to that. But check this for a fully clockwise setting gives you the most range. I tested this with recording a part, changing velocities and that all worked correctly.

 

[lokeyfly]

I was wondering as well just where this sample comes from. I figured if it were a sampled preset, the OP would probably name it, but who knows. Perhaps it was dragged in from the studio One sample loops, but again, why not just specify the sample name. We could also check that. So it's likely an imported sample, but anything is possible. Well just have to remain in a holding pattern until there's more info.

 

[Jacelane]

Can you let is know the exact name of the sample/preset and even what library it came from. If its from a Studio One Soundset that is. We can then load it up and see what might be going on. Velocity many not be being routed to the amp volume in Impact XT.

Outrun - Synthwave by Ghosthack - Any sample from this pack

 

[Jacelane]

If the sample isn't changing in volume in Impact XT, but does so in Sample One with Amp enabled, it's likely an envelope setting. Try the different AHD settings in Impact. Particularly keeping A (attack) down, and moving H and D around (hold & release). Otherwise, the sample is only acting and on Amp which encompasses ADSR being switched on or off, along with its settings.

I tried every combination and nothing worked unfortunately.

It also might pay to check the device or controller that you're triggering the sample from, and that it's not set to full on velocity. That might be overriden when using Sample One's Amp on setting.

Im loading them into the pad sometimes my midi controller isn't even on.

There is also the outside chance the patch, that the sample has some velocity limits.

Alao, and very helpful would be if you could specify the sample so that I could check and verify. Thanks.

Ountrun - Synthwave by ghosthack but if that was the case why is it working fine with sample on XT and not Impact XT?

 

[Jacelane]

Yes you did and its a good question too. I thought it good to start with Studio One Soundset? then Patch name. Sample is a third name. We may or not have that library too but its a good start. But if its a random sample imported into Impact then I have done this here. This control as pointed out sets the amount of velocity control. It actually defaulted to that. But check this for a fully clockwise setting gives you the most range. I tested this with recording a part, changing velocities and that all worked correctly.

Tried this and nothing happened.

 

[Jemusic]

I just downloaded the free Ghosthack Synthwave sound set. When I drag the sounds onto Impact XT pads I am getting full velocity response from my controller. It records and plays back all velocities. Adjusting velocities in the piano roll editor changes volume levels.

Make sure you have the right pad selected. Does the velocity control down on the bottom right effect the response.

 

[Jacelane]

I just downloaded the free Ghosthack Synthwave sound set. When I drag the sounds onto Impact XT pads I am getting full velocity response from my controller. It records and plays back all velocities. Adjusting velocities in the piano roll editor changes volume levels.

Make sure you have the right pad selected. Does the velocity control down on the bottom right effect the response.

I'm so frustrated right now. I've been dealing with this for so long. I thought it was normal. So...I've been working out of a template that I created maybe Studio one 5? not sure. I'm currently on S16 pro. I just did a blank Impact XT and everything is working fine, but in my template, it does not.

When I drag a new impact XT over the one I have in my template, it still doesn't work, but when I create a new instance even IN my template it works fine. I don't see any difference in any settings. The only thing that I'm noticing is that the velocity bar at the bottom is hugging the wall to the left regularly in my template. But ugh it is a bit further out on the new Impact XT not sure if that means anything.

 

[Jacelane]

Ok I figured it out. open the inspector tab and put velocity from 127 to 0. Problem solved.

 

[Trucky]

Glad you figured it out.

As a test, I downloaded the same "Ghosthack - Essential Sounds" soundset that @Jemusic used and velocity worked as expected for me in Impact XT.

Another settings difference in your 2 screenshots was the Start Time which explains the offset...

 

[lokeyfly]

Ok I figured it out. open the inspector tab and put velocity from 127 to 0. Problem solved.

Good Jacelane, and thanks for notifying us of your fix and findings. That really does help others if they happen upon a similar issue. Rarely will I load any free soundsets onto my PC, particularly lately, as I'm approaching some near high HD usage on my C drive. So big thanks to Jemusic and Trucky for doing that with following up. Note Truckys starting affecting your offset.

 

[Jemusic]

That value in the Velocity box in the inspector is added to whatever incoming velocities are being sent to Studio One. So if it was 127 then yes that is the reason it was slamming at full volume the whole time. It does help in some situations. Except that adding 127 is a little too much! You can also set this to negative values as well thereby lowering incoming velocities too. eg playing a felt piano software instrument very softly.

A setting of 0 means the velocity is unchanged for the recording. This depends on your controllers velocity curve. It's worth playing around a bit with your controllers velocity curve options (if you can adjust them that is) in order to get it right to suit your playing style. There is usually a sweet spot which that will be set just right and the Velocity value can be left mostly at 0 in the inspector.

 

[lokeyfly]

Agreed, the 127 velocity in the Inspector would have buried each note to a maximum level. Leave them typically in each inspector at zero Jacelane, unless you have that certain controller or group of sample(s) require that to be offset.

FWIW, my Atom SQ requires a setting of about 20 to 40, because piano type playing on it is just not active enough. It's really best at zero for percussion or step sequencing.