7/3/2023 0 Comments Script studio tutorialsObviously, if you wanted to set a fader to a specific dB value, you'd need to do the math to convert -10dB or similar to float.Ĭode: Select all let trackList = context.mainTrackList įor (i = 0 i < trackList.numTracks i ) Not the only or even best way to do that, but it's easy to understand and extrapolate from. Iterate tracks, and if a track has an audio channel, address it's properties. Some of my knowledge of the object model was acquired via means that don't allow publicly sharing but the method below for iterating tracks and addressing faders and pans doesn't really fall into that category. I'm mainly interested in trying to get access to track related values and functions like getters and setters for faders, pan knobs, etc. I don't know where it'll lead but at the very least I'll learn something new!Ĭolliderman wroteWould you be willing to share the list of methods you know of currently? Not sure if that's something you've documented for yourself or not but if so that would be awesome. I think I'll be able to get a decent grasp of Javascript pretty quickly and the prospect of tailoring some Studio One functionality to my needs is pretty cool. While I am a musician I actually am a developer as well, but mostly embedded projects in C/C to date. Not sure if an API will ever come from Presonus but that would be very cool if it did. That way people are free to decide for themselves whether they want to learn about it or not. I totally agree! The more information out there about this kind of stuff the better. Off topic: I can always hear some people thinking certain things when these scripting discussions come up so just to clarify some of it. It's not just nerds doing nerdy stuff because they're nerds.īy sheer coincidence of design or not (no idea) Studio One is setup for that better than most. That happens near daily on the Reaper forum. In comparison to alternately making a feature request and waiting two years for X when the application developers have much more important priorities, doing things that only they can do. … and then some friendly "code monkey" like darrenporter1 gives you X the next day. " Hey, is there any way to do X? It really annoys me that I can't do X." The benefit is to be able to simply go to a forum (or script archive) and ask. The above is a pretty common but somewhat narrow minded point of view. It's the developers job to make new features or functions. "I'm a musician and/or an audio engineer, not a developer. As far as I can tell, Sony Vegas was the first audio workstation to ever do anything like that. Vegas was always a Windows platform only product and it used C# as one of it's scripting languages, which worked really well there, and Sony published the full API on the web. A couple of products did it later on, Tracktion, Ardour, but for most part Reaper is the only product other than Vegas (which it was initially based on) that did it somewhat early on. Scripting in audio workstations is not exactly a widespread official feature in the industry. We just have to wait and see if they publish something at some point. I spent a good bit of time trying to figure out how he did that, what method he used to do that, with no luck.īut yes, any correctly written script that's in the \scripts folder will load when Studio One starts.ĭoes there exist a list of all known classes and member functions anywhere? He changed that later and made it a protected *.package like the Studio One script packages. The first version of Studio One X was unprotected, you could just unzip it and see all of it's source code. A script written by a user can be unzipped and read to study the source code, unless the JS in it is obfuscated. The core script packages / dependencies that install with Studio One are protected, for obvious reasons.
0 Comments
Leave a Reply. |