← SyncScript Pro
SyncScript Pro Help

Getting started

What SyncScript Pro does

SyncScript Pro matches the dialogue of your screenplay to the spoken words of your Final Cut Pro clips. It transcribes every clip of an exported Event on your Mac, matches the transcripts against the script lines and prepares the result as keywords on the clips. You review and correct the result on a small timeline before you export. Nothing is changed in Final Cut Pro until you export and send the result. SyncScript Pro does not tag your footage fully automatically, and it is not meant to. The matching gives you suggestions, and an assistant editor checks and corrects every result on the timeline before it goes into Final Cut Pro. The app gives the assistant editor a tool to reach the same checked result in roughly half the time. We don't know a faster way to do it, and a result that a person has checked is the only one worth cutting with.

How many lines are found depends on the footage. A scene with improvised or unclear dialogue matches less, and that is expected. You close the gaps by hand, which is still much faster than doing everything manually.

Before you start

You need an Apple Silicon Mac running macOS 15 or later, and Final Cut Pro. The released app is built for Apple Silicon only. Your script must be a PDF with a text layer. Your clips must be in a Final Cut Pro Event as sync clips and/or multicam clips.

The app checks your license over the internet, and the first transcription downloads the speech model (about 1.5 GB). A short loss of connection does not block the app.

First launch

On the first launch the app asks for your email address. Enter it and click Continue. The button stays disabled until the address looks valid. You cannot skip this step. The address is sent with the license check, so support can find and renew your trial.

Step 1: import the Event and transcribe

Export a single Event from Final Cut Pro as FCPXML. On page 1. Transcribe, drop the file on the Import tile. Click Transcribe Clips. The first run downloads the speech model. When all clips are done, the app moves on to page 2. Script by itself after about a second. See Import an Event and transcribe the clips.

Step 2: import the script

If the app has not moved on, click Continue to Script. On page 2. Script, drop your screenplay PDF on the Script Input tile and select the scenes that you shot. See Import and edit the screenplay.

Step 3: match

Click Continue to Match Captions, then Start Matching on page 3. Matching. Look at the results, and fix lines without a caption. See Match the script and check the result.

Step 4: review and export

Click Continue to Keywords. On page 4. Keywords you see one clip at a time and can move, trim, replace and add keywords. When you are done, choose Export to Final Cut Pro… in the File menu and click Send to FCP, or Export FCPXML… to save a file. See Edit keywords on the timeline and Export keywords to Final Cut Pro.

Import and edit the screenplay

Import the screenplay PDF

Open page 2. Script. In the Script Input tile, drop your screenplay PDF on the drop zone, or click Choose... and pick the file. Only PDF files are accepted. No other screenplay format can be imported. The Transfer Script menu described below only reads files that SyncScript Pro itself wrote.

The PDF needs a text layer. The app has no text recognition (OCR): a scanned PDF without text produces no script lines.

Choose the scenes to work with

If the PDF contains more than one scene, the app lists the scenes it found and waits for your selection. Scene chips (All and one per scene, labeled like "Sz 42") appear for scenes that were detected from the clips of the imported Event and are also in the script. The Add scene: picker lists the other scenes found in the PDF. Review Clips opens the Scene Check window, which lists every clip with its scene. Every change of the scene selection parses the PDF again. Your own edits are carried over.

If you already imported a Final Cut Pro Event that carries scene metadata, the matching scenes are selected and parsed automatically.

What the parser recognizes

The parser reads the PDF text and builds one script line for every block of dialogue:

  • Scene headings are recognized when a line starts with INNEN, AUSSEN, INT., EXT., INT/ or I/E, in capital letters.
  • Scene numbers are taken from the numbers printed in the margin of the screenplay. A number only counts when a scene heading of the kinds above follows it. Lines before the first numbered scene get no scene number.
  • A character cue is a line in capital letters of 2 to 30 characters. Narrator cues such as ERZÄHLER or NARRATOR are not imported, and a line that contains " und " or " & " is not treated as a cue.
  • The separation of dialogue from stage directions is a heuristic tuned for screenplays in German.

Edit the script lines

Script lines appear in the Script Lines panel. Two views are available: Block Editor (the default) and Classic List. The choice is remembered.

In the Block Editor, click into a character name or dialogue to edit it. Drag a line to reorder it within its scene. Press Return in the middle of a line to split it. Your edits are staged: click Apply to commit them or Discard to drop them. Switching to Classic List applies staged edits automatically.

