Import Script: Difference between revisions

From ACT3ai MediaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
= Import Script =
== Overview ==
== Overview ==
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]].   
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]].   
Line 8: Line 6:
* From [[Getting_Started|Getting Started]] → '''[[New_Project|New Project]]''' setup, choose **Import Script**.   
* From [[Getting_Started|Getting Started]] → '''[[New_Project|New Project]]''' setup, choose **Import Script**.   
* Inside the [[Editor|Editor]]: **File → Import → Script** (adds to the current project).
* Inside the [[Editor|Editor]]: **File → Import → Script** (adds to the current project).
== Supported Formats ==
* '''[[Final_Draft|Final Draft (FDX)]]''' – preserves scene numbers, title page, and notes where available. 
* '''[[Fountain|Fountain]]''' – plain‑text screenplay syntax. 
* '''[[Markdown_Support|Markdown]]''' – headings and lists mapped to scenes and beats. 
* '''[[Plain_Text|Plain Text]]''' – best‑effort parsing with format hints. 
* (Optional) '''[[PDF_Import|PDF]]''' – when enabled, uses OCR + heuristics (review carefully after import).


== How Imports Are Structured ==
== How Imports Are Structured ==
Line 21: Line 12:
* '''Action & Dialogue''' flow into the [[Script_Editor|Script Editor]] with speaker attribution.   
* '''Action & Dialogue''' flow into the [[Script_Editor|Script Editor]] with speaker attribution.   
* '''Beat Markers''' (from Fountain/Markdown) populate [[Story_Beats|Story Beats]].   
* '''Beat Markers''' (from Fountain/Markdown) populate [[Story_Beats|Story Beats]].   
* Optional page/line notes become [[Annotations|annotations]] in the [[Editor]].
* Optional page/line notes become annotations in the [[Editor]].


== How to Use ==
== How to Use ==
# Open '''[[Import_Script|Import Script]]''' from the project creation flow or the [[Editor]].   
# Open '''[[Import_Script|Import Script]]''' from the project creation flow or the [[Editor]].   
# Choose your file type: [[Final_Draft|FDX]], [[Fountain]], [[Markdown_Support|Markdown]], or [[Plain_Text|TXT]].   
# Choose your file type: [[Final_Draft|FDX]] or TXT.   
# Select parsing options:   
# Select parsing options:   
## Map # headings to [[Story_Beats|beats]] (Markdown/Fountain).   
## Map # headings to [[Story_Beats|beats]] (Markdown/Fountain).   
## Preserve original scene numbers.   
## Preserve original scene numbers.   
## Detect languages for [[Subtitles|subtitles]] and [[Dubbing|dubs]]. 
# Click '''Import''' to preview the parsed structure.   
# Click '''Import''' to preview the parsed structure.   
# Confirm to create '''Acts, Scenes, Shots''' and open in the [[Script_Editor|Script Editor]].   
# Confirm to create '''Acts, Scenes, Shots''' and open in the [[Script_Editor|Script Editor]].   
Line 44: Line 34:
* Cast roles in [[Characters|Characters]] and assign [[Digital_Actors|Digital Actors]].   
* Cast roles in [[Characters|Characters]] and assign [[Digital_Actors|Digital Actors]].   
* Block shots in [[Top_Down_View|Top‑Down View]] and add camera notes.   
* Block shots in [[Top_Down_View|Top‑Down View]] and add camera notes.   
* Generate previews via [[Google_Veo_3|Google Veo 3]], [[Runway|Runway Integration]], or [[WAN_AI|WAN AI]].   
* 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.
* Finish and [[Build_Video|Build Video]]; then use [[Export_Script|Export Script]] / media export as needed.


Line 51: Line 41:
* '''Dialogue misattributed''' → Ensure character names are uppercase and on their own lines.   
* '''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.   
* '''Excessive paragraphs in one scene''' → Add blank lines between action blocks for clearer segmentation.   
* '''Non‑English scripts''' → Enable language detection to prep [[Subtitles|subtitles]] and [[Dubbing|dubbing]] tracks.
* '''Non‑English scripts''' → Enable language detection to prep subtitles and dubbing tracks.


== Credits & Storage ==
== Credits & Storage ==

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: ActSceneShot.
  • 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.