CHANGELOG
What shipped.
Every notable change to studio.live, newest first. Dates are release days.
Initial release
A feature inventory of the studio.live codebase. Availability depends on your plan, browser, device and deployment configuration. Features marked “Not generally available” are disabled by production flag defaults; their inclusion does not announce a public rollout or store release.
Walls and view modes
- Browse media with card and list views and device-local view preferences.
- The wall player implements fit, fixed-aspect, scroll, filmstrip, spotlight, masonry, compare, Movosaic and zoom layouts, with tile-fit and layout controls. Not generally available: the wall player is disabled by default.
- Not generally available: justified layouts and spatial-library views, including the video globe, space library, zoom wall and formations, have additional feature gates.
Local media and ingest
- Open local files and folders, restore a local library, hide or remove assets, and clear local data.
- Scan, extract metadata, generate thumbnails and hash local media through worker-based processing. Local media indexing and storage run on your device.
- Video, image and audio intake follows the supported-format registry; playback and proxy support depend on the format and available browser capabilities.
- Not generally available: catalog audio and GIF ingest, container transcoding and reusable storyboard artifacts have separate feature gates.
Playlists, Explore and search
- Playlist playback implements local and catalog stages, navigation history, play order, looping and still-image dwell.
- Explore catalog records carry author, license and source attribution; catalog search includes a full-text fallback.
- Not generally available: Explore discovery rails, server-owned playlists, public playlist walls, provider-link playlists, session resume and semantic catalog search are disabled by default. Local-file playlists remain private.
Provider embeds and global transport
- Global play, pause and stop coordinate wall playback, the scheduler and mounted provider embeds. Wall controls include seeking and random advance; supported commands vary by provider.
- The first-party partner embed player uses partner credentials and signed playback tokens.
- Not generally available: public-wall provider embeds, isolated-wall YouTube and Vimeo frames, provider-link playlists and additional provider integrations are disabled by default. Unsupported playback can remain a poster or an external link.
FX and audio
- Shared audio playback uses one audio graph with global wall transport.
- Not generally available: the FX suite, EQ and filters, mixer desk, audio-reactive visuals and flash-capable effects are disabled by default.
- Not generally available: spectrum visualization, enhanced mixing, live radio and worklet mixing have separate feature gates.
XR
- Not generally available: immersive VR and AR, 360-degree and 180-degree projection, native media layers, spatial audio and collaborative theater require the XR gate and, where applicable, additional gates and compatible devices.
Community and marketplace
- Profiles and public galleries support visibility controls; profiles start private.
- Not generally available: community publishing, feeds, reactions and follows are disabled by default; comments have a separate gate.
- Not generally available: marketplace listings, purchases, creator earnings and payouts are disabled by default. Playlist storefronts require both playlist and marketplace gates.
Jam sessions
- Not generally available: real-time jam rooms and room chat are disabled by default. Room chat uses a bounded buffer cleared when the room ends; reported messages enter the report workflow.
Accounts and plans
- Account flows include sign-in, session management, plan display, checkout and the billing portal. Payment availability depends on configured providers.
- Plan prices and feature limits come from plan data, rather than fixed prices in this release note.
- Not generally available: wallet top-ups, e-pin redemption, balance-funded plan purchases, prepaid vouchers, quota packs and extended Stripe billing features are disabled by default. E-pin inventory administration is separate from redemption.
Desktop and Steam
- The codebase includes an Electron desktop shell and Steam-specific sign-in handoff. This release note does not claim a published desktop build or Steam store release.
- Not generally available: desktop-specific chrome, the privileged native bridge and direct updates are disabled by default. Steam builds do not initialize the direct updater.
Admin and backoffice
- Backoffice routes cover ingest, review, catalog, walls, licensing, safety, customers, billing, plans, operations, feature flags, monitoring, compliance and localization. Actions remain subject to module gates and permissions.
- Admin operations use Access identity, role checks and audit controls. Customer controls include audited data export and deletion routes.
- Not generally available: risk administration and enforcement, campaigns and the machine backoffice API are disabled by default.
Privacy and security
- Local-library processing and storage stay on the device; optional cloud and provider workflows have their own network and consent boundaries.
- The product includes legal and privacy pages, content-report and takedown intake, attribution, and cookie-choice controls.
- Not generally available: the privacy-proof panel, family controls, and IP-risk recording and enforcement have separate feature gates.
Languages and appearance
- The language picker supports 36 locales with locale-aware direction and number/date formatting.
- Dark, light and high-contrast themes, reduced-motion preferences and right-to-left layouts are available in the interface.
- Translations carry machine-translation disclosure where applicable; English remains the binding language for legal documents.
Workspaces, sharing and teams
- Create and manage local collections with undoable rename, reorder, recolor and membership edits; crop and rotate wall media non-destructively.
- Sync workspace metadata and version history subject to account storage limits; create, list and revoke view-only share links subject to your plan. Metadata sync does not upload your local media files.
- Team spaces support member roles, invitations, removals and paid seats, subject to team entitlement and billing configuration.
- Not generally available: review-link settings, reviewer comments and enterprise OIDC single sign-on have separate feature gates.
Exports, conversion and recording
- Export selections as EDL, CSV or printable SVG contact sheets. References use asset IDs rather than filesystem paths; contact-sheet watermarks depend on your entitlement.
- Not generally available: worker-based video export and local video conversion require the video-export gate and an active export lease. Progressive MP4 and cloud handoff have separate gates.
- Not generally available: microphone and line input, local master-audio recording and offline audio bounce require their respective audio gates and, where applicable, device permissions and recording entitlement. Local recordings are not uploaded.
- Not generally available: same-LAN peer video and bounded program-audio return use manual signaling and confirmation at both ends, without a hosted relay.
Search, source libraries and offline use
- Install the web app when your browser offers installation; pin locally available originals and posters for offline readiness. Local pinning does not download remote catalog media.
- Not generally available: on-device semantic indexing and natural-language search, semantic clustering, ratings, color labels, pick/reject and smart collections have separate feature gates.
- Not generally available: cloud-library connections, remote file binding and playback, and watched local folders require their UI and provider gates. Some provider adapters also require terms clearance; enabling a flag alone does not enable them.
Developer integrations
- The partner API uses scoped partner credentials.
- Not generally available: user API keys and MCP service, the metered catalog API, and the admin MCP service have independent feature gates.
- Not generally available: declarative plugin packs, edge-dispatch integrations and paid-plugin features require the plugin-platform gate and any additional feature gates.