Studio One - Scripting API

[Mako]

Is there a way to request/receive access to the scripting API in Studio One? I would like to be able to build extensions like a tool to manipulate the clip gain envelope, for example. It seems the things I want to do can't be done with the current command macros. Thanks

 

[Stuart Welwood]

The only place that I have seen code is gotten to by pressing the Editor button in Presence. The user is then asked for confirmation to create a new program. The interface changes to one that looks like it was designed to manage the program. (I'm guessing.) It has a Script button that reveals the following code:

function onInit ()
{
}

function onNoteOn ()
{
}

function onNoteOff ()
{
}

function onController ()
{
}

function onVoiceStart ()
{
}

function wakeup ()
{
}

Poke the 2nd button on the upper right and you should see some interesting info. I'd like to know more myself.

 

[Davey]

I'd also love a public API, and also more macro information and functionality but I think Presonus are not so interested in that stuff.

The thing is, if they opened that stuff up to the community they would be surprised at how much good stuff people came up with. The same applies to external device definitions. If you give people the power to make their own then pretty much every controller and keyboard will be catered for. Better compatibility, better product.

 

[Lukas]

Yeah, there's no public documentation or official support for scripting.

and also more macro information

What kind of macro information are you looking for?

I tried to cover the most essential details about creating macros in this video...

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Accept third party cookies

...and in my macro / command arguments documentation:

Macro Documentation | Studio One Toolbox

Studio One Toolbox - Free online tools and scripting add-ons for Studio One users. Our Tutorial Database includes more than 500 free Studio One video tutorials!

s1toolbox.com

 

[Mako]

Is the scripting exposed somewhere in the app and just not official and documented? If its exposed I am sure I can figure out the things I want to do I don't think they are too crazy

 

[Trucky]

Is there a way to request/receive access to the scripting API in Studio One?

Here's the site where PreSonus developers check for this type of request or question...

Studio One Feature Requests

 

[Vocalpoint]

Is the scripting exposed somewhere in the app and just not official and documented?

My understanding is the API is internal and intended for Presonus development staff.

Probably TONS of documentation on it too - but none available to the public.

VP

 

[BobF]

My understanding is the API is internal and intended for Presonus development staff.

Probably TONS of documentation on it too - but none available to the public.

VP

Imagine the support load if it were to be made public

 

[Vocalpoint]

Imagine the support load if it were to be made public

Please no. This is the primary reason it is internal - and best left for the lab.

VP

 

[Cypher]

let people register as developers and limit support for them. they would all be fine.
Keeping stuff like this classified makes people switch to other DAWS, where their needs can be adressed.
These artificial limitations are dated and frustrating.

 

[Vocalpoint]

let people register as developers and limit support for them. they would all be fine.
Keeping stuff like this classified makes people switch to other DAWS, where their needs can be adressed.
These artificial limitations are dated and frustrating.

Keeping stuff like this "classified" is up to Presonus. Not the user community.

And since when is this a limitation? Why not just use the program and create some music?

VP

 

[Cypher]

Since when it is a limitation that you can't use software they way you want?
Why limit people in their workflow and limit them in creating enhancements?

Why do you think Ableton and especially Max 4 Live is so popular?

 

[Lukas]

Since when it is a limitation that you can't use software they way you want?

Which exact features are you missing?

 

[Vocalpoint]

Since when it is a limitation that you can't use software they way you want?

Since when is even discussing a technology that is not for end users eyes - a limitation?

Just because you bought a license - doesn't make you a developer or allow you access to developer resources.

I AM a developer and I am not slighted by the fact that I can't have access. I will let Presonus deliver the goods - if/when they are ready to.

Why limit people in their workflow and limit them in creating enhancements?

Why do you think Ableton and especially Max 4 Live is so popular?

Who is limited? And if you legitimately believe you are limited - why do you use S1?

Maybe its time to get on over to Ableton - where you can do some real damage?

VP

 

[Cypher]

"just leave if you don't like it here" ... what a great mentality

Maybe we just try to use criticism as a chance of improvement.
if you are happy, good for you!
Doesn't mean there's no room for changes

 

[Lukas]

Let's please keep the tone here respectful. It's clear there’s genuine interest in user scripting. At this point, however, user scripting in Studio One has not been officially announced or confirmed.

In the meantime, what you can do is share specific feature requests that could improve workflows. Concrete ideas are more likely to be implemented soon.

Thanks for keeping this discussion constructive.

 

[Vocalpoint]

"just leave if you don't like it here" ... what a great mentality

Just remember - you brought up Ableton.

If you have ideas for improvement for Studio One - please list them or submit a feature request.

But if your idea of “improvements” is expected access to an internal API that the vendor has never been advertised (or even officially acknowledged) can't really help you there. It is what is it.

This really has nothing to do with making S1 better. Feature requests via the standard channels do that.

VP

 

[Mako]

I put in a request at presonus anyone can go in there and upvote it.

The main thing I would like to do in a script is take a selected range and insert -infinity key frames on the clip gain envelope to mute a section of audio without breaking it into events. This just matches my thinking better when working in a DAW. This seems like a basic capability DAWs I used a long time ago had it (Cakewalk, lol) where you could mute directly on the audio waveform. For sure Studio One is better in many, many ways than the old DAWs and fits my workflow well for a lot of other operations. So not really looking to switch to another DAW.

I am a dev I have built vsts for personal use. My day job is developing pro AV software for live production.

 

[Lukas]

The main thing I would like to do in a script is take a selected range and insert -infinity key frames on the clip gain envelope to mute a section of audio without breaking it into events.

You wouldn't have any luck because scripting can't do this. Editing automation is not something Studio One scripting currently provides access to.

 

[Stuart Welwood]

Cakewalk had their CAL scripts, which were quite useful in making custom functions to extend the app's abilities. I have over 800 of them. CW dealt with the issue by providing documentation without support.

I always found the documentation more than adequate for my needs, but I was a senior software engineer for decades (I'm 72.) Scripting languages tend to be somewhat simpler than universal computing languages, and CW's certainly was. I have no idea what Presonus would have in mind, but it would likely be something like what I found just by poking around. The attached file gives us a good start.