Writing Plugins

Question

Does anyone know if its possible to write a plugin for Logic that allows exporting of audio and midi data in a fixed format, to a fixed file-naming structure?
Thanks in advance!

Answer 1

So, looking at the blurb, you can:
It contains a suite of utilities - the lack of structure of these utilities exists because I wrote the software as Automator Actions. Automator already has a collection of utilities, as well as some of the other apps that exist on your machine. I was not interested in reinventing the wheel (or taking the time) so Accelerando's utilities are either unique or developments in progress. Some of them tackle user interaction problems, some filesystem problems, and so on. The applications ( or uses ) appear like a mixed bag since it is fitting into Automator's environment - when it is an extension of this environment.
Has anyone got some practical applications for Accelerando they can share? What sort of things are you doing with it, and how's it making your workflows easier?
Well - Automator and the apps on your computer include many actions* already so definitely use those in any workflow*. The applications are very broad indeed - I tried for many things with the software, easy to use and configure - fast and efficient to operate. Much of the software is designed to be at the ready and used interactively - as opposed to much of the Automator uses people know. For example, 10 key commands can be performed by Accelerando very quickly so you would just create a workflow of this frequently used 10 key command sequence, save it, and run it whenever you need to use it. Key Commands aren't the only option, there's actually a lot more to it. As you work, you realize the patterns you use in your workflow and the things you do not do out of time constraints or repetition - many of these can be simplified by scripting.
Seeing as the examples for Logic include stuff like sending a key command, I'm presuming it's basically some kind of scripting top-end to remotely control apps (a bit like Applescript).
Well - it is a scripting top-end, but it does not require scripting experience - all configuration is handled by the UI. AppleScript requires the user to know the applescript syntax, or language. Even though applescript's language is relatively user friendly, it is still a barrier for many potential users who could benefit from it. So that element has been removed. No scripting experience is required - no language needs to be learned, so it allows many users to script in ways many would only imagine. Furthermore, the tasks (of the actions) are straightforward, so the user really only needs to learn the concepts of using Automator, the actions they need to use, and other software which is involved. In that case, they only need to learn how to put the legos together for their purpose. Power users will typically benefit the most from it, since they have a deep understanding of the software they wish to control (Logic in this case), they will have the patterns and objectives for many complex tasks already memorized.
Does it come with useful scripts, or is it purely a development environment for doing your own stuff?
I have a collection of conceptual workflows, but the uses for the software are too broad for me to personally create great, useful workflows which could benefit any user so much so that they will not need to learn to use the software. For that reason, 'useful scripts' are omitted and conceptual workflows are available.
I guess I could download and digest the manual, but it would be nice to hear about any successes...
There is no problem downloading and installing the software, but the actions will not perform without authorization. So, you could download, install, see how the pieces all fit together in Automator and get some ideas for the capabilities. Remember, it is designed to be available in an interactive sense, so a sequence of a few key commands and menu selection (for example) will require less time to invoke and run (assuming it is already configured) than doing it manually - the added benefits are that you don't have to enter them yourself and that the accuracy is better (at least, in my case : ^)
Cheers,
J
*A workflow is an Automator document, which contains one or many actions. Actions are software which perform a simple or specific task. Actions may be freely configured/ordered for easily configuration of complex workflows - much of the additional work/configuration can be removed from the interface, so scripting in this way is easy to use, for people who desire to script or automate.