In the Classic List, click a line twice to edit it. Tick two or more lines with the selection buttons for merging, then click Merge to join them into one line.

Add a scene the PDF import missed

The Scene Selection tile appears once the PDF yielded scenes. In it, click Add Scene Manually. Enter the scene number (for example 42 or 62A) and, optionally, paste the scene text: character names in capital letters on their own line, dialogue below. The scene heading and stage directions are skipped. Click Add Scene.

Add one scene at a time. A scene that is already in the script, or that the PDF import found, is refused with a message in the sheet. So is pasted text that contains more than one scene. Deselecting the scene later removes its lines again, and Cmd+Z brings them back.

Move an edited script to another session

Use the Transfer Script menu above the script lines. Copy Script and Paste Script… move the lines between sessions through the system clipboard, so copying something else in between replaces them. Export Script… and Import Script… write and read a .syncscriptlines file. After a paste or an import, a sheet lets you choose which scenes to take.

Import an Event and transcribe the clips

Before you start

SyncScript Pro reads an exported Final Cut Pro Event file. It does not read a live Final Cut Pro library. Sync your clips in Final Cut Pro first, as sync clips and/or multicam clips, and export a single Event as FCPXML.

The source media of the clips must be reachable on disk.

Import the Event

Open page 1. Transcribe. In the Import tile, drop the Event file on the drop zone or click Choose File.... The picker accepts .fcpxml, .fcpxmld bundles and packages. Dropping a Final Cut Pro library (.fcpbundle) does nothing. Export a single Event instead.

Only the first Event in the file is imported. The tile shows the file name and a clip count. The count can differ from the number of clips that are transcribed, because only the first Event is imported. If the app finds no usable clips, it tells you to load an Event with sync clips and/or multicam clips.

Importing a new Event clears the transcription, captions and matches of the current session.

Choose the language

In the Transcribe tile, set Language:. The default is English, and the choice is remembered across launches and per session. The list contains 25 European languages.

The speech model itself is not given the language setting. The language is part of the transcript cache key, so changing it means the clips are transcribed again, and it is used as a hint when matching. Chinese, Japanese and Korean are not available.

Transcribe the clips

Click Transcribe Clips. The engine is Parakeet v3 and is chosen automatically. Each take is transcribed once from its own source audio on your Mac. The captions are shifted to every camera angle and the multicam clip of that take. Clips without an audio track are skipped, and so are conform variants of a clip that contain only picture.

The first run downloads the speech model (about 1.5 GB) and needs an internet connection. The button reads Loading speech model… while it loads.

While the run is active the button shows the progress, and Cancel stops it. Clips that are already transcribed stay in the cache, so a later run resumes quickly.

Missing media

Before transcribing, the app checks that the source files can be reached. If files are unreachable (for example a disk that is not mounted), the run stops with a message that starts with the number of unreachable files and lists up to five file names. Mount the volume and run Transcribe Clips again.

Transcribe again from the source

After a run, Re-Transcribe from Source transcribes all clips again instead of reusing the cached results. Use it after updating the app. It takes as long as the first run. A confirmation dialog asks first.

When the run is done

A green badge reports "Transcription complete" with the number of captions. When all clips succeeded and you are still on page 1. Transcribe, the app moves on to page 2. Script by itself after about a second. If it does not, click Continue to Script.

If some clips failed, the badge is orange, the failed clips are named in a red message, and the app does not advance on its own.

Match the script and check the result

Start matching

Open page 3. Matching and click Start Matching. Matching does not start by itself. The page first shows whether script lines and captions are loaded.

Each script line is matched against the captions of the clips. Scenes are respected: a line is matched against the clips of its own scene, and a clip without scene metadata can match any selected line. Only lines that are switched on and have no variant suffix are matched.

Read the results

The list on the left shows one row per active script line (lines that are switched off, and lines with a variant suffix, have no row): a colored dot, the line number, the character, the dialogue and a similarity percentage. A line without a match shows two dashes instead of a percentage, and a line with several matches shows a count badge. The status labels are Exact Match, Close Match, Minor Difference, Major Difference, No Match, Non-Dialogue and LLM Filled. LLM Filled appears only with the optional local LLM check described below.

Select a row to see the matching captions, the clip name with timecode and the best similarity score in the Details tile.

Fix a line that found no caption

