i think there should be one caveat in regards to multithreaded objects in general, and that is you can no longer rely on the patch depth--right to left execution order..had to make some slight changes in file loading externals and move around some counters, etc, so that things would work again...but of course the benefit outweighs the minor hassle...just think there should be fair warning of that, assuming the threaded soundfiler made the default...
well, i never thought about the excecution order when writing the new soundfiler ... but you are right, i should add a warning.
anyway, since the soundfiler _has_ to work asyncronously to avoid dropouts, there is no other way to solve this that makes sense ...
i'm curious if anyone has tried to compile it on osx ... i'd be glad to get some feedback...
cheers ... tim