@lovstudio/dsh-video-studio

Service API, configuration, and extension points

All HTTP routes live under /video-studio/. The DSH host checks the connection service's requestRejection() before serving either API or static files. The browser has no API secrets. Media reads support byte ranges and HEAD for seeking.

Endpoint	Behavior
GET api/capabilities	Actual ASR and rendering availability
GET api/projects	Saved projects
PUT api/projects/:id	Validate and atomically save a project
POST api/assets	Stream a media upload into the managed asset store
GET media/:id	Authenticated managed media, including Range requests
POST api/render	Queue an immutable project snapshot for MP4 export
POST api/asr	Queue a transcription for an uploaded asset
GET api/jobs/:id	Job state and progress
POST api/jobs/:id/cancel	Cancel queued or running work
GET exports/:id.mp4	Download a completed render

For asset upload, the body is the binary file; query fields describe name, kind, duration, and optional width/height. Projects use versioned frame-based data. The host accepts only managed asset references for rendering. Each render receives a temporary loopback media server exposing its snapshot's asset allowlist, without giving Chromium the user's DSH login cookie.

ASR requires explicit server configuration. Choose a provider/model supporting timestamped segments:

export DSH_VIDEO_ASR_ENDPOINT='https://your-provider.example/v1/audio/transcriptions'
export DSH_VIDEO_ASR_MODEL='your-timestamp-capable-model'
export DSH_VIDEO_ASR_FORMAT='diarized_json' # or verbose_json