DSP Robotics Support

Well... I finished my port (at least a 1.0 version of it, thanks for all of the generous help given here) ... and ... not so unexpected... a good number of people who like it and find it useful are complaining that it's not 64-bit.

I hope the FS developers get around to making a x64 plugin shell at some point. At any rate, here is the result of the port from my VS desktop app to a plugin version. I typically only make things I personally want and then see who else maybe finds it useful.

Over 225 downloads in one day... no donations yet.

Download: Download
Image: http://i.imgur.com/YVLdNmN.png

Side Note: I spent a good bit of time coding (learning how to code) Win API functions for it in Ruby, partly to grab the song name from the running DAW automatically (GetWindowText, it worked great in design and preview mode) with an eye on doing some other things later via the Win API, but learned after the fact that (apparently anyway) the API calls won't work from inside the running plugin shell.

It wasn't a complete waste though, at least I now know how to make API calls if I do a desktop app with it.

Thanks for sharing, S1User. What exactly does your plugin do?

It's a way for audio engineers (which is my primary thing, recording and mixing) to keep track of clients and sessions and billing and contacts in a more efficient way.

I've made similar applications as stand alone Window's apps, which work fine, but having it as a plugin on the master bus is a better approach imo. The idea being that whenever you work with the DAW your contacts and billings and client information is always right there in the daw, on a plugin on the master bus, no need to run another application.

The timer is there to do that other job. It's sometimes the case that sessions get interrupted for reasons having nothing to do with the client so you'd pause the timer in those cases, not charging the client for time when you the operator / engineer are called away for other reasons. When you return to the session, start (un pause) it.

If you don't run sessions or bill people by the hour it has no real practical use.

What I'll be adding going forward is exporting all of the collective data to Excel format, or something that will import directly into Excel, given that people who do that need that collective data for tax purposes. I'll also be adding a way to push a client's mix to a Dropbox folder for mix approvals, given that Dropbox sync is just a local folder, and maybe have the feedback comments from the client show up in the session notes. That latter bit may not be possible without the Win API working from the plugin shell though.

So generally speaking, my development projects related to DAW's aren't musical, they're more doing the necessary offline jobs that most workstation mfg's simply ignore. You can find synths and things everywhere but things like this, housekeeping and/or offline management tools, don't really exist at all as plugins... and FS is a really easy way to push what otherwise might be standalone apps into VST Plugins.

F***n Perfect tool