Import Script: Difference between revisions

From ACT3ai MediaWiki
Jump to navigation Jump to search
(Created page with "= Import Script = <strong>Coming Soon</strong> Contact Us if you have any problems using our product, or if you have questions.")
 
No edit summary
Line 1: Line 1:
= Import Script =
== Overview ==
The '''Import Script''' feature lets you upload and parse existing screenplay documents so you can start editing and planning in ACT 3 AI without retyping. It automatically converts industry‑standard formats into the Editor’s structured script view.


<strong>Coming Soon</strong>
== Supported Formats ==
* **Final Draft (.fdx)** 
* **Plain Text (.txt)** with Fountain or Markdown screenplay syntax 
* **PDF (.pdf)** (text‑based only; images/hand‑written pages not supported)


== How It Works ==
# Click the **Import Script** button in the main navigation or on the Editor’s start screen. 
# Select your file or drag‑and‑drop into the upload area. 
# ACT 3 AI parses scene headings, character names, dialogue, and action lines. 
# Review the auto‑mapped elements in a preview dialog; make corrections if needed. 
# Confirm to load the structured script into the Editor, ready for writing, shot planning, and AI enhancements.


== Preview & Validation ==
* **Element Mapping** – See a side‑by‑side list of parsed elements (Scenes, Characters, Dialogue). 
* **Error Highlighting** – Lines that failed to parse (e.g., unusual formatting) appear in red; click to edit raw text. 
* **Character Extraction** – Unique character names auto‑populate the Cast and Characters pages for quick assignment.
== Integration with Workflow ==
* **Immediate Linking** – Imported scripts link to storyboards, shot prompts, and timeline slots as soon as they load. 
* **Auto‑Tagging** – Script elements are tagged with metadata (scene number, shot count) to drive scheduling and budget estimates. 
* **Version Control** – Each import creates a new script version in the project’s history for easy rollback and comparison.
== Tips & Troubleshooting ==
* For best results, use a text‑based PDF or native FDX/CELTX/FPI file. 
* Avoid PDFs that contain scanned images—text extraction will not work. 
* If character names merge with action lines, edit them in the preview dialog before import. 
* Re-run **Import Script** any time you update the source file; new versions appear as separate script drafts in your project.
== See Also ==
* [[Editor]] 
* [[Characters]] 
* [[Cast]] 
[[Category:ACT 3 AI Features]]




[[Contact_us|Contact Us]] if you have any problems using our product, or if you have questions.
[[Contact_us|Contact Us]] if you have any problems using our product, or if you have questions.

Revision as of 08:38, 16 July 2025

Overview

The Import Script feature lets you upload and parse existing screenplay documents so you can start editing and planning in ACT 3 AI without retyping. It automatically converts industry‑standard formats into the Editor’s structured script view.

Supported Formats

  • **Final Draft (.fdx)**
  • **Plain Text (.txt)** with Fountain or Markdown screenplay syntax
  • **PDF (.pdf)** (text‑based only; images/hand‑written pages not supported)

How It Works

  1. Click the **Import Script** button in the main navigation or on the Editor’s start screen.
  2. Select your file or drag‑and‑drop into the upload area.
  3. ACT 3 AI parses scene headings, character names, dialogue, and action lines.
  4. Review the auto‑mapped elements in a preview dialog; make corrections if needed.
  5. Confirm to load the structured script into the Editor, ready for writing, shot planning, and AI enhancements.

Preview & Validation

  • **Element Mapping** – See a side‑by‑side list of parsed elements (Scenes, Characters, Dialogue).
  • **Error Highlighting** – Lines that failed to parse (e.g., unusual formatting) appear in red; click to edit raw text.
  • **Character Extraction** – Unique character names auto‑populate the Cast and Characters pages for quick assignment.

Integration with Workflow

  • **Immediate Linking** – Imported scripts link to storyboards, shot prompts, and timeline slots as soon as they load.
  • **Auto‑Tagging** – Script elements are tagged with metadata (scene number, shot count) to drive scheduling and budget estimates.
  • **Version Control** – Each import creates a new script version in the project’s history for easy rollback and comparison.

Tips & Troubleshooting

  • For best results, use a text‑based PDF or native FDX/CELTX/FPI file.
  • Avoid PDFs that contain scanned images—text extraction will not work.
  • If character names merge with action lines, edit them in the preview dialog before import.
  • Re-run **Import Script** any time you update the source file; new versions appear as separate script drafts in your project.

See Also


Contact Us if you have any problems using our product, or if you have questions.