> For the complete documentation index, see [llms.txt](https://autoedit.gitbook.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://autoedit.gitbook.io/documentation/master-1.0.6/export/export/edl-export.md).

# EDL export

## Component/part description

## Related projects

## Implementations Options considered

## Current implementation

## What needs refactoring

## Module: EDL Composer module in autoEdit 2.

To extrapolate as standalone module and publish to npm. Add tests. Decide on test suite for these modules. <http://www.autoedit.io/jsdoc_docs/module-edl_composer.html>

Module figured out by reverse engineering export EDL from FCP7. supports limited amount of feature, eg only edit. No transitions.

connected with spec of paper-edit json.

[EDL tutorial](/documentation/master-1.0.6/appendix/edl-format.md)

EDL specifications <https://documentation.apple.com/en/finalcutpro/usermanual/index.html#chapter=96%26section=1%26tasks=true>

<http://www.edlmax.com/EdlMaxHelp/Edl/maxguide.html>

Limitations of EDL. not multi-track sequence. Only one video track. If given a multitrack EDL JSON, eg b-roll. (currently not a use case/feature for autEdit 2 or 3) could create multiple EDL for each track, with track name/number next to it. (this might not be necessary, XML option might be better suited, see below). Rationale is that for other use case, eg app for making video slideshow multi-track video is needed. Having a module that can tackle this could add more flexibility in those scenarios. Such as when combining with computational photography, eg programmatically matching transcription video interview track with B-roll of cutaways images.

Another edl limitation. No support for text titles, while xml does.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://autoedit.gitbook.io/documentation/master-1.0.6/export/export/edl-export.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.