I've got to say that RackAFX is an awesome refactoring of and re-bridging back to industry standard audio plugin API's. It is a much more straightforward and easy to learn equivalent API. I know that your motivation, as a teacher, was to facilitate students and readers of your books (really great pedagogically, by the way) in focusing on DSP and Synth building via your terrific prototyping workbench. But in the process, I think you're also developing a better way to create and deploy audio plugins in general than what is currently in use.
As an investment in the future, I am wondering if you might start promoting the RackAFX API as a plugin interface (independent of VST or AU) for use in open source client software such as new composition tools perhaps on tablets and phones in addition to desktop DAWs. Do you think you might post to the forum or write an article or online appendix to the books on your thoughts about best practices for using our RackAFX plugins in client programs we might attempt down the road?
Beyond how to capture and present RackAFX GUI events and values to the plugin code, the rest seems so straightforward to anyone knowing how to interact with the OS's file system and its midi and audio drivers.
Thanks again for the books and software. The books are the best yet that I've read on DSP and synth building not to mention explaining the VST and AU API's. You've obviously explained these concepts many times over until it is just right.
Thanks for the comments about the books and RackAFX. All of them have been in development for a long time. The FX book is actually very literally based on my class notes from teaching DSP/Signal Processing/PlugIns back in the 1990's and I think it reads that way too. The synth book is definitely deeper (and taking on 3 APIs was a challenge) and more intense.
I had never thought of releasing the client-side API for RackAFX, but I guess it makes some sense, especially for programs like Audacity and Wavosaur (and who knows, maybe someone in the big-leagues like Sonar would see the addition of RAFX support as a way to both differentiate their product in the marketplace while also getting more entrenched in Academic use?).
The good news is that the client-side API is just as simple as the plugin-side API. I don't think you can find an easier plugin to host than RAFX, so yeah I might try to spend some time working on a White Paper/API for client implementation as well as provide some sample client code. Not sure what the timeline will be on that, but thanks for the suggestion - could lead to something really cool with the open-source DAWs and beyond...
All the best,
Most Users Ever Online: 152
Currently Browsing this Page:
Guest Posters: 1
Newest Members:channa, bvaccaro, HCassell, Max, Sim1, Chris Wade-Evans, Marlow, kcmixs2, DanieleR, jimjulian
Moderators: W Pirkle: 391
Administrators: Tom: 74, JD Young: 80, Will Pirkle: 0, W Pirkle: 391