I am starting to dive into SOUL now (bit late to the party I guess :). and got a few questions after poking around with the example project and the docs.
- The demo project expects the soul .dll to be either at the desktop (lol), the user’s home directory (double lol) or the app’s parent directory (better, but not universal). I know we’re far from a production environment but shouldn’t there be already a sensitive default where people can expect the soul binary to be like any other dynamic lib (C:\Windows\System32 and /usr/local/lib for example)? Ideally once this platform has thrived you can just expect it to be on an audio computer like eg. runtime32.dll but if you don’t specify this ideal location soon, everybody and is dog will install it to arbitrary locations and the end user will end up with multiple versions of this dynamic lib file.
- I skimmed the Syntax Guide but I didn’t see a mechanism for including other soul files ("#include “MyProcessorCollection.soul”). Is this on the roadmap?
- Is there any mechanism to tell a SOUL Processor to execute the inner loop in a fixed block size (or at least fire a callback every 32 samples to eg. update filter coefficients)? I know you’ve stated that you’re trying to follow the paradigm that the algorithm shouldn’t care about block processing, but there are some situations (like above) where you need to have control over this aspect.