Select a line that has no match and click Assign Caption Manually, then pick one of the unmatched captions in the sheet Assign Caption to Keyword. A manual assignment counts as an exact match. To drop a wrong match, remove the caption with the red x in the details.

Check which clips landed in which scene

On page 2. Script, click Review Clips in the Scene Selection tile. The floating window Scene Check lists every detected clip with its scene, and flags clips without scene metadata and scenes that are not in the script. From there you can add a missing scene manually.

Use the lines of one scene for the clips of another

Sometimes clips are labeled with a scene number that shares its setup with another scene. In the Block Editor, click the scene tab of the script scene with the right mouse button and choose Also Use for Clips of Scene…. Enter the scene numbers of the clips, separated by commas. A number such as 62 covers all clips of that scene. With a letter such as 62A, only that scene's clips are covered.

A plain number is used by the manual tools of the timeline. Only a lettered scene such as 62A changes which script lines automatic matching uses for those clips.

To undo this, click the tab with the right mouse button and choose Stop Using for Clips of followed by the scene.

Aliases are saved with the session. They are not part of an exported script file.

Match again

When results exist, the header shows a Re-Match Clip button (it reads Re-Match when it is not limited to one clip). It matches again the clip that is open in the timeline editor. Its menu offers Re-Match All Clips. If you edited the timeline in that scope, the app asks first. Manual keyword edits are discarded. Additional titles and crew talk regions are kept.

Optional: local LLM check

In Settings, tab LLM, Enable LLM Matching lets a local Ollama model verify matches and drop captions it rejects. It is off by default and is switched off again at every launch. You must install and start Ollama yourself and pull the model. The app does not do that. It runs only when matching the whole session, not for Re-Match Clip.

Edit keywords on the timeline

The timeline at a glance

Page 4. Keywords shows one clip at a time: the video, a transport bar and four lanes. From top to bottom the lanes are the ruler with the Action Cut range, the lane for additional titles, the main lane with the waveform, keyword blocks and DISCARD blocks, and the captions lane.

Use the chevrons in the transport bar or Option+Left / Option+Right to move to the previous or next clip.

Move and trim keywords

Drag a keyword block to move it. Drag an edge to trim it. Hold Option while dragging to duplicate it. Hold Cmd when you start dragging on empty space or on a keyword block to create a new keyword region instead; hold Cmd and Option to create a DISCARD region.

Magnetic snapping is on by default; toggle it with N. Pressing Cmd after you have started moving or trimming a block turns it off for the rest of that drag. Blocks snap to the playhead, to the edges of keyword, DISCARD and title blocks, to caption edges and to detected speech onsets. The onsets are not drawn on the timeline.

Shift blocks together (magnetic ripple)

Hold Shift, and no other modifier, when you start the drag. When you move a block, it and everything after it in the same lane travel together. When you trim the end of a block, its end and everything after it travel; when you trim the start, the rest of the block and everything after it shift. This works separately for the keyword lane and the title lane.

Set the Action Cut

Drag on an empty part of the ruler to set the range, or drag the green In and red Out markers. Dragging only moves the range. To also cut away what lies outside, press I and O at the playhead, or choose Set In Point and Set Out Point in the context menu: everything left of In and right of Out becomes DISCARD, as long as the point is more than 0.3 seconds from the clip edge. Keyword blocks inside the new DISCARD region are removed or shortened. Clear In/Out in the context menu of an empty spot removes the two points but keeps the DISCARD blocks.

Add additional titles

Drag horizontally on the empty title lane, then pick an existing title or a script keyword, or type a new title and click OK. Without text the label is Additional Title.

To add a title at the playhead, press T and choose from the list. Click a title twice to rename it. The context menu offers Rename, Copy, Replace with Existing Title, Convert to Keyword... and Remove.

Additional titles are exported as ordinary keyword markers, not as Final Cut Pro titles, as long as Include Additional-Title Keywords is on in the export sheet.

Replace a keyword

Click a keyword block with the right mouse button, or place the playhead on it and press R. The dialog Replace with Existing Keyword lists the other keywords of all scenes, grouped by scene; filter by number, character or dialogue, move with the arrow keys and press Return.

Mark a clip group as done

Click the checkmark in the transport bar, or press Cmd+D. In a group marked as done, edits on the timeline are refused with a message; uncheck it to change it again. Selecting and copying still work, and matching again can still overwrite a done group.

Export keywords to Final Cut Pro

What the export contains

