I never looked into Reaper scripts much

can you explain what can be done and what can't be done with scripts?

and how is it different than actions?

Thanks

 

(Custom) Actions are just calls of built-in functions or their combinations,

ReaScript can call Reaper's API functions, so can be used for macros, extensions, basically anything:
https://www.reaper.fm/sdk/reascript/reascript.php

 

Actions are scripts. But they are written in native code, not in ReaScript.
What primarily defines Actions, however, is the fact that they follow a very simple logic.
They are triggered by the user, the code is executed once sequentially from top to bottom, and then they automatically terminated.

In order of increasing complexity:

• Actions: Native scripts with simple, sequential execution logic, managed without or with very few control structures (conditions, loops, etc.).
• Custom Actions: Sequential chaining of scripts (native or user-created with ReaScript) with simple, sequential execution logic.
• ReaScript: Scripts created by users in EEL2, Lua, or Python. The complexity can vary. From simple linear scripts (like actions), through communication with external programs, web calls, vst-communication, etc., up to analytical or procedural programming and automation tasks.
• Extensions: Compiled, and therefore potentially very performant, add-ons with deep integration into Reaper's Extension API, which can significantly extend Reaper's functionality (SWS, ReaPack, etc).

Custom actions only work reliably with actions and very simple sequential scripts, because within the chain of a custom action, there are no control structures to check whether one action has already finished executing before the next one starts. Therefore, if running an action takes too long, a kind of race condition occurs where the next action is executed even though the previous one has not yet finished.

 

Last edited: Tuesday at 5:14 PM