tlRender
tlRender is an open source library for building playback and review applications for visual effects, film, and animation.
The library can render and playback timelines with multiple video clips, image sequences, audio clips, and transitions. Examples are provided for integrating the library with OpenGL applications.
The library is written in C++ and uses the CMake build system, with Python bindings on PyPI:
pip install tlRender
These screenshots show an example application built with tlRender. The application is comparing two images with a wipe and horizontal layout.
Features:
- Support for timelines, image sequences, movies, and audio files
- A/B comparison with wipe, overlay, and difference modes
- Color management with OpenColorIO
- Multi-track audio with variable speed and reverse playback
- Experimental support for USD files
- Available for Linux, macOS, and Windows
Quick start
A window that plays a timeline, movie, or image sequence given on the command line.
C++
#include <tlRender/UI/Init.h>
#include <tlRender/UI/Viewport.h>
#include <tlRender/Timeline/Player.h>
#include <ftk/UI/App.h>
#include <ftk/UI/MainWindow.h>
#include <iostream>
using namespace ftk;
int main(int argc, char** argv)
{
try
{
// Create the context and application.
auto context = Context::create();
tl::ui::init(context);
auto input = CmdLineArg<std::string>::create(
"input", "A timeline, movie, or image sequence.");
auto app = App::create(
context, argc, argv, "simple", "Simple player example.", { input });
if (app->hasCmdLineHelp())
return 0;
// Create a timeline and a player for it.
auto timeline = tl::Timeline::create(context, Path(input->getValue()));
auto player = tl::Player::create(context, timeline);
// Show the player in a window.
auto window = MainWindow::create(context, app);
auto viewport = tl::ui::Viewport::create(context);
viewport->setPlayer(player);
window->setWidget(viewport);
// Start playback and run the application.
player->setPlayback(tl::Playback::Forward);
app->run();
}
catch (const std::exception& e)
{
std::cout << "ERROR: " << e.what() << std::endl;
return 1;
}
return 0;
}
Python
The same player, after pip install tlRender:
import feather_tk as ftk
import tlrender as tl
import sys
# Create the context and application.
context = ftk.Context()
tl.ui.init(context)
input = ftk.CmdLineArgString("input", "A timeline, movie, or image sequence.")
app = ftk.App(context, sys.argv, "simple", "Simple player example.", [input])
if app.hasCmdLineHelp:
sys.exit(0)
# Create a timeline and a player for it.
timeline = tl.Timeline(context, ftk.Path(input.value))
player = tl.Player(context, timeline)
# Show the player in a window.
window = ftk.MainWindow(context, app)
viewport = tl.ui.Viewport(context)
viewport.player = player
window.widget = viewport
# Start playback and run the application.
player.playback = tl.Playback.Forward
app.run()
The examples directory has fuller players in both languages, with playback controls and a timeline.
Web Player
An experimental build of the example player runs in the browser, playing movies with the WebCodecs API:
The "url" query plays a movie from any host that allows cross-origin range reads.
Python
The Python bindings are one wheel per platform for CPython 3.12 and later, built on the feather-tk wheel, which pip installs with them, and OpenTimelineIO:
import opentimelineio as otio
import feather_tk as ftk
import tlrender as tl
The wheel has only the FFmpeg codecs that need no patent license: AV1, APV,
VP8 and VP9, MPEG-2 and MPEG-4, MJPEG, FFV1, CineForm, UT Video, HuffYUV,
MagicYUV, Dirac, PNG, v210, and the FLAC, Opus, Vorbis, ALAC, MP3 and PCM
audio codecs. H.264, HEVC, ProRes, DNxHD, DV and AAC are not in it, so a
camera movie or anything else carrying them does not open with the wheel
alone. Two ways to play them: install FFmpeg yourself, and tlRender reads
them with the ffmpeg and ffprobe commands on PATH; or build from
source, where the codecs are compiled in.
OpenTimelineIO does not publish wheels for every platform tlRender does, so on some pip builds it from source, which needs a C++ compiler.
The Python examples show the API in use. The wheel also carries the C++ libraries, headers, and CMake package, so a project with its own bindings can build against the same installation:
cmake -DtlRender_DIR="$(python -c "import tlrender; print(tlrender.get_cmake_dir())")" ...
tlRender's package finds feather-tk's in the feather_tk package beside it.
Building Dependencies
A CMake super build script is provided to build all of the dependencies from source.
Build options go in etc/Config/local.cmake, which is not tracked. For
example, to enable USD (building USD also requires Python 3):
set(TLRENDER_USD ON CACHE BOOL "")
Required dependencies:
Optional dependencies:
Building on Linux
Requirements:
- Git
- CMake 3.31
Debian
Install system packages:
sudo apt-get install build-essential git cmake xorg-dev libglu1-mesa-dev mesa-common-dev mesa-utils libasound2-dev libpulse-dev libpipewire-0.3-dev libva-dev libdrm-dev libwayland-dev wayland-protocols libxkbcommon-dev libegl1-mesa-dev libdecor-0-dev
The Wayland packages are optional; without them SDL is built with X11 only and runs through XWayland on a Wayland desktop.
Rocky 9
Install system packages:
sudo dnf install git libX11-devel libXrandr-devel libXinerama-devel libXcursor-devel libXi-devel mesa-libGL-devel pipewire-devel libva-devel libdrm-devel wayland-devel wayland-protocols-devel libxkbcommon-devel mesa-libEGL-devel libdecor-devel
Rocky 8
Install system packages:
sudo dnf install git libX11-devel libXrandr-devel libXinerama-devel libXcursor-devel libXi-devel mesa-libGL-devel pipewire-devel libva-devel libdrm-devel wayland-devel wayland-protocols-devel libxkbcommon-devel mesa-libEGL-devel
Install newer compiler:
sudo dnf install gcc-toolset-13
Enable newer compiler:
scl enable gcc-toolset-13 bash
NVIDIA hardware decoding loads the driver's CUDA library at run time. On RHEL family systems that is a separate package:
sudo dnf install nvidia-driver-cuda-libs
Build
Clone the repository:
git clone https://github.com/grizzlypeak3d/tlRender.git
Run the super build script:
sh tlRender/sbuild-linux.sh
Try running the tlplay application:
./build-Release/bin/tlplay/tlplay tlRender/etc/SampleData/MultipleClips.otio
Example running gcovr for code coverage:
gcovr -r ../../../../lib --html --object-directory lib --html-details --output gcov.html lib/tlCore lib/tlIO lib/tlTimeline
Building on macOS
Requirements:
- Git
- Xcode
- CMake 3.31
Clone the repository:
git clone https://github.com/grizzlypeak3d/tlRender.git
Run the super build script:
sh tlRender/sbuild-macos.sh
Try running the tlplay application:
./build-Release/bin/tlplay/tlplay tlRender/etc/SampleData/MultipleClips.otio
These aliases are convenient for switching between architectures:
alias arm="env /usr/bin/arch -arm64 /bin/zsh --login"
alias intel="env /usr/bin/arch -x86_64 /bin/zsh --login"
Building on Windows
Requirements:
- Git (https://git-scm.com)
- Visual Studio 2022
- CMake 3.31
- NASM (https://www.nasm.us) for compiling FFmpeg and libjpeg-turbo.
- MSYS2 (https://www.msys2.org) for compiling FFmpeg.
- Strawberry Perl (https://strawberryperl.com/) for compiling network support.
- Python 3.11 for compiling USD.
Open the Visual Studio command console "x64 Native Tools Command Prompt for VS 2022". This can be found in the Start menu, in the "Visual Studio 2022" folder.
Clone the repository:
git clone https://github.com/grizzlypeak3d/tlRender.git
Run the super build script:
tlRender\sbuild-win.bat
Try running the tlplay application:
set PATH=%CD%\install-Release\bin;%PATH%
.\build-Release\bin\tlplay\Release\tlplay tlRender\etc\SampleData\MultipleClips.otio
Metadata
Release files for tlRender 0.24.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| tlrender-0.24.0.tar.gz | 44.4 MB | Details |
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| tlrender-0.24.0-cp312-abi3-win_amd64.whl | CPython 3.12 | abi3 | Windows x86-64 | Details |
| tlrender-0.24.0-cp312-abi3-manylinux_2_28_x86_64.whl | CPython 3.12 | abi3 | Linux glibc 2.28+ x86-64 | Details |
| tlrender-0.24.0-cp312-abi3-manylinux_2_28_aarch64.whl | CPython 3.12 | abi3 | Linux glibc 2.28+ ARM64 | Details |
| tlrender-0.24.0-cp312-abi3-macosx_11_0_arm64.whl | CPython 3.12 | abi3 | macOS 11.0+ ARM64 | Details |
| tlrender-0.24.0-cp312-abi3-macosx_10_15_x86_64.whl | CPython 3.12 | abi3 | macOS 10.15+ x86-64 | Details |
Total release size: 257.1 MB
Release files / tlrender-0.24.0.tar.gz
| Download URL | tlrender-0.24.0.tar.gz |
|---|---|
| Size | 44.4 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9e04ba3b3f215f5b2f461b27608486cb0bf5b9c5076bfd7d5bbafa30df57712a
|
|
BLAKE2b-256 checksum How to use checksums |
d0945610fff15b478b9d1ced621667f034ac1cb3013e1c889a3d57edeae57211
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / tlrender-0.24.0-cp312-abi3-win_amd64.whl
| Download URL | tlrender-0.24.0-cp312-abi3-win_amd64.whl |
|---|---|
| Size | 35.6 MB |
| Tags | CPython 3.12 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
3926c448984b9526211adef49381aaa3a94eb582c92214adaf480a26bde9e632
|
|
BLAKE2b-256 checksum How to use checksums |
93cee730a015141a5cdf048f3ad0eec7b738b9bf6f2c8d36852769b7938f9fa3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / tlrender-0.24.0-cp312-abi3-manylinux_2_28_x86_64.whl
| Download URL | tlrender-0.24.0-cp312-abi3-manylinux_2_28_x86_64.whl |
|---|---|
| Size | 48.7 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
6caa661b9a1120b45211aa8a3c137999b2b5514a6a8197656798f6bdffa91370
|
|
BLAKE2b-256 checksum How to use checksums |
c94420ea49b29c01471b15ae4af16f5c03c8aeed4f186b049006c4afd488be5b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / tlrender-0.24.0-cp312-abi3-manylinux_2_28_aarch64.whl
| Download URL | tlrender-0.24.0-cp312-abi3-manylinux_2_28_aarch64.whl |
|---|---|
| Size | 46.1 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
1c35290b08b83a7223edd97b8044742f1696630486ab5d120e8282ff94193e94
|
|
BLAKE2b-256 checksum How to use checksums |
662307023875c10fe0d68184d8f56b31333c2548ab38a725a376aa4bd431e8f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / tlrender-0.24.0-cp312-abi3-macosx_11_0_arm64.whl
| Download URL | tlrender-0.24.0-cp312-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 38.2 MB |
| Tags | CPython 3.12 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
a7d6105958698f42b366a130353f9dd0cff1c992c85e35022ff992c96103fd0b
|
|
BLAKE2b-256 checksum How to use checksums |
7217152c2cfab60e12d3ba540154fa4d56fd799655c52a0ebaf0da0217b0d896
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency logRelease files / tlrender-0.24.0-cp312-abi3-macosx_10_15_x86_64.whl
| Download URL | tlrender-0.24.0-cp312-abi3-macosx_10_15_x86_64.whl |
|---|---|
| Size | 44.1 MB |
| Tags | CPython 3.12 abi3 macOS 10.15+ x86-64 |
|
SHA-256 checksum How to use checksums |
299b9cae9f669eed13f2e173d92fdcf09072c2875afdc86fe29fda374f1f70b2
|
|
BLAKE2b-256 checksum How to use checksums |
3d439cf8ce34367827832780a3091b4b33483d02bfec430c4a5387a179a7cb7a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 1, 2026.
Transparency log