The export writes keywords only. It saves your imported Event again, with keyword markers on the browser clips you worked on, and on clips that share a take with them: one marker per dialogue line, plus optional markers for additional titles and the Action Cut. Dialogue inside DISCARD regions is not exported. It does not create Final Cut Pro titles, captions or a timeline, and projects in the Event are left out. Additional titles are written as ordinary keyword markers.

The result is a new Event named like the source Event with " - SyncScript Pro" appended, so it does not merge into your original Event.

Open the export sheet

On page 4. Keywords, choose Export to Final Cut Pro… in the File menu (Cmd+E) or click Export to FCP in the bar below. The command is available once matching results exist and the timeline editor is open.

Choose what to export

  • All Clips exports every clip. Selected Clip Groups Only exports only the groups you pick with Choose Groups…; the other clips are not written to the file at all. By default the groups marked as done are selected. This choice is shown when your clips form groups.
  • Include Additional-Title Keywords adds one marker per additional title. It is on by default.
  • Include Action Cut Keyword adds a marker named Action Cut for each kept range. It is on by default.
  • Mark Outside Action Cut as Rejected sets a Rejected rating on every region outside the Action Cut. It is off by default.
  • Keyword Handles extend dialogue keywords, and the Action Cut and Rejected ranges, by the given number of frames at the start and end. The preset buttons are 0f, 12f, 24f and 48f and set both values. Keywords for additional titles get no handles.

Save your toggles and handles with Presets. Defaults for new exports are in Settings, tab Export.

Send to Final Cut Pro

Click Send to FCP. The app writes a temporary FCPXML file and opens it with Final Cut Pro. Final Cut Pro then asks which library to import into. Complete that dialog, then check the Keywords field in the Info Inspector.

The app reports success when the handoff happened, not when the import in Final Cut Pro has finished. Final Cut Pro must be installed.

Save the FCPXML as a file

Click Export FCPXML… instead to choose where the file is saved, for example to send it to someone. While a session is open, every export also writes a diagnostics copy into the session folder (or the diagnostics folder you chose), and a copy into the Default export location if you set one in Settings.

How keywords are written

A dialogue keyword reads like 001 CHARACTER dialogue. Commas are replaced by a character that looks similar, because Final Cut Pro keywords cannot contain commas; this is the setting Replace commas with alternative character, which is on by default. The case of character names follows Character name format: (uppercase by default). Both settings are in Settings, tab Parsing.

Sessions and keyboard shortcuts

Save and reopen your work

Your work lives in sessions. Choose Save Session in the File menu (Cmd+S) to save. Once the session contains script lines, the app also saves it automatically every five seconds while it is active, and the most recent session is reopened at launch.

To reopen another session, click it in the session list in the sidebar. There is no separate open command. The sidebar buttons create a new session, save the current one and import a session from a file. In the context menu of a session you can rename, export or delete it.

Move a session to another Mac

Choose Export Current Session… in the File menu. A session is a folder with the extension .syncscript. It does not contain your media; it stores the paths of the source files, so they must be reachable on the other Mac. Import it with the import button in the session sidebar; the import always creates a new session and opens it.

Start a new session

The dialog for a new session offers New (blank) and New (keep Script). The second keeps the loaded screenplay PDF and its scene list, but the script lines are cleared; parse them again on page 2. Script. Both start an empty session on page 1. Transcribe.

Change a keyboard shortcut

Open Settings and choose the Shortcuts tab. Click the key field of an action, press the new combination and the shortcut is set; Esc cancels. The trash button clears a shortcut. If a combination is already used, the app asks before rebinding it. Reset all to defaults restores the factory shortcuts after a confirmation.

Export… saves your shortcuts as a JSON file. Import… merges a file into your shortcuts; actions that the file does not mention go back to their default.

Some gestures are fixed and cannot be rebound: J, K and L for shuttle, the number keys to assign keywords, Cmd+Z and Cmd+Shift+Z for undo and redo.

Reference

Requirements and limits

  • macOS 15.0 or later. The released app is built for Apple Silicon only.
  • Final Cut Pro is required to use the result. The app reads and writes FCPXML.
  • The screenplay must be a PDF with a text layer. The app has no OCR and imports no other screenplay format.
  • The Event must be an exported .fcpxml or .fcpxmld file (or an Event dragged from Final Cut Pro) with sync clips and/or multicam clips. Only the first Event of a file is imported.
  • Transcription uses Parakeet v3 with 25 European languages. Chinese, Japanese and Korean are not available.
  • The export contains keywords only: no Final Cut Pro titles, no captions, no timeline.

