@osmo.inc/cli 0.1.24 → 0.1.25
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/DEPLOY.md +36 -1
- package/README.md +5 -0
- package/dist/osmo.js +3019 -286
- package/package.json +4 -4
- package/release.json +11 -11
package/DEPLOY.md
CHANGED
|
@@ -63,7 +63,42 @@ comment made in Studio never appears on the review link.
|
|
|
63
63
|
Use `osmo studio permissions` to inspect source access. Permissions, invitations,
|
|
64
64
|
and revocation work as before; deploying does not make private source public.
|
|
65
65
|
|
|
66
|
-
##
|
|
66
|
+
## Render on cloud GPUs
|
|
67
|
+
|
|
68
|
+
Use cloud rendering when your machine cannot render quickly or agents need to
|
|
69
|
+
submit several projects at once:
|
|
70
|
+
|
|
71
|
+
```sh
|
|
72
|
+
osmo studio deploy --cloud
|
|
73
|
+
osmo jobs RENDER_JOB_ID
|
|
74
|
+
osmo jobs cancel RENDER_JOB_ID
|
|
75
|
+
# Or wait for the finished review link:
|
|
76
|
+
osmo studio deploy --cloud --wait
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
The command uploads the revision and returns a durable job ID. You can disconnect
|
|
80
|
+
after submission; `--wait` only keeps the local command waiting. It publishes to
|
|
81
|
+
the same project and review link as regular deploy. Cloud rendering uses playable
|
|
82
|
+
`Video.src` assets, so upload any required assets with the project.
|
|
83
|
+
|
|
84
|
+
Cloud rendering consumes paid plan allowance or purchased credits. The free plan's
|
|
85
|
+
allowance cannot fund it. Basic allows up to 10 active jobs, Pro 25, and Max 50;
|
|
86
|
+
purchased credits without a paid plan allow 10. Workspace renders use the paying
|
|
87
|
+
seat's limit. Jobs beyond the account limit or available GPU capacity wait in the
|
|
88
|
+
queue. These are account ceilings, not a guarantee of immediately available GPUs.
|
|
89
|
+
|
|
90
|
+
Only active preparation, rendering, and encoding consume allowance. Queueing and
|
|
91
|
+
upload time are free. Failed renders are free; infrastructure retries charge only
|
|
92
|
+
the successful attempt. Cancelling a running render consumes its acknowledged
|
|
93
|
+
processing time. Reusing an identical successful render is free. Jobs reserve
|
|
94
|
+
allowance before starting and never consume more than that reservation.
|
|
95
|
+
|
|
96
|
+
Cloud output supports up to 3840×2160 (or portrait), 60 fps, 10 minutes, and 20 GiB.
|
|
97
|
+
Source files remain limited to 2 GiB each, with a 20 GiB project total. A queued job
|
|
98
|
+
expires after 24 hours. Availability and rates are controlled by the service;
|
|
99
|
+
`--json` includes the job's payer and usage information.
|
|
100
|
+
|
|
101
|
+
## Supported video uploads
|
|
67
102
|
|
|
68
103
|
Upload MP4 with H.264 8-bit 4:2:0 video and optional AAC audio, up to 2 GiB.
|
|
69
104
|
Files are uploaded as supplied; export a compatible MP4 from your video tool
|
package/README.md
CHANGED
|
@@ -47,6 +47,11 @@ not runnable local projects: media remains as URLs, and no Git history or cloud
|
|
|
47
47
|
sync connection is created. Pass a folder argument to override the destination.
|
|
48
48
|
Cloud operations require login and retain existing source permissions.
|
|
49
49
|
|
|
50
|
+
On a machine with limited GPU power, use `osmo studio deploy --cloud` to submit
|
|
51
|
+
the render to Osmo's GPUs using paid allowance or credits. Add `--wait` to wait
|
|
52
|
+
for the review link, or follow the returned job with `osmo jobs JOB_ID`.
|
|
53
|
+
See the [cloud rendering guide](https://unpkg.com/@osmo.inc/cli/DEPLOY.md).
|
|
54
|
+
|
|
50
55
|
## Share a video and collect feedback
|
|
51
56
|
|
|
52
57
|
Upload a video from any tool and get a review link with timestamped comments and
|