· Now
Epitech's end-of-studies project: a Python API in which the scenes are written, backed by a rendering engine in C++. A scene is a program rather than a timeline: shapes are declared, positioned and animated in code, then rendered frame by frame into a video file. It exists because precise timing is tedious in a conventional editor — here every duration, easing curve and dependency is written down, so a video can be re-rendered or edited by changing a line rather than by dragging clips again.
- Python is the whole user surface: the scene API, serialization, easing curves and the dependency scheduler. The C++ engine only renders.
- Nothing is scheduled by hand: each element waits on the one it follows, so inserting a step pushes everything after it along instead of invalidating a column of timestamps.
- Easing curves are first-class — exponential decay, smoothing, rush-from — and apply to any property, gradients included.
- Graphical interface generated automatically from the API, so the same scene can be edited by hand or by code.
- Where it is headed: an AI vibe-edits the video by editing its code — what models do far better than laying out a design — while the generated interface shows what that change did on screen, so the result stays readable without anyone parsing a diff.