Troubleshooting

1. Script does not appear in the REAPER Actions list

Symptoms: After installing via ReaPack, the script is not searchable in the Actions list.

Fix:

  1. Confirm the install completed: Extensions → ReaPack → Browse packages → find the script → check the status column shows "Installed".
  2. If the status shows "Installed" but it's not in the Actions list, restart REAPER. ReaPack-installed scripts are registered on startup.
  3. If you installed manually, the script must be loaded via Actions → Show action list → Load. Copying the file to the Scripts folder does not auto-register it.
  4. Check the REAPER console (Ctrl+Alt+R or View → Show REAPER console) for any load errors.

2. Script opens and immediately closes (no visible error)

Symptoms: You run the script from the Actions list. The window flashes briefly and disappears, or nothing appears at all.

Cause: ReaImGui is missing or out of date.

Fix:

  1. Open Extensions → ReaPack → Browse packages.
  2. Search for ReaImGui.
  3. If it shows "Not installed", install it.
  4. If it shows "Installed", check the version — Temper requires 0.9.x or later. If outdated, right-click → Reinstall latest.
  5. Restart REAPER and try again.

3. Script does nothing when "Roll All" is clicked

Symptoms: The Scatter window opens, you click Roll All, but no items are placed on tracks.

Check these in order:

  1. A parent track is selected. Scatter requires you to select the parent track (not a child track) before running.
  2. The parent track has child tracks. Scatter operates on direct children. If the selected track has no children, there is nothing to assign to.
  3. Library root is set. The Library Root field must point to a valid directory containing audio files.
  4. Files match the filter. If a track's filter string doesn't match any filename in the library root, that track is skipped. Try clearing the filter to verify files exist.
  5. Edit cursor is placed. Items are inserted at the current edit cursor position. Confirm the cursor is visible in the arrange view.

4. "Missing dependency" error on launch

Symptoms: REAPER shows an error dialog mentioning a missing package, extension, or API function.

Fix:

  • ReaImGui missing: Install via Extensions → ReaPack → Browse packages → search "ReaImGui".
  • js_ReaScriptAPI missing: Optional but improves behavior. Install via ReaPack if desired.
  • SWS missing: Not required by Temper scripts. Only needed if another installed script requires it.

See the Dependency Checklist for the full list with download links.

5. macOS Gatekeeper blocks the script

Symptoms: On macOS, running the script produces: "ABS_Scatter.lua cannot be opened because the developer cannot be verified."

Fix:

This is a standard macOS security warning for files downloaded from the internet. ReaScript .lua files are plain text and do not execute outside of REAPER's Lua environment.

To allow the script:

  1. Open System Preferences → Security & Privacy → General.
  2. Click Open Anyway next to the blocked item.
  3. Alternatively, right-click the .lua file in Finder → Open → Open in the dialog.

For ReaPack-installed scripts, the download is handled by ReaPack itself. If you see this warning, follow the same procedure for the ReaPack extension binary (.dylib) in your UserPlugins folder.

6. ReaPack sync fails or repository is unavailable

Symptoms: Extensions → ReaPack → Synchronize packages returns an error or the Temper repository shows as unavailable.

Fix:

  1. Check your internet connection.
  2. Go to Extensions → ReaPack → Manage repositories and verify the Temper URL is correct: 
    https://tempertools.com/reapack/index.xml
  3. If the URL is correct and sync still fails, try Extensions → ReaPack → Refresh repositories (forces a re-fetch of the index).
  4. If the issue persists, check the Temper Discord #support channel — it may be a temporary server issue.

7. Duplicate items placed on every roll

Symptoms: Each Roll places new items on top of existing ones at the same position, building up a stack.

Explanation: This is expected behavior. Scatter inserts new items at the edit cursor without removing previous ones. It does not manage existing items.

Workflow fix:

  • Select and delete previous items before rolling again, or
  • Move the edit cursor to a new position for each roll variation, or
  • Use REAPER's undo (Ctrl+Z) to step back to before the previous roll.

8. Keyboard focus lost after closing script window

Symptoms: After closing the Scatter window, keyboard shortcuts stop working in REAPER. You need to click the arrange view before shortcuts respond again.

Fix: Install js_ReaScriptAPI via ReaPack. This extension enables proper focus return when script windows close. Without it, REAPER doesn't always reclaim keyboard focus automatically.

9. Permissions error on Windows (script won't load)

Symptoms: REAPER shows a permissions error when trying to run or load the script.

Fix:

  1. Check that the .lua file is not in a protected folder (e.g., C:\Program Files\). Scripts must be in the REAPER Scripts folder: %APPDATA%\REAPER\Scripts\
  2. Check the file is not blocked by Windows: right-click the .lua file → Properties → look for an Unblock checkbox at the bottom → check it and click OK.
  3. If running REAPER as a non-admin user, ensure the Scripts folder has write permissions (required for preset saving).

10. Script ran previously but stopped working after a REAPER update

Symptoms: Scatter worked before, but after a REAPER update it no longer opens or produces errors.

Fix:

  1. Check the Known Limitations page to confirm the new REAPER version is supported.
  2. Update ReaImGui: Extensions → ReaPack → Browse packages → search "ReaImGui" → reinstall/update.
  3. Check the REAPER console for specific error messages (Ctrl+Alt+R).
  4. If a REAPER API change broke the script, report it in the Temper Discord #bug-reports channel with your REAPER version and the console error. We validate against REAPER API updates and will issue a patch.

Still stuck?

Post in the #support channel on the Temper Discord. Include:

  • Your REAPER version (Help → About REAPER)
  • Your OS and version
  • ReaImGui version (visible in ReaPack packages list)
  • What you were doing when the issue occurred
  • Any error text from the REAPER console (Ctrl+Alt+R)