Skip to content

Releases

ReaSock 0.4.0

Choose a tag to compare

@github-actions github-actions released this 26 Oct 11:26
ae00805
  • Protocol 0.5.0: actions can have an on/off state. Register with toggle: true and set it with action.setState; REAPER shows it as a checkmark in menus and a lit toolbar button. In @techaudio/reasock, registerAction(…, { toggle: true }) and setActionState(), restored after a reconnect.
  • takes.set can point a take at a moved or renamed file (path), keeping its offset, rate, and length, as an undo point.
  • items.insert can place files at the play position (position: "play").
  • Fixed: items.insert handed new sources to takes through SetMediaItemTake_Source, which REAPER asks extensions not to use, since it may duplicate the source.
  • The MCP example can place media files (reaper_insert_media).

ReaSock 0.3.0

Choose a tag to compare

@github-actions github-actions released this 26 Oct 11:04
4b7ffe9
  • Protocol 0.4.0: ReaSock can now change the project, so a sound library or media browser can place sounds in REAPER.
  • items.insert places media files, or parts of them, at the edit cursor or a given time: on the current track, a given one, or a new one; one after another, each on its own track, or as takes of one item. Each file can bring a take name, item notes, and extension data. Every file is checked first, so a request with a bad file changes nothing, and the error says which file and why.
  • items.set and takes.set change item notes, take names, and extension data (per-item and per-take strings saved in the project), in batches.
  • Every change is one undo point, named after the client unless it passes its own name.
  • Peaks for inserted files are built a little at a time, so long files don't stall REAPER.
  • items.list, items.listSelected, and items.get can include item notes and extension data; takes.list can include extension data.
  • Items now report their active take (takeGuid, startOffset, playRate) and whether they loop their source, so a client can work out which part of a file an item plays. Slip edits now count as changes in items.selectionChanged.
  • transport.get and transport.changed include the edit cursor and the time selection.
  • initialize lists the methods the server supports (capabilities.methods), so clients can tell what an older ReaSock lacks.
  • debug.stats reports main-thread time per method.
  • @techaudio/reasock: createClient() returns a client right away and connects when REAPER starts, for apps that start before REAPER. Actions and subscriptions set up meanwhile wait for the connection. Calls fail at once with NotConnectedError while disconnected, and a REAPER that doesn't answer in time gives TimeoutError, so apps can tell "not running" from "busy". supports() says whether the connected ReaSock has a method, RpcError carries the error's data, and the signal option stops a client.
  • Examples: place.mjs places media files at the edit cursor.

ReaSock 0.2.1

Choose a tag to compare

@github-actions github-actions released this 26 Oct 10:00
56bb18e
  • @techaudio/reasock: a refused connect() (a wrong token, say) closes its connection, so a Node script exits instead of hanging. And an action or subscription REAPER refused is no longer retried on every reconnect, where it failed each time and stopped the client from ever reconnecting.

ReaSock 0.2.0

Choose a tag to compare

@github-actions github-actions released this 26 Oct 09:44
5ccd540
  • Security: WebSocket clients must send the token from REAPER's instance file (~/.reasock/instances/<pid>.json) in initialize (protocol 0.3.0). The token is random each time REAPER starts, and on macOS and Linux the instance file and its folders are now readable only by your user, so other users on the machine and web pages can't connect. Scripts inside REAPER need no token.
  • Examples: Python (a hotkey to copy selected items' file paths, a selection follower), an MCP server for AI agents, shell helpers with websocat, a browser dashboard, and a ReaImGui inspector panel, which also ships in the ReaPack package.
  • @techaudio/reasock on npm: a typed TypeScript client (every method, param, result, and event typed from the OpenRPC description), with reconnect that restores actions and subscriptions after REAPER restarts, and a browser build.

ReaSock 0.1.1

Choose a tag to compare

@github-actions github-actions released this 26 Oct 07:31
f0cbf66
  • Security: refuse WebSocket connections from web pages unless their origin is listed in allowedOrigins in ~/.reasock/config.json. Browsers don't apply cross-origin rules to WebSockets, so in 0.1.0 any website open while REAPER was running could connect to ReaSock and run REAPER actions. Native clients (Node, Python, Electron main processes) are unaffected.

ReaSock 0.1.0

Choose a tag to compare

@github-actions github-actions released this 26 Oct 04:42
700e10f
  • First release: a WebSocket and ReaScript bridge between REAPER and other programs, with actions clients can register (Lend), state-change events (Tell), queries for tracks, items, takes, and markers (Ask), and a bundled API reference.