Showcase Studio in Pylerium update goes LIVE at 100 Subscribers!

Showcase in Pylerium

Open SHOWCASE in Pylerium to use the existing Promotional editor inside the desktop app. All original cards, lighting, layouts, particles, keyframes, cinematic controls, camera paths and recording modes remain available. SHOWCASE PROJECT in Workshop and SHOWCASE PLUGIN in Plugins select the corresponding capture source.

The desktop app manages the studio's local API runtime automatically. No separate server command is needed. Enable phone access explicitly shares the studio on the LAN and displays the phone URL. Turning it off returns to desktop-only access. Closing Pylerium saves the current scene, releases the embedded browser, and stops the owned studio and project-preview runtimes. Projects launched through the normal runner retain its existing stop/close behavior.

Capturing a project

Choose a Workshop project, plugin, or SELECT FOLDER. The capture inspector finds Python scripts and HTML pages, skips build/dependency folders, detects common GUI/web frameworks and suggests a local server URL. You can edit that URL for any running webpage, Flask, FastAPI or other web app.

• AUTO CAPTURE launches a selected Workshop project when needed, waits up to 20 seconds for its GUI or web server, and records a clip. It can enable and capture a selected GUI plugin. Static HTML folders are captured as pages.
• RUN SELECTED uses the existing runner and default execution profile.
• SCREENSHOT captures the running URL or visible project/plugin window.
• CAPTURE CLIP records 1–15 seconds. GUI clips sample at 30 fps and retain aspect ratio, up to 1920×1080. Web clips are rendered with Playwright and trimmed to the selected duration.
• CAPTURE HTML PAGES previews and screenshots up to eight discovered HTML pages. A project can contain more pages; individual pages can also be imported through the studio's existing Library.

Keep native GUI windows visible and unobstructed for screen capture. External window capture requires Windows; embedded plugin/widget and web capture have their own paths. Console-only projects need an authored visual interface or generated image to produce a showcase card. FFmpeg on PATH is required for clips; browser capture uses installed Chrome or Playwright Chromium.

In the web editor, click Pylerium → Captures → Place capture card. Captured images are embedded in the card so they also work in the original standalone Promotional editor; videos use its persistent media cache. Edit in Workshop / Plugins returns to the project editor. Load project scene brings that project's saved scene into the editor. Save scene back to project writes .showcase/scene.json in that project's directory. Desktop and phone openings load the workspace's latest saved scene; this is shared persistence rather than concurrent editing synchronization.

Captures, browser storage, selected folders and the workspace scene live under orchestration_data/showcase (or the configured workspace/state root). Existing project code is preserved; scene exports write to .showcase.

Project and plugin SDK

Projects may publish generated media directly:

from showcase_sdk import publish_capture
publish_capture('screenshot.png', 'preview.webm', title='My project')

For a PyQt widget, call this on its GUI thread after rendering:

from showcase_sdk import capture_widget
capture_widget(window, title='My GUI')

Runner-provided project IDs and the shared database path associate captures with the current workspace. SDK captures appear in the same Pylerium capture library.

Source and packaging

Development uses the original sibling Promotional sources. Systematic/showcase_studio is a bundled snapshot for standalone distributions. Run python Systematic/sync_showcase.py after changing the original studio to refresh that snapshot before packaging. The EXE builder includes the studio files, bridge, Qt WebEngine and Playwright driver. Browser installations and FFmpeg remain external prerequisites; no EXE rebuild is implied by source changes.

Install Systematic/requirements.txt for Flask, Playwright and PyQt6-WebEngine alongside the existing Pylerium dependencies. If Qt WebEngine is unavailable, OPEN IN BROWSER retains the editor and project bridge.