Scripting in Studio One

[Fidelitymusic]

Edit: Added Scripting API repo link below.

[Fidelitymusic]

Haven't tested on Windows yet, let me know if it works. You can download the .package HERE and follow the installation instructions. Source can be found under: scripts/sources/flam-tool-source

Flam Tool.png

Studio Pro Scripting API Reference: https://github.com/CSources/Studio-Pro- ... -Reference

[Housemus]

Very interesting. I really hope that this API will be extended by the development team. Because there are people with creative ideas out there. Take a look at Max for Live, or the Reaper customization. Also a nice way to get a community involved.

But... Fender is having the 'new features for new markets disease'. Guitarists and starters are in the picture right now. Refinement of included features is out.

[wikter]

Haven't tested on Windows yet, let me know if it works. You can download the .package HERE and follow the installation instructions. Source can be found under: scripts/sources/flam-tool-source

Flam Tool.png

Studio Pro Scripting API Reference: https://github.com/CSources/Studio-Pro- ... -Reference

Thanks for the code and the reference to the "community generated" API reference.
Presonus never wasted a second trying to make it public or open. Thankfully, its community did. Thanks guys!

[wikter]

But... Fender is having the 'new features for new markets disease'. Guitarists and starters are in the picture right now. Refinement of included features is out.

Time to rewrite again the amp simulator tool.
Oh... And it's really funny to see Presence Fender guitar libraries have a real lack of realism. Not even the amp EG is working on those patches, the filters poorly assigned and velocity is just set. Refinements gone.

[Crossinger]

Presonus never wasted a second trying to make it public or open.

If they do, it comes at a cost: Documentation, maintenance, support, in short: responsibility. I understand why they won’t do it.

[wikter]

Presonus never wasted a second trying to make it public or open.

If they do, it comes at a cost: Documentation, maintenance, support, in short: responsibility. I understand why they won’t do it.

Sorry, but it's just LACK of responsibility. They created a protocol, it's not that hard to publish a simple guide with parameters and brief explanations. It's a profesional software, not a toy to be sold in Walmart.

[Vocalpoint Studios]

Sorry, but it's just LACK of responsiveness. They created a protocol, it's not that hard to publish a simple guide with parameters and brief explanations. It's a profesional software, not a toy to be sold in Walmart.

Correction - this has nothing to do with responsiveness.

This is (and always has been) an internal API intended for use by their DEV team (and only their DEV team) for their specific purposes.

If they wanted us messing around in there - or knowing anything about this API - they would make it public.

VP

[Fidelitymusic]

Here we go, another day and you have nothing better to do but go on another forum to fuss about the scripting API that you have no intention of using.

If it upsets you, contact Fender and let them know that there are thieves, as you'd like to refer to us, documenting what objects, methods, and elements are available within the scripting environment to create our own scripts. You can encourage them to issue a takedown of it so nobody can use it, that'll satisfy you.

[wikter]

There's a "how to" create devices, but it ends on the easy line. Create, assign parameters, go to bed, no functions, no paging, no autolearn...
There's also a list of devices created in xml. A company don't waste time on xml files/code when it can be done by creating binaries. But, yeah, this goes nowhere.
I did my job opening tickets and being answered like that: we're germans, you're wrong, we made no mistakes, don't mess with us, we're perfect.
Ok Presonus, bye!.
Let's see how Fender manages this.

[Vocalpoint Studios]

So nobody can use it, that'll satisfy you.

That’s just it - nobody can use it without full access to the API and it’s real documentation but if your little scripting adventure here is making you happy - rock on.

VP

[Fidelitymusic]

Crossfade Tool.png

Added a basic Crossfade Tool script and various updates to the scripting API documentation.

https://github.com/CSources/Studio-Pro- ... sfade-tool

[Housemus]

I don't see any problem in enthousiatic user engagement and the building of nice extensions and/or documentation of the scripting environment. It is a bit negative to view it as forbidden territory.

Some companies have well documented API's, some don't. Autodesk for example had 3 API's back in the day for C++, Lisp and Visual Basic of their 3D software. Lots of companies were making usefull extensions, but some companies like user involvement and some don't. I do think that the half hearted approach and historically semi-open status of the current situation is not ideal.

Maybe Fender should only license qualified developers for building extensions as a middle ground. Like Max for Live. Call it Fender Premium or something like that. Or just forbid it completely if they don't want it. We will then just wait when new features are dropped.

Fender strikes me as this kind of company when I see the killing of the old forum, the strange update cycles, the included/excluded tools in the subscription model. It is just very inconsistent the last few years and the discussion of the company strategy is like walking on egg shells on other forums.