DSH Plugins Marketplace

DSH Plugins

Plugins

/

dsh-studio-film

d

dsh-studio-film

Manifest valid

Film and video studio, offering film projects, media resources, and local service connections.

UI (client)hasBundlePatch

dsh-studio-film

简体中文

Repository

  • Repository name: dsh-studio-film
  • Repository description: PRINTFILM studio adapter for scripts, episodes, storyboards, asset management and video production tasks.
  • Source: https://github.com/1997liuyh-boop/dsh-studio-film
  • Upstream: https://github.com/yi1108/printfilm, locked in UPSTREAM.json.

Features

  • Manage projects, stories, scenes, characters and production notes.
  • Organize episodes and shots with image direction, dialogue, duration and status.
  • Manage character, scene, prop, image, audio and video assets.
  • Bridge the original application's generation, preview, export and task status into DSH.
  • Use a bound DSH session for messages, model state, tool results and stop operations.
  • Show real service and database failures with a retry path; no sample data is presented as connected.

Installation

Install the control bundle, then this exact studio tag through the official Desktop plugin manager after fully quitting Desktop:

& "<Desktop install directory>\resources\runtime\cli\bin\dsh.cmd" plugin --profile desktop add "github:1997liuyh-boop/dsh-studio-library#v0.1.3"
& "<Desktop install directory>\resources\runtime\cli\bin\dsh.cmd" plugin --profile desktop add "github:1997liuyh-boop/dsh-studio-film#v0.2.5"
& "<Desktop install directory>\resources\runtime\cli\bin\dsh.cmd" plugin --profile desktop list

Verify main: lib/index.js, exports./client: lib/client.js, dsh.bundle.patch: ./cordis.patch.yml and the built static entry. Install and configure the PRINTFILM service, database and video-generation service separately, then restart Desktop.

Service setup

The plugin does not ship the PRINTFILM service. Prepare the pinned upstream source in a new absolute directory, then follow its own documentation to install dependencies and start the service:

node scripts/prepare-upstream.mjs film "C:\work\printfilm"

Configure the DSH host with printfilmUrl, or set DSH_STUDIO_PRINTFILM_URL to the service origin. The default origin is http://127.0.0.1:33102.

Started by the studio library (recommended)

PRINTFILM needs PostgreSQL, a Garnet cache, a Python backend and two web servers, so it cannot ship inside the plugin. Once the app, its runtimes and data are prepared locally, tell the studio library where they are in the profile's cordis.patch.yml; it then starts the whole stack itself (dsh-studio-library 0.1.20 or later), with no PowerShell start script:

- id: dsh-studio-projects
  config:
    printfilmService:
      appDirectory: D:/studio-apps/printfilm      # upstream source: backend, frontend/dist, admin/dist, .venv
      runtimeDirectory: D:/studio-runtime         # pgsql, garnet, dotnet, node, ffmpeg
      dataDirectory: D:/studio-data/printfilm     # runtime.json (databasePassword, secretKey), postgres, garnet

The environment variables DSH_STUDIO_PRINTFILM_APP, DSH_STUDIO_PRINTFILM_RUNTIME and DSH_STUDIO_PRINTFILM_DATA work as well. With that in place:

  • The stack starts when the studio is installed or enabled. The console studio list shows the connection state, offers a Start button when offline and shows the failure reason on that row (missing file, port in use, process exit with the last error-log line).
  • Start order: database (35432) → cache (36379) → backend API (33104) → web (33102) → admin (33103). Ports that are already listening are reused; only the missing parts are started.
  • Logs are written to dataDirectory/logs. Quitting Desktop does not stop the running services.

Without these three directories the studio library starts nothing and the console shows "no start script configured"; start the upstream service, database and video-generation provider yourself before opening the studio.

Requirements and limits

The adapter does not download personal projects, import accounts or start external services. Service and database failures limit the studio to status and retry views. Third-party applications and assets keep their own licenses; see THIRD_PARTY_NOTICES.md.

License and sources

MIT licensed. The upstream source, locked revision and adaptation patches are recorded in UPSTREAM.json and patches/.

Versions

Latest versionPublishedSize
0.2.5——

Comments

Loading…