Wave array bad behavior

[kortezzzz]

Hi,
I'v released a new drum sampler lately

http://www.tornsub.com/ProductDetails.aspx?pid=4

and it works just fine, but having one major problem that seems hard to resolve:

I'm using 20 sample slots which means 20 wave array primitives that load a new sample at once on preset change to create a new drumkit. I understand that to do it properly,
I should first remove the old samples from the memory (clear the array) and then, load the new ones. I use timers for this, but the problem is that sometimes, when a preset changes, i got harshing popping and clicking sound (something like bad speakers effect). Thought maybe its due to the fact that the wave array primitives need some more time to clear their arrays before loading the new waves, so increased the timers delay but it hadn't resolved the problem. Note that the bad audio behavior comes and goes. For instance, it comes after 2-3 preset changes and disappear after another 2-3 preset changes. Really strange...

Does anyone knows how long it takes to the wave array primitives to clear their array before they are ready to load a new samples?
Or probably the problem is somewhere else? A bug maybe?

[tulamide]

Have you already tried the "Clear Audio" prim? I just quote one line from the description: "It is also needed in some occasions to clear the audio buffers when changing settings or presets."

[kortezzzz]

Thanks for the suggestion, tulamide. didn't think about that. I'll try and report soon.

[kortezzzz]

Unfortunately, the "clear audio" prim. hadn't changed a lot. Maybe switching 20 samples at once is just to much for a FS schematic? Maybe it's because of lack of multicore support? So far,took me almost a week to find a solution for that. Another interesting thing: its happens with any multisample player version ever posted in SM\FS forums as well, not only in my schematic. Each of my kits weigh aprox. 10-12 mb, make me wondering what gonna happen if one try to work with bigger samples.

[Tronic]

To delete, and load data into memory, the time it takes is not fixed,
think you should run a check by taking the trig from wave array, to be sure that it is in memory.
 
I do not know if there have been updates with internal release since the last version,
and it has lots of bugs in the audio section and especially with the preset manager.

So who knows.

[kortezzzz]

An update:

Seems like there is a specific problem with wave array +asio4all driver combination. Never thought that a driver may cause issues, as never had driver issues using samplers or anything and my small laptop allways responded well with asio4all. but for some reason the asio4all doesn't likes fs's wave array prim...
Tried my vst on other machines with pro audio interfaces and solid drivers and no problem occured. Anyway thanks for trying helping, guys.