@shotstack/cli 0.16.0 → 0.16.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +12 -0
- package/dist/shotstack.js +30 -29
- package/package.json +1 -1
- package/skills/shotstack/SKILL.md +1 -1
package/README.md
CHANGED
|
@@ -99,6 +99,18 @@ shotstack studio my-template.json --output json # emit {"url":"...","shortened":
|
|
|
99
99
|
|
|
100
100
|
When a browser can be launched, the command is silent — the URL only opens in the browser. On a headless server (no `$DISPLAY`, no `xdg-open`), the URL is printed to stdout instead so you can copy it elsewhere.
|
|
101
101
|
|
|
102
|
+
### `shotstack inspect <edit | render-id | video-url>`
|
|
103
|
+
|
|
104
|
+
Draws frames of an edit, a finished render or a video into a contact sheet, in headless Chrome, without rendering. Nothing is charged, and an edit or a video URL needs no API key.
|
|
105
|
+
|
|
106
|
+
```sh
|
|
107
|
+
shotstack inspect edit.json --at 0.5,4,8.05 # a tile per time, written to inspect.jpg
|
|
108
|
+
shotstack inspect edit.json --bars map.json # a tile at every bar line from `analyze --output json`
|
|
109
|
+
shotstack inspect edit.json --at 3 --grid # one still with a grid labelled in output pixels
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
It uses Google Chrome, or Edge or Brave on macOS and Linux. `CHROME_PATH` points it at any other Chromium-based browser. Chrome keeps its sandbox, so a container that blocks the sandbox (running as root, or under Docker's default seccomp profile) needs a non-root user with user namespaces allowed. Only in a disposable container running edits you trust, `SHOTSTACK_CHROME_NO_SANDBOX=1` runs Chrome without its sandbox.
|
|
113
|
+
|
|
102
114
|
### `shotstack ingest <subcommand>`
|
|
103
115
|
|
|
104
116
|
Uploads your own local files (or fetches remote URLs) via the [Ingest API](https://shotstack.io/docs/guide/ingesting-footage/ingest-api/) and hosts them on Shotstack so they can be referenced from an Edit. An Edit can only reference media by URL, so this is how you get a local clip, image, audio file, or font into a render.
|