Skip to content

v0.1.0

Choose a tag to compare

@HaD0Yun HaD0Yun released this 14 Aug 18:54
· 342 commits to main since this release

First tagged release. CozyClay restarts its version line at 0.1.0 — the studio is real and usable, but the scene format and the ARDY bridge contract are still moving, and the version number should say so.

npx cozyclay

Highlights

Scenes are documents. The hierarchy holds named scenes you can create, switch, duplicate and delete. Each one owns its own set, cast and camera work — moving an actor in one scene no longer moves it in every other.

Cuts. The timeline is no longer one continuous take. Shot blocks are placed freely, may leave gaps, and can be removed down to none; playback hard-cuts at their edges, and frames outside any shot leave the camera to you.

One camera surface. Each shot owns its camera: keys, follow, and a drawn dolly rail with an authored start point, a dolly speed limit and a pitch offset. The rail rides inside the shot that owns it, edited from a single bar under the timeline instead of two competing panels.

Motion generation, locally. The ARDY bridge keeps its HTTP contract but now runs on this machine when no CCLAY_ARDY_HOST is set — npm run ardy:setup provisions everything into ~/.cozyclay/. A persistent warm worker turns same-prompt regeneration from ~160 s into ~0.4 s on Apple Silicon.

Video providers. Runway, Seedance, Kling and Veo adapters sit behind one provider-neutral bridge; the request is conditioned on the staged shot's framing, duration and subject rather than whatever the viewport happens to show.

Video to pose keys. Extraction lands as ordinary cozyclay.pose.v1 keys, so the timeline, IK layer and generation path all apply unchanged. UI wiring is still open — see #11.

Fixes

  • Recorded MP4s reported a duration 30× short, because mdhd.duration was written in the movie timescale instead of the media timescale. Every Record export was rejected as a reference video; both the muxer and the download path are fixed. (#13)
  • tools/ardy/cclay_motion_edit.py could not be parsed from a fresh clone. (#7)

Notes

  • npm carries older 1.x builds from before this reset. 0.1.0 is the current line; treat 1.x as retired.
  • Requires Node.js 22+. Motion generation is optional and off until you point it at a machine that can run it.