Audio intelligence
Structure before spectacle.
Tempo, beats, sections, energy, stems, semantic cues, and lyric or transcription data can inform a Music Graph used by planning, timeline, and live-cue workflows.
DWCTEDMG / DWCTGenerativeSoundStudio
Hear the structure.
Direct the motion.
A music-reactive creative production environment that connects audio understanding, visual direction, rendering, review, and delivery.
Public developmentSource · documentation · progress
GitHub repository
DWCTEDMG/
DWCT
This is the public source repository behind DWCT Studio. It contains the primary desktop product, its Electron and React interface, the FastAPI backend, build and packaging tools, documentation, tests, and the broader EDMG engine work that supports the product.
The repository calls EDMG Studio the canonical product. The working application lives under studio/edmg-studio/; older entry points remain for compatibility and specialized workflows.
Product purposeFor artists · creators · production teams
One working surface from a track to a reviewable visual master.
DWCT Studio is being developed for musicians, visual artists, directors, independent labels, live-performance teams, and small creative organizations producing music-led visual work.
It brings project media, audio analysis, scene planning, render operations, comparison, and handoff into one desktop workflow. It is not presented as a push-button substitute for creative direction or human review.
Production workflowUnderstand · direct · render · review
A documented path through complex work
Creative decisions stay visible from the first analysis to final delivery.
- 01
Understand the track
Bring in audio, analyze structure and energy, review timing and transcription data, and establish the creative brief before visual work begins.
- 02
Direct the visual plan
Translate musical sections into scenes, treatments, motion ideas, and render variants while keeping the artist's intent visible in the plan.
- 03
Render with control
Use the Studio's internal renderer or an explicitly configured compatible render backend. Model, hardware, time, and quality expectations are scoped before production.
- 04
Review and hand off
Compare variants, record approvals, check continuity, and deliver clearly named masters, supporting assets, project notes, and agreed source material.
Current capability areasScope confirmed per engagement
Direction & continuity
Variants with a reason.
Scene plans, visual direction, render tasks, comparison, approvals, and continuity warnings help teams evaluate choices instead of losing them in folders of unexplained outputs.
Flexible production
Local first. Connected when chosen.
Studio supports an internal render path and optional configured services or render tools. Availability depends on the selected model, hardware, licenses, and project configuration.
Useful handoff
Masters plus the map.
A scoped handoff may include video masters, audio, stills, cues, templates, source assets, decision notes, and delivery documentation. The exact package is defined before production begins.
Adobe and platform-ready delivery
Built to join a professional workflow—not trap the work inside one app.
Export choices, source access, ownership, and destination requirements are agreed during scoping and documented at handoff.
Adobe-centered teams
Delivery can be organized for workflows using Adobe Premiere Pro, After Effects, Audition, Photoshop, and related review processes. This describes compatible file delivery—not a native Adobe plug-in, certification, endorsement, or awarded partner status.
Publishing destinations
Versions for YouTube, Vimeo, Instagram, TikTok, live playback, or another agreed destination can be prepared to its current technical requirements. No platform approval or guaranteed distribution result is implied.
Rights and provenance
Customers confirm rights to supplied music, likenesses, and assets. Third-party licenses, model or service dependencies, AI-assisted material, usage permissions, and ownership expectations are identified as part of the project record.
Security boundaries
The normal desktop architecture keeps the project workflow and API on the local machine. Remote backends require configured access controls, and external providers are disclosed and selected according to the engagement rather than assumed.
Current availability
Development is active. Access is scoped.
DWCT Studio is currently presented as an actively developed product and production capability, not as a generally available finished download. Features, model availability, performance, and supported outputs are confirmed for each evaluation or customer engagement.
No Adobe certification, Adobe partnership, marketplace approval, or third-party platform endorsement is claimed unless it is formally awarded and independently verifiable.
GitHub: DWCTEDMG/DWCTGenerativeSoundStudio Ask about Studio