Question

Please provide a documentation for the scripting API functionality. If people outside Presonus could work on studio one, this would push the development of features, especially that of niche requests. 

As suggested before, I would combine this with a marketplace system where people can sell their expansions:

http://answers.presonus.com/35202/studio-one-as-framework-with-marketplace?show=35202#q35202

Answer 1

Are you a fan of the way REAPER does this? Because I was a long time REAPER user and I honestly hated their system. REAPER to me is a cautionary tale of how this is a recipe for instability, inconsistency, and wasted time. I think scripting is better for tasks that are basically macros with repeat cycles, while loops, etc.

Answer 2

I haven't used Reaper, but there are countless other examples in the software world where this works. There are many ways how this can be done. A good architecture, encapsulation, standards and handling of exceptions can deal with issues like crashes. Just because a script in a custom midi editor has a bug, it does not mean the whole DAW has to crash.

Then there is the other point I mentioned in the post: The marketplace. It is one thing if hobbyists make extensions vs companies that focus all their resources on a product. They will want to avoid that their product crashes because otherwise, no one will buy it. When you buy a third party extension you will also get the updates from the marketplace system.

So I don't see a problem why this shouldn't work.