Your tools.
Your rules.

1. For audio signal processing, open the node-based Creator. Connect input, processing and output, then design the mini-module’s controls.
2. If you need another algorithm, add C++ Function and use the Creator SDK.
3. For commands, MIDI generation, file analysis and custom windows, open Lua Creator from the scripts section.
4. Save your source project. Compiling a DSP module and installing a Lua package are separate ways to add your result to the app.

You have chosen the right editor for the task. Detailed reference material is available on the Creator page.

1. Open Lua Creator from the scripts section. Create a package with New or open an SDK example with Open.
2. Review the manifest: ID, name, version, commands, entry files, contexts and permissions.
3. Select a command, edit its Lua file and press Check. Fix errors reported in the log.
4. Save the package and press Preview copy. Inspect the result on the project copy.
5. When satisfied, use Run in real project on your actual project. Stop ends an active run.
6. Press Install to add its commands to the library; Export saves a .vltscript package to share.

The checked script is installed and available in the scripts menu.

Check validates the source; it does not replace testing behavior on a project copy.

local context = vlt.context.get()
local tracks = context.selection.tracks or {}

return {
  message = "Selected tracks: " .. #tracks
}

1. Read the selection with vlt.context.get() and project state with vlt.project.get().
2. Check that a track or MIDI clip exists and prepare operations using IDs from the current response.
3. Pass the current revision, a descriptive label and operations to vlt.project.apply().
4. Inspect the result and undo it in the app. If the project changed during processing, read it again and prepare new operations.

A consistent batch of edits is applied and available in history.

Start with midi-transpose: it handles selection, MIDI range and state freshness.

1. Open interactive-workbench or styled-workbench and inspect its window description and handlers.
2. Use native buttons, fields, tables and tabs; add a canvas for custom graphics.
3. Break lengthy work into chunks, show progress and provide cancellation.
4. Check keyboard operation, window closure and Stop. Review completed edits separately from unfinished background work.

Your tool has its own interface and a controllable lifecycle.

1. Open pcm-analysis, transient-slicer or Arrangement Lab from the SDK.
2. Choose an input file or generation settings and review the required permissions.
3. Read and synthesize in bounded blocks, with cancellation for lengthy work.
4. Audition the result, check its level and then add the completed audio to the project.

You have analyzed or generated audio ready for the arrangement.

1. Open a package in Lua Creator and review its sources, resources and declared permissions.
2. Run Check and Preview copy, then Install.
3. Select a command in the script manager, assign a shortcut or add it to the toolbar. Context commands appear where applicable.
4. Share with Export → .vltscript and keep the editable source.
5. If a script does not start, check the selected command, project context, permissions and log.

Commands are available where needed, and the package is ready to share.