Purpose of SFZ?

[MDMA]

Why is there an sfz multi sample advance if it doesn't work properlly?

I've looked everywere and found a lot of unanswered questions!!!

I load a wav sample into the player, choose a key center and it works fine but when I choose to add more samples it completly ignores them.

Are there any solutions out there or proper sfz integration is simply not possible?

Thanks in advance!

[nix]

U can make ur own multi-sampling instrument with velocity layers,
but I don't know how capable the .sfz function is.
It may be broken.
That's like the latest thing we have got,
and devs r on FlowStone.
If your object is multi-sampling with velocity layers-
I can help, but I can't help off the bat with a .sfz loader.

[MDMA]

U can make ur own multi-sampling instrument with velocity layers,
but I don't know how capable the .sfz function is.
It may be broken.
That's like the latest thing we have got,
and devs r on FlowStone.
If your object is multi-sampling with velocity layers-
I can help, but I can't help off the bat with a .sfz loader.

Oh, right, thanks for replying.
Multi sampling is a good option 2, being able to assign samples per key and determine their range as well as creating velocity layers!

I'd be very thankfull if you could point me in the right direction, yes.

[nix]

viewtopic.php?f=10&t=10655&hilit=multi+sampler

Here in this thread is a multi-sampler I built ages ago.
You may have to tinker with it to get it going, but I should be here if u get stuck.

We can implement velocity layers,
but our problem is- how much RAM we r sucking.

If the samples r short we might be able to get by--
grr... we need 64-bit really

The main component is the wave array.
If we make velocity too, I imagine we would use that.

We can of course use the keyboard's velocity on single samples-
that would be less RAM intensive

I am going to make sitar, Casio mt-40 and fujitone IIIb sample libraries sometime 8D

[MDMA]

http://synthmaker.co.uk/forum/viewtopic.php?f=10&t=10655&hilit=multi+sampler

Here in this thread is a multi-sampler I built ages ago.
You may have to tinker with it to get it going, but I should be here if u get stuck.

We can implement velocity layers,
but our problem is- how much RAM we r sucking.

If the samples r short we might be able to get by--
grr... we need 64-bit really

The main component is the wave array.
If we make velocity too, I imagine we would use that.

We can of course use the keyboard's velocity on single samples-
that would be less RAM intensive

I am going to make sitar, Casio mt-40 and fujitone IIIb sample libraries sometime 8D

Thanks a lot Nix, this gives me something to mess about with when I finish my current project as I decided not to implement this type of system on it, at least not on this first version.

I'll be coming back to this topic then!

Peace!!!

[CoreStyler]

with disk streaming, without the need of loading into schematic (memory), will be possilble to create any kind of instruments. For example, inclduding array of mem into a text... velocity, volume etc.
But, loading one single array of a wave goes out of mem. If disk streaming was added, will be possible (i think) to get an index of a text file without opening the whole data into the schematic/plugin.

My thread:
viewtopic.php?f=12&t=11229

[MDMA]

with disk streaming, without the need of loading into schematic (memory), will be possilble to create any kind of instruments. For example, inclduding array of mem into a text... velocity, volume etc.
But, loading one single array of a wave goes out of mem. If disk streaming was added, will be possible (i think) to get an index of a text file without opening the whole data into the schematic/plugin.

My thread:
viewtopic.php?f=12&t=11229

Thanks, it sounds like we will need to wait for better integratioin then.