01
Record in OBS. Pick it up in Blender.
Keep a recording’s details with the footage when you start working in Blender. Even if you move the file, Blender can recognize the recording OBS already registered.
OBS → Blender walkthrough02
Edit in Kdenlive. Render in Blender. Keep the connection.
Keep track of which take went into a Blender render, starting with footage registered in Kdenlive. See when changed inputs make a result stale, and find the recorded render through OpenAssetIO.
Kdenlive → Blender → Manager walkthrough03
Move media once. Reuse what the apps know.
Find a moved clip and confirm its new location once. Other participating applications can reuse that location from the same local production. If several files match, you choose the right one.
See how applications recognize shared mediaIntegrations and demos
Try it in the applications you already use.
Point each application at the same production file (.pproj), and what one of them learns about your media is there for the next. Your edits, compositions and sessions stay in their usual project files.
Video Sequencer · Rendering
Blender
Moved your footage? Bring it back into the Sequencer and keep working, with Blender remembering exactly what went into every render.
- Reconnect moved movies, sounds and image sequences
- See which takes a render was made from
- Notice when changed footage leaves a render out of date
Video editing
Kdenlive
Renamed or reorganized your clips? Reopen the edit and pick up where you left off. Kdenlive also tells you when a proxy no longer matches its source footage.
Try it in Kdenlive →Recording
OBS Studio
Stop recording, and the take is ready for the next application, details included.
Try it in OBS →Compositing
Natron
Reconnect moved image sequences to the Reader nodes you already have. Your composition stays untouched.
Try it in Natron →Audio
Ardour
Ardour recognizes renamed or moved audio files by what they contain and puts them back into your session.
Try it in Ardour →Compositing · Trial
Nuke 17.0v1
Find moved plates without rebuilding Reader nodes. The trial is prepared but has not yet been run in licensed Nuke, so your run could be the first.
Be the first to try it →Pipelines · OpenAssetIO
Timelines that find their own media
Hand a timeline to another tool and let it locate the footage, even when the original file paths no longer exist. OpenAssetIO connects the application to PostProject.
SDK scenario · Shared identity
Reuse a take recorded by another app
Recognize an existing clip and retain its identity in the next application. When several recorded assets match, the application asks you to choose.
See the asset-reuse recipe →SDK scenario · Render history
Explain an affected render
A scene references a texture. When the texture changes, inspect why the recorded render is stale. The runnable example keeps scene references separate from the render’s production history.
Follow the scene-and-texture example →Start here
See two applications work together
Follow a tested handoff from start to finish, and watch media knowledge travel from one application to the next.
Good to know
Early pilots, worth the setup
For now you build an extension or a matching application version yourself. Each guide walks you through setup, supported versions and how to remove it again. Start with a test project.
PostProject shares what applications know about your media. It does not convert timelines or copy your files.
For software developers
Give your application a shared memory for media.
Add moved-media recovery and render history without building a separate tracking system for every application. C, C++, Python and command-line interfaces let your software share one local production file and learn what other applications changed. The OpenTimelineIO demo shows how OpenAssetIO finds timeline media through PostProject. Your application stays in control when files are missing or several candidates match.
Start an integration from the Python sample host or C++ sample editor. See how a small application records media and reconnects moved files.
Future possibilities: REAPER and DaVinci Resolve feasibility notes.