Ok, but it's not clear to me how we will distinguish between a faulty
drum-sample that we only want to attempt to load once and one that we have
since fixed and would like to reload. This is assuming (reload) is not a
option there as (reload) will attempt to reload everything and presumably
clear the cache.
sorry, i don't know fluxa very well, so i was not aware of (reload). this could fix it. although it seems to me there's a 2-level cache. fluxus caches the samples in the fluxa.ss module, these are affected by (reload). the fluxa server also caches the samples in AsyncSampleLoader.cpp.

Quite a few complicated questions for such a small synth program! :-)
yes, i feel a bit confused already. probably it's better if i stick to the visual side of fluxus :).

best,
gabor

Reply via email to