The House Wears a Face
README.md
film
The whole timeline, as a cutscene definition: the camera path, its easings, the
fourteen cues, the fades. require("demo.film") returns the definition;
cutscene.play("demo.film") runs it.
It authors only the SHAPE of the movement. Every pose, lens and duration comes
from demo.constants, the same table the spec's shot list is written from, so
a shot restaged there is restaged here, and nowhere is a number written twice.
What is in it
Eighteen camera moves for fourteen shots. One entry per MOVE, which is not one entry per shot: a shot that stops before its window ends, or cuts inside it, is written as its parts. Shot 5 runs its dolly and stops two seconds early, which is the only way a reflection that keeps travelling can be seen to keep travelling. Shot 8 cuts to an 85 mm insert on the glass and back out. Shot 13 arrives on the station a second before the cut, so the cut into shot 14 is a match and not a stumble.
Every move is sine-eased or linear, because the camera is calm and the room is the thing that moves quickly. The one exception is shot 4's 12 cm creep, which is linear on purpose: an eased push that small reads as a wobble.
A check that the moves still sum to the film. The moves are the shot table
divided up, so their durations sum to K.DURATION. If they do not, the module
raises at require time rather than loading: a shot re-timed in one place and not
the other puts every cue after it against a camera that is somewhere else.
Fourteen cues. One per shot, at that shot's authoritative time, each doing exactly one thing: firing the beat every slice registered against.
Cues that live INSIDE a shot are not built here. A slice declares those with
beats.extra(name, t) from its register(), which runs during beats.bind(),
and by then this module is already in the require cache and its cue list is
fixed. The FilmClock component fires them off the film clock instead, which
also re-arms them when the clock is seeked backwards.
onStart resumes the simulation. Every slice's continuous motion is a
component's update(dt), and those do not tick while the simulation is frozen,
which an engine sitting in edit mode is, by default. It resumes rather than
entering play mode on purpose: play mode locks the VFS, and this world is shared
with other authors.
Running it
Through /source/demo/play.luau, and only through it. That script stops whatever
is playing, rebinds every slice, returns every slice to its shot-1 state, and
then hands the clock over. Running it twice must produce the same hundred
seconds.