I would not want to appear too lazy to not look in the source code or read this thread again from the start, but since I am admittedly lazy... Is this library designed to only process stereo signals? (I have it working for that but my concern is processing mono efficiently as well as processing surround audio in the future without having to manage several instances of a filter class) I can't see any obvious way to set the number of channels used, at least in the DSP::Filter base class...
thevinn wrote:A filter can be instantiated to work with any number of channels from 1 and up.
Thanks. So the number of channels is in the template parameters. That, I suppose, makes it impossible to support an arbitrary number of channels dynamically at runtime...? I know, that's not a very typical use case, but I'd like to be prepared for all sorts of weird things. Anyway, not a big deal at the moment, my app currently only supports stereo operation at most anyway.
It should have been obvious the number of channels is in the template parameters, but your library is like Logic (the app). If you don't constantly (re)learn and use it, it's easy to forget how things work.
XCode 4 projects with targets for Mac OS 32/64, iOS, and iOS simulators.
Visual Studio 2010 projects with both 32 and 64 bit platforms.
Shared settings files (.xcconfig for XCode 4 and .props for Visual Studio).
Folders were reorganized so each module is self contained (Juce, DSP Filters static library, and DSP Filters demo application).
Would a kind soul(s) please get the sources and see if it builds correctly for either MacOS, iOS, Windows, or all three? Of course it works on my machine but I would like to know that what I put up there doesn't have any issues before I move on.
No resource editor.
No built-in MFC support.
No built-in ATL support.
No profiling support.
No built-in x64 compiler.
No support for OpenMP.
No support for add-ins or IDE macros.
No debug memory or registers window and only one watch window.
Don't know if that's all, but I'm pretty confident that for a simple DSP lib (not trying to say that your lib is simple.... you get the idea) anything you do with the Full version, you can do with the Express version....except the 64bit thing.
it does have x64 capability, you just need to install it separately and there is a registry "hack" involved.
ideally the only difference in the project files should be that they have the target set differently for the x64 versions. the lib names, configuration and other properties should be identical across targets.
msvc has capability to do this - it allows you to specify linker directories and header directories based upon target, of course. this is obviously absolutely necessary. due to that, the project files can be identical.