Pages

  • 1. Transcribe: import the Event and transcribe the clips.
  • 2. Script: import the screenplay PDF, select scenes, edit script lines.
  • 3. Matching: match script lines to captions and check the result.
  • 4. Keywords: timeline editor and export.

Menus

  • Check for Updates… in the app menu checks for a new version. The app also checks automatically once a day.
  • Buy SyncScript Pro in the app menu opens the product page in the browser. It is shown until a paid or complimentary license is active.
  • Reset Everything... in the File menu (Shift+Cmd+R) clears the transcription, the script and keywords, and the matches and titles after a confirmation. It cannot be undone.
  • Export to Final Cut Pro… in the File menu (Cmd+E) opens the export sheet. It is available on page 4. Keywords once matching results exist.
  • Save Session in the File menu (Cmd+S) saves the current session.
  • Export Current Session… in the File menu writes the session as a .syncscript folder.
  • Send Feedback… in the Help menu opens the feedback sheet.

Settings

Open Settings with Cmd+comma. The tabs are Parsing, Display, Export, LLM, License, Shortcuts and About. A General tab (with Auto-advance to next phase) is shown only in Developer Mode, and an Advanced tab only while you hold Option; automatic advancing after transcription is on by default. The setting Auto-label FCPX rejects as Discard sits in the section FCP Import of the Parsing tab.

  • Replace commas with alternative character: on by default. Final Cut Pro keywords cannot contain commas; this replaces them with a character that looks similar when you export.
  • Character name format: UPPERCASE by default. Options: UPPERCASE, Title Case, As-is. Applied on export.
  • Trim whitespace from dialogue: on by default. Applied when the script is parsed.
  • Auto-label FCPX rejects as Discard: off by default. Applies to clips that are matched afterwards.
  • Default export location: empty by default. When set, every export also writes a copy to this folder.
  • Include timestamp in filename: on by default. Applies to that copy.
  • Include Additional-Title Keywords: on by default. Start value of the export sheet.
  • Include Action Cut Keyword: on by default. Start value of the export sheet.
  • Mark Outside Action Cut as Rejected: off by default. Start value of the export sheet.
  • Start Handle: and End Handle: 0 frames by default. Start values of the export sheet.
  • Enable LLM Matching: off by default, and off again after every launch. See Match the script and check the result.

Keyboard shortcuts (defaults)

All of the following can be rebound in Settings, tab Shortcuts, except the fixed gestures in the last item.

  • Playback: Space plays and pauses. Left and Right arrows step one frame; Shift with the arrows steps by 24 frames. Option with the arrows jumps to the previous or next clip. Up and Down jump to the previous or next edit point. Tab and Shift+Tab jump to the next or previous caption.
  • Marking: I sets the In point, O sets the Out point. Return opens the keyword popup. Delete removes the selected keyword. Esc deselects. T inserts an existing additional title at the playhead. R opens the picker to replace the keyword at the playhead. C toggles Discard at the playhead.
  • Zoom and view: plus and minus zoom, Shift+Z zooms to fit, N toggles magnetic snapping, S toggles skimming.
  • Session: Cmd+S saves, Cmd+D marks the current clip group as done, Cmd+B splits the block at the playhead, Cmd+C and Cmd+V copy and paste.
  • Fixed gestures: J, K and L shuttle; the number keys assign keywords 1 to 10 (with Shift: 11 to 20), acting on the selected caption; Cmd+Z and Cmd+Shift+Z undo and redo. These cannot be rebound.

Files the app creates

  • Sessions: ~/Library/Application Support/SyncScript Pro/Sessions/<id>.syncscript.
  • Speech models: in the Application Support folder of your user Library.
  • Transcript cache: ~/Library/Application Support/SyncScriptPro/TranscriptCache.
  • Export presets: ~/Library/Application Support/SyncScript Pro/export-presets.json.
  • Shortcuts: ~/Library/Application Support/SyncScript Pro/keyboard-bindings.json.
  • Script files you export: .syncscriptlines.

Network use

Transcription, matching and editing run on your Mac. The app contacts these hosts:

  • api.malibureview.app for the license check (when the main window appears, then daily; it sends a device hash, the app version and your email address), for redeeming or deactivating a license key, for update checks and for feedback you send.
  • huggingface.co, to download the speech models on first use.
  • localhost:11434 only if you enable the local LLM.

