Create, save, and export scripts
Write a motion script from scratch or export an edited version. Learn how edits are saved and when to export a copy or sync changes to the original file.
You can create a script without generating one from video first. Save the version before exporting. Sync funscript is available only for tracks with an imported source file.
01 Start with a blank script
- In Library, click New script, or choose New script from Studio's Editor entry.
- A new script starts with no nodes. Open Duration and set its timeline length; this example uses 15 seconds.
- Turn on Add node and place alternating high and low positions in the waveform. Press Esc to finish. Select nodes to adjust their position or time. Start with a few nodes to check the rhythm.
- Click Save and enter a Title. Description is optional. This example uses Four-beat practice.
- Click Save script and check Saved and the version information. The new script appears in Library → Scripts. Saving does not automatically link it to a video.
- To use it with a video, follow Match and link scripts. Use Export when you need a file.
02 Save and export a script
| Current state | What to do next |
|---|---|
| Normalize / Clamp / Smooth / Scale / Phase Shift / Repeat preview | Apply commits the edit; Cancel or Esc discards it. A preview is not a saved version. |
| Edits applied to the active track | Stop editing and wait for Saved. Unsaved means saving is still in progress. Follow any error or conflict message. |
| New script or metadata changes | Check Title and Description, then click Save script. |
| A copy opened from History | Apply version to commit the edited copy. Comparing a version does not apply it. |
- Finish transform previews, resolve unapplied session copies on each axis, and confirm the versions you want.
- Click Export, choose a destination, and wait for Script exported.
- Check the exported .funscript and any additional axis files. Reimport them if you want to verify the result.
Use Library → Import → Import script to reopen the main .funscript. If export fails, use Retry export or choose a writable destination.
How do Export, Sync funscript, and backup differ?
Export saves the stored tracks and metadata to files. Sync funscript lists the local source files it will replace and asks you to confirm. It does not create a separate backup. Settings → Library → Back up… backs up the library. A track without an imported source shows No source file.
03 Verify multi-axis files and sync sources
This example uses a script with L0 and R0 tracks. Check every axis file. ZIP export bundles the scripts and metadata together; the primary-axis file alone does not contain every axis.
The export contains a main file and .twist.funscript, with 42 L0 nodes and 41 R0 nodes, plus a .peaksync.json metadata file. Keep the shared filename prefix and axis suffixes. Select the main file when reimporting, then check both tracks. For ZIP exports, extract the archive first.
- Save the versions you want for each axis. Resolve any Session only copies with Apply version first.
- Click Sync funscript and review the axes, versions, and source files in Replace these local source files?
- Confirm that these are the imported files you want to update, then click Sync files. To keep the original files, cancel and use Export to save elsewhere.
- Tracks without imported sources show No source file. New or generated scripts cannot sync to a source file that does not exist.
- If Source sync pending appears, use Resume sync as directed. For errors, check file availability and permissions before retrying.
- Reopen the source files after syncing and verify the edited nodes.
Here, the first L0 node in the reimported script changes from 50 to 60. After Saved appears, sync the files. On completion, Source files synced appears. The source file now starts at position 60; node times and all 41 R0 nodes are unchanged.
To back up the library, open Settings → Library → Back up…. For the full workflow, see Library backup. Export, sync, and library backup preserve different things.
Check your changes
The intended versions are saved. Reimporting preserves axes and nodes, and syncing updates the actual source files.