Import Script: Difference between revisions

From ACT3ai MediaWiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
= Script Import =
= Import Script =


== Overview ==
== Overview ==
The Script Import feature in ACT 3 AI allows creators to bring existing scripts into the platform for editing, pre-visualization, and AI-assisted production.   
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]].   
It supports industry-standard screenplay formats and automatically adapts imported content to the ACT 3 AI scene structure.
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]].


== Key Benefits ==
== Where to Find It ==
1. Work with scripts written in external screenwriting tools.
* From [[Getting_Started|Getting Started]] → '''[[New_Project|New Project]]''' setup, choose **Import Script**.
2. Preserve scene formatting, dialogue, and stage directions.
* Inside the [[Editor|Editor]]: **File → Import → Script** (adds to the current project).
3. Reduce setup time by automatically generating scenes from imported content.
4. Support for popular formats such as Final Draft, Fountain, and PDF.
5. Enable AI to immediately begin generating visuals and storyboards from your script.


== Workflow for Script Import ==
== Supported Formats ==
1. **Open the Script Import Tool**   
* '''[[Final_Draft|Final Draft (FDX)]]''' – preserves scene numbers, title page, and notes where available.
  Navigate to the [[Import_Script|Script Import]] option in the project dashboard.
* '''[[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).


2. **Select Your File**  
== How Imports Are Structured ==
  Upload from your computer or import directly from integrated services (e.g., Google Drive, Dropbox).
* Script elements are mapped to the ACT 3 hierarchy: '''[[Acts|Act]] → [[Scenes|Scene]] → [[Shots|Shot]]'''.   
* '''Scene Headings''' (e.g., INT./EXT.) become [[Scenes|Scene]] cards. 
* '''Action & Dialogue''' flow into the [[Script_Editor|Script Editor]] with speaker attribution. 
* '''Beat Markers''' (from Fountain/Markdown) populate [[Story_Beats|Story Beats]]. 
* Optional page/line notes become [[Annotations|annotations]] in the [[Editor]].


3. **Choose File Format**  
== How to Use ==
  Supported formats include:
# Open '''[[Import_Script|Import Script]]''' from the project creation flow or the [[Editor]].
  * **FDX** – Final Draft.
# Choose your file type: [[Final_Draft|FDX]], [[Fountain]], [[Markdown_Support|Markdown]], or [[Plain_Text|TXT]].  
  * **Fountain** – Plain text screenplay format.
# Select parsing options:
  * **PDF** – Screenplay exports from other tools.
## Map # headings to [[Story_Beats|beats]] (Markdown/Fountain). 
  * **TXT/DOCX** – Basic text files.
## Preserve original scene numbers. 
## Detect languages for [[Subtitles|subtitles]] and [[Dubbing|dubs]].
# 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.


4. **Map Script Structure** 
== Formatting Hints (For Best Results) ==
  Review and confirm:
* Use proper '''Scene Headings''' (e.g., `INT. LAB – NIGHT`) so the parser can segment reliably.
  * Scene headings (INT./EXT.).
* Keep character names on their own lines in ALL CAPS for accurate dialogue mapping.
  * Action descriptions.
* In Markdown/Fountain, use `#` / `##` for beats and sub‑beats to seed [[Story_Beats|Story Beats]]. 
  * Dialogue and character names.
* Avoid embedding images in text imports—attach reference art separately to [[Storyboard_Panels|Storyboard & Panels]].


5. **Auto-Generate Scenes**  
== After Import: Next Steps ==
  ACT 3 AI will create individual scene entries in your [[Editor|Editor]] for further editing.
* Open the [[Timeline|Timeline]] to arrange scenes and add transitions.
* Cast roles in [[Characters|Characters]] and assign [[Digital_Actors|Digital Actors]]. 
* 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]]. 
* Finish and [[Build_Video|Build Video]]; then use [[Export_Script|Export Script]] / media export as needed.


6. **Apply AI Enhancements (Optional)**  
== Troubleshooting ==
  Use [[AI_Wizard|AI Wizard]] to:
* '''Missing scenes or wrong splits''' → Check scene heading syntax; re‑run import with “Preserve scene numbers.”  
  * Expand descriptions.
* '''Dialogue misattributed''' → Ensure character names are uppercase and on their own lines.
  * Add visual details.
* '''Excessive paragraphs in one scene''' → Add blank lines between action blocks for clearer segmentation.
  * Suggest alternative dialogue.
* '''Non‑English scripts''' → Enable language detection to prep [[Subtitles|subtitles]] and [[Dubbing|dubbing]] tracks.


7. **Save & Organize**   
== Credits & Storage ==
  Store the imported script in the **Script** section of your [[Project_Structure|Project Structure]].
* 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]]).


== Supported Integrations ==
== Privacy & Rights ==
1. **Final Draft** – Direct import of .fdx files.
* Imported files are stored within your [[Organization|Organization]] and follow project‑level permissions.
2. **Google Docs** – Import via copy/paste or export.
* Use only material you have the rights to process; see [[Documentation|Documentation]] → Legal/Usage.
3. **Dropbox / Google Drive** – File-based imports.
4. **Screenwriting Software Exports** – Celtx, WriterDuet, StudioBinder.


== Best Practices ==
== See Also ==
1. Use properly formatted screenplays for best auto-parsing results.
* [[New_Project|New Project]] 
2. Double-check imported scene breaks and character names.
* [[Script_Editor|Script Editor]] 
3. Apply consistent scene naming for smooth AI generation.
* [[AI_Wizard|AI Wizard]] 
4. Keep an untouched copy of your original script for reference.
* [[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]]


== Related Pages ==
[https://act3ai.com/contact Contact Us] if you have any problems using our product, or if you have questions.
* [[Import_Script|Import Script]]
* [[AI_Wizard|AI Wizard]]
* [[Editor|Editor]]
* [[Project_Structure|Project Structure]]
* [[Version_Control|Version Control]]
* [[Creating_Movies|Creating Movies]]

Revision as of 08:54, 15 August 2025

Import Script

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

Supported Formats

  • Final Draft (FDX) – preserves scene numbers, title page, and notes where available.
  • Fountain – plain‑text screenplay syntax.
  • Markdown – headings and lists mapped to scenes and beats.
  • Plain Text – best‑effort parsing with format hints.
  • (Optional) PDF – when enabled, uses OCR + heuristics (review carefully after import).

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, Fountain, Markdown, or TXT.
  3. Select parsing options:
    1. Map # headings to beats (Markdown/Fountain).
    2. Preserve original scene numbers.
    3. Detect languages for subtitles and dubs.
  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=264"