@osmo.inc/cli 0.1.23 → 0.1.24

package/DEPLOY.md

@@ -39,17 +39,27 @@ osmo studio deploy
 
 The first deployment creates a private cloud project. Its review link is separate
 from source access and opens for anyone who has the link. Later deployments add
-versions to the same review destination. `link` is the stable review URL,
-`versionLink` identifies one version, and `page` is the cloud project URL.
-Use `osmo studio open` for local editing.
+versions to the same review link. The command prints that one link: it shows the
+newest version to anyone who has it, and someone on the project who is signed in
+finds "View project" on it, or "Edit project" with web editing, which opens the
+project itself. With `--json`, `link` is the review URL, `versionLink`
+is this version's own URL, and `page` is the project's page. Use
+`osmo studio open` for local editing.
 
 `osmo studio sync` synchronizes local source and cloud revisions;
-`osmo studio history` lists revisions. In an already connected project, sync
+`osmo studio history` lists revisions and marks the project's versions: a
+sync's or a deploy's. A comment made in Studio in the web goes on the version
+that was the latest at the time; one made on the review link, on the version
+its reviewer watched. In an already connected project, sync
 before and after editing. Deploy refuses unseen cloud changes; sync and inspect
 those changes before trying again. `osmo studio clone PROJECT` copies a project
 you can access into a local folder. These cloud operations need login.
 
-Read local and cloud feedback with `osmo studio comments list --open --json`.
+Read local and cloud feedback with `osmo studio comments list --open --json`:
+the comments from the local Studio, from Studio in the web (anyone on the
+project can comment there, on the live project) and from the review link, each
+with its scene, its time and, for a cloud comment, the version it is on. A
+comment made in Studio never appears on the review link.
 Use `osmo studio permissions` to inspect source access. Permissions, invitations,
 and revocation work as before; deploying does not make private source public.
 

package/README.md

@@ -26,6 +26,11 @@ osmo studio render
 Local editing and rendering need no Osmo account. `open` starts the local browser
 editor and prints its address; it keeps running while you edit. Read the generated
 `AGENTS.md` before authoring with an agent. `render` saves `exports/scene.mp4`.
+Rendering uses the browser-playable `Video.src` by default. Use
+`osmo studio render --original --out exports/final.mov` to select local
+`Video.originalSrc` where set, recommended for final RAW renders.
+Missing originals fail only with this flag;
+clips without `originalSrc` still use `src`. The flag also works with `--at`.
 
 Local Studio supports Apple Silicon macOS and Linux x64/arm64 with glibc. It needs
 Git 2.29+ for project setup and FFmpeg with libx264 plus ffprobe for video rendering.
@@ -91,3 +96,35 @@ login created using `--no-spend`.
 A blocked plan also includes `reason`, `resetsAt`, and guidance in `message`.
 An exhausted plan is a successful status read (exit 0); authentication, network,
 and permission failures exit 1. Raw internal billing units are never returned.
+
+
+### Film resources
+
+Film looks download automatically when a project opens, a look is applied, or a
+scene is rendered. Only the tables needed by that scene and camera profile are
+fetched. Studio shows progress and a Retry action if a download fails; a render
+never silently omits a film effect. Installed tables work offline.
+
+To prepare the entire library for offline use (about 1.16 GiB unpacked):
+
+```sh
+osmo resources get film
+```
+
+Find individual looks with `osmo resources list --type film`, inspect one with
+`osmo resources show ID`, then install it with `osmo resources get ID`.
+`osmo resources install` is an alias for `get`. An individual look installs all
+three camera variants (about 9.4 MiB); automatic downloads fetch only the needed
+variant (about 3.14 MiB).
+
+Film resources install once per user, shared across projects and CLI versions:
+
+- macOS: `~/Library/Application Support/Osmo/resources/film`
+- Linux: `$XDG_DATA_HOME/osmo/resources/film` (default `~/.local/share/osmo/resources/film`)
+- Windows: `%LOCALAPPDATA%/Osmo/resources/film` (resource downloads only; local Studio still needs a supported renderer platform)
+
+`OSMO_FILM_TABLES` overrides that directory, including for native rendering.
+Files are pinned to the CLI's catalogue, checked by size and SHA-256, and written
+atomically. npm updates and uninstall leave these files in place. Film downloads
+need no login. Shaders and 3D models keep their existing project/folder downloads
+and preserve user-modified files; `--out` applies to those resources, not film.

package/SETUP.md

@@ -44,6 +44,14 @@ Cloud sync is optional. For a project already connected to the cloud, sync befor
 and after editing; resolve any conflicts before deploying. To remix an accessible
 shared project, sign in, run `osmo studio clone PROJECT`, then open the local copy.
 
+## Film looks and offline use
+
+Film tables install automatically into a shared per-user Osmo data folder when
+opening projects, changing effects, or rendering. Studio shows download progress
+and Retry. Prepare every look before going offline with `osmo resources get film`
+(about 1.16 GiB); use `osmo resources list --type film` to choose individual looks.
+No separate setup command is needed. CLI updates preserve installed tables.
+
 ## Share an existing video with an AI agent
 
 ```text