Open Source API and interchange format for editorial timeline information.
Main web site: http://opentimeline.io/
Discussion group: https://lists.aswf.io/g/otio-discussion
Slack channel: https://academysoftwarefdn.slack.com/messages/CMQ9J4BQC To join, create an account here first: https://slack.aswf.io/
OpenTimelineIO is currently in Public Beta. That means that it may be missing some essential features and there are large changes planned. During this phase we actively encourage you to provide feedback, requests, comments, and/or contributions.
OpenTimelineIO is an interchange format and API for editorial cut information. OTIO is not a container format for media, rather it contains information about the order and length of cuts and references to external media.
OTIO includes both a file format and an API for manipulating that format. It also includes a plugin architecture for writing adapters to convert from/to existing editorial timeline formats. It also implements a dependency- less library for dealing strictly with time,
You can provide adapters for your video editing tool or pipeline as needed. Each adapter allows for import/export between that proprietary tool and the OpenTimelineIO format.
Documentation, including quick start, architecture, use cases, API docs, and much more, is available on ReadTheDocs
OpenTimelineIO supports, or plans to support, conversion adapters for many existing file formats, such as Final Cut Pro XML, AAF, CMX 3600 EDL, etc.
OTIO also supports several other kinds of plugins, for more information see:
The python-wrapped version of OpenTimelineIO is publicly available via pypy. You can install OpenTimelineIO via:
pip install opentimelineio
For detailed installation instructions and notes on how to run the included viewer program, see: https://opentimelineio.readthedocs.io/en/latest/tutorials/quickstart.html
import opentimelineio as otio
timeline = otio.adapters.read_from_file("foo.aaf") for clip in timeline.each_clip(): print(clip.name, clip.duration())
There are more code examples here: https://github.com/PixarAnimationStudios/OpenTimelineIO/tree/master/examples
Also, looking through the unit tests is a great way to see what OTIO can do: https://github.com/PixarAnimationStudios/OpenTimelineIO/tree/master/tests
OTIO includes a viewer program as well (see the quickstart section for instructions on installing it):
If you want to contribute to the project, please see: https://opentimelineio.readthedocs.io/en/latest/tutorials/contributing.html
You can get the latest development version via:
git clone [email protected]:PixarAnimationStudios/OpenTimelineIO.git OpenTimelineIO
You can install development dependencies with
pip install .[dev]
You can also install the PySide2 dependency with
pip install .[view]
Currently the code base is written against python2.7, python3.7 and python3.8, in keeping with the pep8 style. We ask that before developers submit pull request, they:
make test-- to ensure that none of the unit tests were broken
make lint-- to ensure that coding conventions conform to pep8
make coverage-- to detect code which isn't covered
Additionaly, to reproduce CI failures regarding the file manifest, run:
make manifestlocally to run the python
To enable C++ code coverage reporting via gcov/lcov for builds, set the following environment variables:
When building/installing through
setup.py, these variables must be set before running the install command (
pip install .for example).
OpenTimelineIO is open source software. Please see the LICENSE.txt for details.
Nothing in the license file or this project grants any right to use Pixar or any other contributor’s trade names, trademarks, service marks, or product names.
For more information, please visit http://opentimeline.io/ or https://github.com/PixarAnimationStudios/OpenTimelineIO or join our discussion forum: https://lists.aswf.io/g/otio-discussion