Export: renders and social delivery

Ember renders in two places: a Resolve timeline through Resolve's render engine, or an Ember project through Ember Engine. Ember Engine is part of Pro and Max and is installed once from the app.

Export writes video files. Caption text, Styles and polish stay on the timeline; Ember does not write SRT, VTT, ASS, JSON or CSV files from Export.

• Open what you want to render: a Resolve timeline with Resolve running, or an Ember project with Ember Engine installed.
• Set the range with the playhead or an In and Out. Export renders the clips inside that range.
• Check that the clips you want are enabled. A disabled clip stays out of the picture and out of the files.
• Choose Folder as the destination. Posting to a social account is the other destination, and it needs an account that is live.

The form runs down the left of the Export page, and Start sits under it. In a Resolve session, Preset is the first row; the rows below it change with the destination.

Preset

Ember includes its own presets and also lists the ones in Resolve's Deliver page, so a preset you built there can be used as it is. In an Ember project the same first row holds Ember Engine's delivery rows instead: Optimized, with Rate Control and Bit Rate when it is off, and Slow mode.

Export To

Folder writes video files to a folder. Social posts the rendered clips to the accounts you connected in Settings.

Path

The folder Ember writes to. It is remembered as the project's default for the next export.

Naming

Pattern creates numbered names from one naming pattern. Source pre-fills editable names from the first video clip in each range.

Isolation

Resolve's Voice Isolation, applied to one audio track during the render. Raise the amount, then choose the track it should target.

1. Choose Folder as the destination

   The Path row below holds the folder. Export starts in your home folder until you pick one.

2. Name the files

   Use a pattern for a consistent series, or edit each source name when every clip needs its own title.

3. Click Start under the form

   Start is pinned under the form, in the page's footer. A Resolve render hands the jobs to Resolve and returns you to the Main page. An Ember project renders on this computer and stays on the Export page.

In Resolve, the render runs through Resolve's own render queue on the Deliver page, which is where Resolve reports its progress. Ember's Export page keeps its own Render Queue: one card per render started in this window, with progress and a Stop while it runs, and its files when it ends. A finished job plays its file or shows it in its folder. While an Ember project is open, the queue also lists deliveries made by an earlier window or from the command line.

The Main page's Export button shows the run while it works, with a percent as Resolve reports one. Click it to cancel.

When the render finishes, Ember checks that each output is a readable media file. A render through Resolve restores the page, the In/Out marks and the render location it changed to do the work.

Connect accounts in Settings > Account > Social, not on the Export page. Until a platform is live, the Social destination reads Social, Coming later and stays disabled, and that platform's row in Settings keeps its Connect button disabled. Posting is part of Pro and Max.

Platforms

Which connected accounts receive the rendered clips. A platform that is not live yet says so in its row and cannot be ticked.

Description

Auto writes a concise description for each clip from what is said in that clip. Manual uses the text you enter as the description for every clip.

Private

Posts TikTok videos as private, which is required while Ember's TikTok app is unaudited.

A missing connection is reported before rendering starts. If an authorization cannot be renewed, the post fails with the account to reconnect; Ember does not silently skip a platform.

Ember renders each continuous stretch of the timeline as one file. Clips that touch, or that sit closer together than Export's own gap, become one file. Leave a longer gap between clips that should be delivered separately.

The gap is not a setting. When clips sit close, the Export footer shows a warning above Start with the gap it will use.

A montage cut with no gaps is therefore one file, not a failed split.

• A preset cannot be loaded: choose another preset. If the list itself does not load, check that Resolve has a project and timeline open.
• The render could not start: open the Deliver page in Resolve and check its render queue for a blocked job.
• An output cannot be read as media: render it again and check the disk and the preset.
• The files are missing from the folder: confirm the destination and that the render finished writing.
• Isolation is refused or has no effect: it needs Resolve Studio, and the track it targets must exist in the timeline. Open the project in Studio and check the track, or set Isolation to zero and render again.
• A social post fails: reconnect the account in Settings > Account > Social and confirm its publishing permissions, then retry.
• Resolve's page, In/Out marks or render location did not come back: set them again in Resolve. Ember puts back what it changed to render.

Errors name the step that failed and what to change. A failed export never reports a file count it did not write.

Rendering to a folder is available on every plan. Posting to a social account is part of Pro and Max. Rendering an Ember project uses Ember Engine, which Pro and Max include. Rendering a Resolve timeline needs DaVinci Resolve running with the timeline open.

• Ignite: captions and polish in one pass

  The pass that places the captions and the polish. Export renders what it placed.

• Furnace: rough cuts before captions

  Cast chooses the clips and spaces them on the timeline. Export splits and writes them.

• Ember with AI agents

  An assistant can start the render and report the files it wrote, in the same session that made the edit.