# Host export presets / templates

The panel asks the host app to render the active sequence/comp to a temp file
(audio for transcription, full video for cloud burn-in). This is **fully
automatic** for end users who run the CaptionForge installer — nothing to set up by hand.

## Premiere Pro — `.epr` presets (bundled, zero setup)

`captionforge-audio.epr` and `captionforge-video.epr` live in this folder and are shipped
inside the extension. `host/captionforge_1_6_12.jsx` renders with
`seq.exportAsMediaDirect(out, <this .epr>, 0)`, reading the preset **by path** —
Premiere never has to import anything. These files ARE committed (don't delete
them).

To regenerate one (rarely needed): File → Export → Media → pick the format
(Waveform Audio for audio, H.264 1080p for video) → Save Preset → copy the
resulting `.epr` here with the matching name.

## After Effects — output modules (auto-configured, zero setup)

AE has no `.epr`; it uses named Output Module templates. `host/captionforge_1_6_12.jsx`
configures the output module **inline at runtime** via `OutputModule.setSettings`
(AE 16.0 / CC 2019+) — audio-only WAV for transcription, H.264 video+audio for
burn-in — and also `saveAsTemplate`s them as `CaptionForge Audio` / `CaptionForge Video` for
good measure. No manual template creation is required.

Fallback chain if a particular AE build rejects the inline settings: an existing
`CaptionForge Audio` / `CaptionForge Video` template → AE's built-in `Lossless` (video) →
a one-line manual-template error pointing the user to Edit → Templates → Output
Module.
