Import Script: Difference between revisions

From ACT3ai MediaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(9 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Overview ==
== 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.
The '''[[Import_Script|Import Script]]''' feature lets you bring existing screenplays and outlines into [[ACT3AI|ACT 3 AI]] so you can immediately continue in the [[Editor|Editor]] with structured [[Acts|acts]], [[Scenes|scenes]], and [[Shots|shots]].
Imports are parsed, auto‑formatted, and linked to downstream tools like [[AI_Wizard|AI Wizard]], [[Digital_Actors|Digital Actors]], and the [[Rendering_System|Rendering System]].


== Supported Formats ==
== Where to Find It ==
* **Final Draft (.fdx)** 
* From [[Getting_Started|Getting Started]] → '''[[New_Project|New Project]]''' setup, choose **Import Script**.   
* **Plain Text (.txt)** with Fountain or Markdown screenplay syntax  
* Inside the [[Editor|Editor]]: **File → Import → Script** (adds to the current project).
* **PDF (.pdf)** (text‑based only; images/hand‑written pages not supported)


== How It Works ==
== How Imports Are Structured ==
# Click the **Import Script** button in the main navigation or on the Editor’s start screen.   
* Script elements are mapped to the ACT 3 hierarchy: '''[[Acts|Act]] → [[Scenes|Scene]] → [[Shots|Shot]]'''. 
# Select your file or drag‑and‑drop into the upload area.   
* '''Scene Headings''' (e.g., INT./EXT.) become [[Scenes|Scene]] cards.   
# ACT 3 AI parses scene headings, character names, dialogue, and action lines.   
* '''Action & Dialogue''' flow into the [[Script_Editor|Script Editor]] with speaker attribution.   
# Review the auto‑mapped elements in a preview dialog; make corrections if needed. 
* '''Beat Markers''' (from Fountain/Markdown) populate [[Story_Beats|Story Beats]].   
# Confirm to load the structured script into the Editor, ready for writing, shot planning, and AI enhancements.
* Optional page/line notes become annotations in the [[Editor]].


== Preview & Validation ==
== How to Use ==
* **Element Mapping** – See a side‑by‑side list of parsed elements (Scenes, Characters, Dialogue).   
# Open '''[[Import_Script|Import Script]]''' from the project creation flow or the [[Editor]]. 
* **Error Highlighting** – Lines that failed to parse (e.g., unusual formatting) appear in red; click to edit raw text.   
# Choose your file type: [[Final_Draft|FDX]] or TXT. 
* **Character Extraction** – Unique character names auto‑populate the Cast and Characters pages for quick assignment.
# Select parsing options: 
## Map # headings to [[Story_Beats|beats]] (Markdown/Fountain).   
## Preserve original scene numbers. 
# Click '''Import''' to preview the parsed structure.
# Confirm to create '''Acts, Scenes, Shots''' and open in the [[Script_Editor|Script Editor]].   
# (Optional) Run '''[[AI_Wizard|AI Wizard]]''' to fill missing beats, logline, or theme.


== Integration with Workflow ==
== Formatting Hints (For Best Results) ==
* **Immediate Linking** – Imported scripts link to storyboards, shot prompts, and timeline slots as soon as they load.   
* Use proper '''Scene Headings''' (e.g., `INT. LAB – NIGHT`) so the parser can segment reliably.   
* **Auto‑Tagging** – Script elements are tagged with metadata (scene number, shot count) to drive scheduling and budget estimates.   
* Keep character names on their own lines in ALL CAPS for accurate dialogue mapping. 
* **Version Control** – Each import creates a new script version in the project’s history for easy rollback and comparison.
* In Markdown/Fountain, use `#` / `##` for beats and sub‑beats to seed [[Story_Beats|Story Beats]].   
* Avoid embedding images in text imports—attach reference art separately to [[Storyboard_Panels|Storyboard & Panels]].


== Tips & Troubleshooting ==
== After Import: Next Steps ==
* For best results, use a text‑based PDF or native FDX/CELTX/FPI file.   
* Open the [[Timeline|Timeline]] to arrange scenes and add transitions.   
* Avoid PDFs that contain scanned images—text extraction will not work.   
* Cast roles in [[Characters|Characters]] and assign [[Digital_Actors|Digital Actors]].   
* If character names merge with action lines, edit them in the preview dialog before import.   
* Block shots in [[Top_Down_View|Top‑Down View]] and add camera notes.   
* Re-run **Import Script** any time you update the source file; new versions appear as separate script drafts in your project.
* Generate previews via [[Google_Veo_3|Google Veo 3]], [[Runway|Runway Integration]], or [[Wan|WAN AI]]. 
* Finish and [[Build_Video|Build Video]]; then use [[Export_Script|Export Script]] / media export as needed.


== See Also ==
== Troubleshooting ==
* [[Editor]]   
* '''Missing scenes or wrong splits''' → Check scene heading syntax; re‑run import with “Preserve scene numbers.” 
* [[Characters]]
* '''Dialogue misattributed''' → Ensure character names are uppercase and on their own lines. 
* [[Cast]]
* '''Excessive paragraphs in one scene''' → Add blank lines between action blocks for clearer segmentation. 
* '''Non‑English scripts''' → Enable language detection to prep subtitles and dubbing tracks.
 
== Credits & Storage ==
* Importing text is free; AI cleanup or auto‑structure prompts may use small [[Credit_System|credits]].  
* Resulting previews and generated media count toward plan storage (see [[Billing_Model|Billing Model]] and [[Credit_System|Credit System]]).


[[Category:ACT 3 AI Features]]
== Privacy & Rights ==
* Imported files are stored within your [[Organization|Organization]] and follow project‑level permissions. 
* Use only material you have the rights to process; see [[Documentation|Documentation]] → Legal/Usage.


== See Also ==
* [[New_Project|New Project]] 
* [[Script_Editor|Script Editor]] 
* [[AI_Wizard|AI Wizard]] 
* [[Characters]] / [[Digital_Actors|Digital Actors]] 
* [[Storyboard_Panels|Storyboard & Panels]] / [[Top_Down_View|Top‑Down View]] 
* [[Timeline|Timeline]] 
* [[Build_Video|Build Video]] 
* [[Export_Script|Export Script]] 
* [[Credit_System|Credit System]] / [[Billing_Model|Billing Model]]


[[Contact_us|Contact Us]] if you have any problems using our product, or if you have questions.
[https://act3ai.com/contact Contact Us] if you have any problems using our product, or if you have questions.

Latest revision as of 08:08, 27 August 2025

Overview

The Import Script feature lets you bring existing screenplays and outlines into ACT 3 AI so you can immediately continue in the Editor with structured acts, scenes, and shots. Imports are parsed, auto‑formatted, and linked to downstream tools like AI Wizard, Digital Actors, and the Rendering System.

Where to Find It

How Imports Are Structured

  • Script elements are mapped to the ACT 3 hierarchy: Act → Scene → Shot.
  • Scene Headings (e.g., INT./EXT.) become Scene cards.
  • Action & Dialogue flow into the Script Editor with speaker attribution.
  • Beat Markers (from Fountain/Markdown) populate Story Beats.
  • Optional page/line notes become annotations in the Editor.

How to Use

  1. Open Import Script from the project creation flow or the Editor.
  2. Choose your file type: FDX or TXT.
  3. Select parsing options:
    1. Map # headings to beats (Markdown/Fountain).
    2. Preserve original scene numbers.
  4. Click Import to preview the parsed structure.
  5. Confirm to create Acts, Scenes, Shots and open in the Script Editor.
  6. (Optional) Run AI Wizard to fill missing beats, logline, or theme.

Formatting Hints (For Best Results)

  • Use proper Scene Headings (e.g., `INT. LAB – NIGHT`) so the parser can segment reliably.
  • Keep character names on their own lines in ALL CAPS for accurate dialogue mapping.
  • In Markdown/Fountain, use `#` / `##` for beats and sub‑beats to seed Story Beats.
  • Avoid embedding images in text imports—attach reference art separately to Storyboard & Panels.

After Import: Next Steps

Troubleshooting

  • Missing scenes or wrong splits → Check scene heading syntax; re‑run import with “Preserve scene numbers.”
  • Dialogue misattributed → Ensure character names are uppercase and on their own lines.
  • Excessive paragraphs in one scene → Add blank lines between action blocks for clearer segmentation.
  • Non‑English scripts → Enable language detection to prep subtitles and dubbing tracks.

Credits & Storage

  • Importing text is free; AI cleanup or auto‑structure prompts may use small credits.
  • Resulting previews and generated media count toward plan storage (see Billing Model and Credit System).

Privacy & Rights

  • Imported files are stored within your Organization and follow project‑level permissions.
  • Use only material you have the rights to process; see Documentation → Legal/Usage.

See Also

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

Retrieved from "https://wiki.act3ai.com/index.php?title=Import_Script&oldid=605"