Building a piano in ST3 - how do I assign velocity...?

[danshousestudio]

When importing a sample into ST2, part of the the file name would determine what velocity would trigger the sample. Using a "V" followed by the velocity value did the trick.

For example, "C1 v85.wav" would be triggered by velocities up to 85.

But the instructions in the ST3 manual don't mention anything about setting velocity levels - nor does the video tutorial. Is this function now beyond our reach?

If worse comes to worse, I can simply set the instrument up in ST2, and then import that into ST3. But I hope that isn't necessary!

[DarkStar]

I don't think that ST3 Import Samples supports velocity splits. It might be on the "to do" list.

Time to break out ST2.5

[danshousestudio]

Yeesh. Too bad. Wasn't expecting a new Sample Tank with lesser capability than the previous.

I've got a big piano sample library, too big to cram into a 32 bit application. Was hoping ST3 could be the answer!

[Peter_IK]

Hi, I asked the SampleTank 3 project manager and he says this is possible:

Redacted

[danshousestudio]

Thank you, Peter!! Good news. In ST2, a space was critical. Now it's an underscore - great to know!!

[DarkStar]

^^^
That's good news; Peter, can you please get that added to the User Manual?

So it is similar to ST2.5 with added _ velocity prefixes?

[danshousestudio]

OK, I tried this, and I cannot load samples named in this manner. ST 3 gives me the error...

"Missing note name. Please make sure that your sample file names begin with the note name. For example, C1.aif or C1 Electric Bass.aif with a space after the note name."

My note names are formatted thus...

C1_v127.wav

ST3 is not recognizing the names. And when I asked support about it, I was told that importing does NOT support velocities. After this latest efforts, I am more inclined to believe the response I got from support!

Peter IK - are you sure you got the right info?

[Peter_IK]

I got it straight from the product manager, so I would think that's the correct information. I will check with him and with support.

[danshousestudio]

Thanks, Peter! Any chance I could speak with this project manager directly...?

I have built a piano sample library that I was planning on distributing using Sample Tank. The 32 bit ST2 couldn't take the large quantity of data included in my sample set, so I had been planning on using ST3's 64 bit plugin, which I'd been told could support the large amount of data. I had also been planning on using key release samples, as I'd been told this would be a feature in ST3.

But if user-imported samples can't include velocity values, ST3 is useless for what I'm trying to do. And, according to support, user-imported samples can't take advantage of the key release feature either.

This is bad news for what I'd been trying to accomplish with ST! But I'd love to get in direct touch with someone who could clear up this stuff for me with some certainty.

[danshousestudio]

Darkstar - I'd be happy to build the instrument in 2.5, but there's a 2 gig limit to the size of the sample set!

[Peter_IK]

I've forwarded the information to him and support and it should work as he described so they are working on it.

[danshousestudio]

Thank you, Peter!!

[Peter_IK]

I have redacted the step-by-step process to avoid confusion. We did indeed find an issue with the import system that is being addressed and I will share news on this when I have more to share. Thank you for your patience.

[danshousestudio]

Good news, Peter! Looking forward to a solution to the issue!

[danshousestudio]

Just checking in to see if there's been any progress on this issue.

Thanks!