Writing a script for Studio One?

[Housemus]

You cannot assume that Fender is 'forbidding' scripting if they haven't released documentation or vice versa. There is a history in Studio One of script packages and nobody got 'sued' back in the day from StudioX, the Color Toolbar and the tools from Lukas.

Maybe Fender wants power users to make custom script packages, but haven't released documentation yet. Good to see the documentation on Github. Fender should encourage involvement. Look at Max for life or Reaper. There are creative users out there. Use them. My 2 cts.

 

[Gray Wolf]

Well, this has gone off the rails.

If the developers wanted to forbid 3rd party scripts, they could very easily do that by only allowing their own script packages to load and blocking everyone elses. That would be a trivial thing for them to do.

After many years of being aware of third party scripts and not doing that, it's perfectly reasonable to assume that they're ok with it.

 

[Gray Wolf]

That's generated code, I don't know any programming languages at all. This is all speculative. If there's something that needs correcting, we depend on people like yourself to point it out. I myself will learn as I go.

If you see anything out of place, please don't hesitate to correct it so we can continue building proper documentation. If you have suggestions on my approach, let me know.

Ok. While prototyping is useful in some cases, and Lukas can explain all of that better that I can, it's unnecessary in basic script functions. My earlier code example is more typical.

 

[Andy_P]

Are the scripts around legally any different than the ''Color Toolbar'' which at one point probably all of us used?

 

[Lukas]

Are the scripts around legally any different than the ''Color Toolbar'' which at one point probably all of us used?

My Studio Pro scripting extensions are developed in cooperation with PreSonus / Fender. That’s why they’re signed and copy-protected via Studio Pro’s activation process.

 

[Andy_P]

Hey Lukas!
I know about yours and them being co developed
I meant the current ones that popped up around forums, like strummer script etc.

 

[Vocalpoint]

There is a history in Studio One of script packages and nobody got 'sued' back in the day from StudioX, the Color Toolbar and the tools from Lukas.

"Lukas: My Studio Pro scripting extensions are developed in cooperation with PreSonus / Fender. That’s why they’re signed and copy-protected via Studio Pro’s activation process."

There is a vast chasm of difference in what Lukas does (and has been permitted to do by Fender) VS a bunch of users trying to reverse engineer skins, guessing what the API contains and so on.

Lukas (presumably) has access to the real API where all the rest of this - is simply throwing something against a wall and hoping it sticks.

VP

 

[Crossinger]

where all the rest of this - is simply throwing something against a wall and hoping it sticks.

ColorToolbar sticks fairly well and has filled a gap.

 

[Vocalpoint]

ColorToolbar sticks fairly well and has filled a gap.

Of course - but it's clear (to me anyway) that Color Toolbar was coded with discrete and VERY specific (most likely - real) API knowledge from wayyyyy back in the day.

Not some guy poking around in random XML files hoping to score a few nuggets of knowledge from an unpublished API.

VP

 

[Housemus]

"Lukas: My Studio Pro scripting extensions are developed in cooperation with PreSonus / Fender. That’s why they’re signed and copy-protected via Studio Pro’s activation process."

There is a vast chasm of difference in what Lukas does (and has been permitted to do by Fender) VS a bunch of users trying to reverse engineer skins, guessing what the API contains and so on.

Lukas (presumably) has access to the real API where all the rest of this - is simply throwing something against a wall and hoping it sticks.

VP

As been said by Gray Wolf before. If scripting was forbidden, development would have blocked this route easily. If it really annoys you that 'some guy'/creative users make packages or publish info about the API on GitHub, just warn Fender.

 

[Vocalpoint]

As been said by Gray Wolf before. If scripting was forbidden, development would have blocked this route easily. If it really annoys you that 'some guy'/creative users make packages or publish info about the API on GitHub, just warn Fender.

No need to "block" something that has never been made publicly available and that you know nothing about.

And no where did I say anything was "forbidden". If this bugs Fender enough to care - I am sure they will take care of it in short order

You guys want to hack around and have fun - by all means - have at it.

VP

 

[Navar]

And no where did I say anything was "forbidden". If this bugs Fender enough to care - I am sure they will take care of it in short order

Depends on how many support requests they get, involving those kind of scripts. I personally only trust Lukas in this case.
I find it sad too that there is no official documentation, I have the ideas and knowledge to do some stuff that would make my life easier but I don't have any desire to reverse something just to waste time.
And I find it very understandable, if they would make it kinda official they have an instant support problem. Even if they would say that they don't support or debug it. People will ask and with every little error, the support would have to make sure, that there is no script involved. Sounds like a lot of pain to me.

 

[Housemus]

No need to "block" something that has never been made publicly available and that you know nothing about.

And no where did I say anything was "forbidden". If this bugs Fender enough to care - I am sure they will take care of it in short order

You guys want to hack around and have fun - by all means - have at it.

VP

I am not a guy and not a hacker . I just want to enjoy good extensions by creative (power) users or 'licensed and permitted' external developers. 'Hack around' is negative way of describing creative user engagement.

 

[Vocalpoint]

Depends on how many support requests they get, involving those kind of scripts.

Highly likely that ANY support ticket sent mentioning an undocumented scripting environment - would essentially be deleted.

I personally only trust Lukas in this case.

That is because Lukas has worked for Presonus, know the internals and most importantly - has the full blessing (and backing) of the actual dev team (and presumably access to the real API). His stuff is high-end, well tested and very well done.

I find it sad too that there is no official documentation, I have the ideas and knowledge to do some stuff that would make my life easier but I don't have any desire to reverse something just to waste time.

Probably a ton of unknown reasons why this remains internal. That is their call and has been this way since 2009.

If they would make it kinda official they have an instant support problem.

It would be a disaster for support - if the actual API was out there and anyone could code anything - with no Q&A, no knowledge base and no experience with it. Pretty sure everyone can see why things are the way they are

VP

 

[Vocalpoint]

I am not a guy and not a hacker . I just want to enjoy good extensions by creative (power) users or 'licensed and permitted' external developers. 'Hack around' is negative way of describing creative user engagement.

Sorry for the verbiage - but do not sugar coat this by making it sound like Fender has somehow invited the "creative community" into it's world and is actively promoting folks to kick off some sort of "Extension-Fest" to enhance the overall Studio Pro experience.

If no one (outside of Fender development employees and insiders like Lukas) has access to (or knowledge of) the actual internal API - my apologies but I really do not have a better word for this - except hacking.

VP

 

[Housemus]

Sorry for the verbiage - but do not sugar coat this by making it sound like Fender has somehow invited the "creative community" into it's world and is actively promoting folks to kick off some sort of "extension-fest" project to enhance the overall Studio Pro experience.

If no one (outside of Fender development employees and insiders like Lukas) has access to (or knowledge of) the actual internal API - I really do not have a better word for this - except hacking.

VP

I call it enthousiastic extending of the functionality. You are a bit hyperbolic with your 'extension fest' and 'disaster for support''

We will see what Fender will do about this 'problem/opportunity'. They don't strike me as a company that likes user involvement (especially the last couple of years)

 

[Vocalpoint]

We will see what Fender will do about this 'problem/opportunity'.

Well - I cannot see how this translates at all to a "problem" and even less so to an "opportunity"

And - pretty sure we have already witnessed exactly what Presonus/Fender intends to do about this - since 2009.

Nothing.

VP

 

[BobF]

Is this horse dead yet?

 

[Housemus]

Is this horse dead yet?

The horse is quite high. It will take some time to get down

 

[Vocalpoint]

Is this horse dead yet?

Only you have the power @BobF

Please make it so.

VP