Feedback and diagnostics are sent only when you click the send button; if sending fails, the report is kept and sent automatically later. Buying a license, the license portal and the legal pages open in your browser.

Troubleshooting

No clips are found after importing the Event

The app reports "No synced clips found in the Event" when it finds no clips it can import in the file. Sync your clips in Final Cut Pro first, as sync clips and/or multicam clips. Dropping a Final Cut Pro library (.fcpbundle) does nothing.

Export a single Event as FCPXML and drop that file instead.

The run stops with "media file(s) unreachable"

The source files of some clips cannot be reached, usually because a disk is not mounted. The message names the volumes and up to five file names. Mount the volume and click Transcribe Clips again; finished clips are not transcribed again.

The speech model does not load

The first run downloads the speech models (about 1.5 GB for the main model) and needs an internet connection and enough free disk space. A failure is shown in a red message that starts with "Failed to load transcription models" and gives the reason. Connect to the internet, free up disk space and click Transcribe Clips again.

Some clips failed to transcribe

The result badge turns orange and reads "Transcription incomplete" with the number of failed clips. A red message names up to five of the failed clips and the reason, and the app does not move on to page 2. Script. Click Transcribe Clips again to retry.

The script shows no lines after importing the PDF

First check the status text. If it reads "PDF loaded: N scenes found. Select scenes and click Parse.", no scene is selected yet: pick scenes with the chips or the Add scene: picker.

If it reads "Parsed 0 script lines from PDF", the usual cause is a PDF without a text layer, such as a scan. The app has no text recognition. Use a PDF exported from your screenwriting software.

Also check the scene headings: the parser recognizes headings that start with INNEN, AUSSEN, INT., EXT., INT/ or I/E in capital letters. For a scene that was not found, use Add Scene Manually.

A character's lines are missing

Narrator cues (ERZÄHLER, NARRATOR) and words such as ENDE, FADE or CUT are not recognized as characters, and neither are cues that contain " und " or " & ". The text below such a cue is not imported under its own name and may end up in the dialogue of the previous speaker. Check these lines and fix them by hand in the Block Editor or the Classic List.

Keywords would land in the wrong place

An orange warning says the captions come from an older version with a bug in the sound sync. This appears for sessions that were saved with an older build. Click Transcribe Clips again, run matching again and then export.

Export to Final Cut Pro is greyed out

The command is available only on page 4. Keywords, after matching results exist and with the timeline editor open. In the export sheet both buttons are disabled while an export runs, when there is no result, or when Selected Clip Groups Only is chosen and no group is selected.

Send to FCP shows no error but nothing appears

The app reports the handoff, not the import. Final Cut Pro asks which library to import into; complete that dialog. The keywords are on the clips of a new Event named like your source Event with " - SyncScript Pro" appended. If Final Cut Pro is not installed, the export fails with an error.

The export reports "No source event"

The message says to import your Event on the Transcribe page first. It appears when the session holds no imported Event. Import the Event again on page 1. Transcribe, click Transcribe Clips (clips that are already transcribed come from the cache) and run matching again.

The app is blocked after the trial or shows a license message

On first launch the app asks for your email address before anything else; see Getting started.

The blocked screen shows the reason in plain words, for example that the trial period has ended, that the license has expired or has been revoked, that this version is no longer supported, or that the app has been offline too long. From there you can buy a license, check again, redeem a license key with I already have a license, or quit.

If the message says the license could not be verified yet, connect to the internet once and click Check Again. A short loss of connection alone does not block the app.

Send a problem report

Choose Send Feedback… in the Help menu. The sheet asks five short questions: 1. Goal, 2. Location, 3. Action, 4. Expectation and 5. Result. Answer at least one, ideally all five, in a few words each. Below them you can pick a severity: Showstopper, Bug, UI/Cosmetic, Feature Request or Question. Click the selected one again to clear it. Then click Send Feedback. The report includes your macOS account name, the app and macOS version, counts of keywords and captions, the engine, audio and video file names, the selected scenes and the session ID. The email field is prefilled with the address you entered at first launch and is sent unless you clear it. A screenshot is added only if you switch it on. If you are offline, the report is saved and sent later.

The Diagnostics button in the sidebar shows whether the script and match baselines were saved and which export is the latest. Send Diagnostics Ticket sends the two baselines and the latest export with its manifest. These files contain script dialogue, clip names and media references.

Written for version 1.2.86.