Discussion: Possibility of more open APIs or scripting support in Nuendo 15

[MattiasNYC]

I totally agree with what you wrote. All of it so far.

@Moli

• Is this something that has been considered before?

By users, sure. If you do a search for “scripting” you’ll find some threads tagged Nuendo;

Custom Scripting Support - Nuendo - Steinberg Forums

Scripting Features in Reaper are getting amazing - Hope SB takes note - Nuendo - Steinberg Forums

Avid Scripting SDK is about to be released. When will nuendo join the SDK - Nuendo - Steinberg Forums

Might be worth reading them just to get a feel for what other people thought.

Steinberg on the other hand rarely make contributions here, so, expect absolutely no response from them

@Moli

one recurring issue I run into is the need to constantly switch between multiple preconfigured PLE presets and trigger them back and forth while working. These presets are already well-designed and tuned — the challenge is simply running and switching them efficiently during real production work.

I agree. I have had somewhat the same experience if I understand you correctly.

One way to improve this would be to allow us to stack multiple PLE scripts into one “super-script” in the same editor interface. Right now in the one instance I ran into this and decided to finish it I have one main PLE that triggers multiple other PLEs post-process. This is incredibly cumbersome because if any of the “sub”-scripts need tweaking they need to be loaded again, tweaked, re-saved, and then I need to re-open the main script again to test it. It really should all be possible to do in the same interface. As you said earlier, it sometimes feels like spending a lot of time to chase small improvements.

I think this would solve some problems.

@Moli

I completely understand that developer resources are limited, and that small, highly specific workflow requests can quickly accumulate into a very large workload if each one is handled at the core feature level. I think this is something most of us on the forum can relate to.

This is also why I personally feel that some form of controlled, user-level extensibility could be beneficial — not to replace official development, but to complement it.
Many of these fine-grained, user-specific workflow improvements seem like good candidates to be solved by users or the community themselves, rather than requiring official implementation every time.

(emphasis added) Absolutely, and a really great point. Rather than having Steinberg plan and implement new functions opening up more of it to scripting by users allows potentially hundreds or even thousands of users to assemble functionality that can then be shared. This should be a no-brainer decision by Steinberg assuming it’s technically feasible and not too costly.

All functions that now appear to be “edge-cases” where you have a thread feature-request posted and 10 likes and nothing else might seem like wasted resources from SB’s perspective but allowing us to take care of that ourselves makes that a non-issue. Great for everyone.

I think it would be a great boost to the Nuendo community, especially the post-production community, if we could do this. I can imagine a forum tag for scripts and then we can share our solutions for different situations.