Project Overview & Development Timeline
Product discovery, wireframes, technical architecture, and initial codebase setup.
Build the Premiere panel UI with search, player, filters, and SMP branding.
Authentication, search, streaming, download, and metadata handling.
Drag & drop, import workflows, cross-platform support, and error handling.
Debugging, performance testing, monitoring, and internal pilot build.
Playlist sync, folder structures, stems, advanced filters, and performance optimizations.
Similarity-based search, music recommendations, and caching mechanisms.
Music inpainting, track variations, timeline analysis, and rights-aware AI concepts.
A web-based panel inside Premiere, connected to SMP search & metadata.
The MVP is a MusicFinder panel in Adobe Premiere Pro. Technically it's a small web app (HTML/CSS/React) running inside Premiere. Editors can search, preview, filter, and then safely download/import tracks into a project. The panel connects to SMP via APIs (login, search, metadata) while Premiere import remains local.
A pragmatic technical starting point for a first MVP.
Although Avid has traditionally been the most widely used platform in professional post-production, we deliberately start the MVP in Adobe Premiere Pro.
Premiere offers a more open and web-oriented plugin environment, which allows us to build and iterate faster using familiar web technologies. This makes it the most suitable platform to validate the core MusicFinder workflow in a controlled way.
The goal of the MVP is not to favor one platform, but to first prove the concept and interaction model. The technical and product learnings from the Premiere MVP will directly inform the next steps.
Avid (enterprise) next — Resolve follows a different route.
Avid is a logical next step for enterprise post. It's a different ecosystem, so after the MVP we do a checkpoint: scope, feasibility, planning and SDK constraints. DaVinci Resolve is considered a separate track and not part of the MVP.
Avid Media Composer is widely used in high-end post and enterprise workflows. The SDK and ecosystem differ from Premiere, so we'll assess technical feasibility and scope after validating the MVP approach.
DaVinci Resolve has a different plugin architecture and user base. It's on the radar but considered a separate initiative, not part of the immediate post-MVP roadmap.
Enterprise workflow, evaluated after MVP validation.
Avid Media Composer is a core platform in professional post-production environments.
Because Avid uses a different SDK, security model and deployment flow than Premiere, a dedicated Avid version requires a separate technical assessment.
After validating the MVP workflow in Premiere, we will evaluate the Avid SDK to determine scope, feasibility and timing for an Avid-specific implementation.
To be filled after the editor session
To be filled after the editor session
To be filled after the editor session