Multi Sampler Sfz loading

[SampleScience]

Does it work? When I try to load my own Sfz or any other Sfz I get nothing, just silence. Any idea why?

Is there any Sfz editor that will work better with the Multi Sampler in Flowstone? I'm trying to build a sample based synth but I have a hard time figuring it out.

Thanks!

[kortezzzz]

Hi,

Here is a working version of the multisampler. Sometimes, the multisampler in Flowstone can't read some wav. files for some reason, so maybe that's your problem. Try my uploaded version and report.

cheers!

[SampleScience]

Hi,

Here is a working version of the multisampler. Sometimes, the multisampler in Flowstone can't read some wav. files for some reason, so maybe that's your problem. Try my uploaded version and report.

cheers!

Thanks! I'm going to try it out, it would be cool to create a free Sfz player in Flowstone with more advanced controls.

[SampleScience]

The Sfz player in Flowstone is really buggy, sometime it works, sometime it doesn't. When it does, it won't always play the wav as it should, sad. And I'm not even talking about the cpu efficiency, I get cpu spikes quite easily with it. Hopefully, someone will code a better sfz module in Flowstone.

[wlangfor@uoguelph.ca]

The Sfz player in Flowstone is really buggy, sometime it works, sometime it doesn't. When it does, it won't always play the wav as it should, sad. And I'm not even talking about the cpu efficiency, I get cpu spikes quite easily with it. Hopefully, someone will code a better sfz module in Flowstone.

Perhaps the problem is in the array and the wav's could be loaded individually. I'd be willing to try this so that they could still be utilized as if they were an array.

Thankyou to kortezz, I'll look into this file and it should be very educational.

[wlangfor@uoguelph.ca]

This is a great schematic kortezz, I'll try an iron out every bug and repost it.
This is top notch work and it should become a schematic that comes with flowstone.

Interestingly, I tried this and it works with zampler patches 100% of the time. Not though, the trickster edition patches that I'd had strangely enough.

Anyways, you are a driving force in the community here, thanks.

[kortezzzz]

This is a great schematic kortezz, I'll try an iron out every bug and repost it.
This is top notch work and it should become a schematic that comes with flowstone.

Interestingly, I tried this and it works with zampler patches 100% of the time. Not though, the trickster edition patches that I'd had strangely enough.

Anyways, you are a driving force in the community here, thanks.

Thanks wlangfor@uoguelph
This schematic is workable. However, it needs some patch pre-tweaking since not every sfz would work correcrtely, so you should know what you're doing with the text patches. Took me some while to shape it and now, it does work ok with the alfa (older FS versions are too problematic and weak for this one ).

[wlangfor@uoguelph.ca]

This is a great schematic kortezz, I'll try an iron out every bug and repost it.
This is top notch work and it should become a schematic that comes with flowstone.

Interestingly, I tried this and it works with zampler patches 100% of the time. Not though, the trickster edition patches that I'd had strangely enough.

Anyways, you are a driving force in the community here, thanks.

Thanks wlangfor@uoguelph
This schematic is workable. However, it needs some patch pre-tweaking since not every sfz would work correcrtely, so you should know what you're doing with the text patches. Took me some while to shape it and now, it does work ok with the alfa (older FS versions are to problematic and weak for this one ).

Ah, thanks for the tip

[wlangfor@uoguelph.ca]

I noticed if loop becomes the continuous type that memory goes crazy.

I used a method I'd found in an older synthmaker schematic to attach to the mono in out It prevented the bug that occurred when having a large amount of cpu drained. Previous to adding; it stayed at a large sum of cpu use (like 30%) due to voices and instances being loaded into memory I'd assume. But that's only the first step, the second issue is the state of loops also being resolved and staying present in cpu's processes.

There may be a different method required, so as to smooth the tail off. I was thinking a mod could be made of a useful attack and release dsp code example that Trogluddite made. It may be that a db to linear conversion could be utilized, such as Aliasant's db40 to linear conversion code example and then fed to a dsp code which checks for the right number and causes a release to be initiated before the instance of silence. So Trogluddite's attack and release becomes instead release.

But, finally I think of the reality of loop points. Obviously, I felt it would be ideal to program them in by the means of a .sfz file; but in this instance, the loop points are automatically deriven from the sample itself. This is a very time consuming process to add loop points, ideally I think one might surmise that it would be better to work with a larger version of this loop interface, to instead write to a .sfz text file.

I'll be touching on that, in hopes of avoiding loop points from the wave files themselves. Ultimately, it comes down do creating a sampler that not only loads .sfz but allows you to make the patch as well. Grace or Directwave is one of the better for that; but what comes hard to miss is the small size of the interface. Not having the ability to zoom into the wave form image to create the loop points for instance is half the problem.

I'll update when I can with a working example to share.

[wlangfor@uoguelph.ca]

here's a custom version with a supersized sample display. This is just for example so that you see what I mean about a larger screen. That way manually selecting the loop points is feasible. I tried using a method to reduce the cpu load upon processing of delay and attack release of the loop points.



I'd probably have the adsr elsewhere.