Hi everyone! I’d like to share Beat Studio, a desktop application I’m developing for music-driven video editing—particularly AMVs, GMVs, and edits where the relationship between the soundtrack and the footage matters. I’m a solo developer and video editor. The project grew out of my own workflow: analyzing a track, marking useful musical moments, searching through footage, choosing scenes, and preparing everything for the edit. Beat Studio brings those steps into one connected workspace. I’ve attached a demonstration video and reference frames so you can see the current build, its interface, and the material I’m working with. Patreon: https://www.patreon.com/AnimaStage/posts/beat-studio-look-171023771 What is Beat Studio? It’s an editing assistant for analyzing your source material and preparing a music-driven timeline. You load a soundtrack and footage into a project, review the analysis, choose scenes, adjust their arrangement, and export the results. You can then continue working in your preferred editor. The aim is to reduce repetitive preparation while keeping shot selection, pacing, and creative decisions under your control. 🎵 Music analysis and editable markers Beat Studio analyzes a soundtrack and displays detected musical events alongside its waveform. Depending on the analysis settings and available components, those events can include: Beats and downbeats. Bass and sub-bass activity. Onsets and percussive events. Changes in energy and potential drops. Vocal-related events when the required analysis or stems are available. The markers give you a starting point for deciding where to place cuts, transitions, or visual emphasis. They are detector results, so they still need review. You can inspect different marker groups, adjust which ones you use, and add manual markers when the analysis misses a moment that matters to your edit. 🎞️ Scene selection with visual previews The Scene Selection panel presents footage as clips with reference frames. This makes it easier to compare scenes and choose material without repeatedly searching through the original files. With a supported local vision model connected, the workflow can also include AI-generated scene descriptions and scores. You can review those suggestions before deciding which clips belong in the project. The attached frames show how scenes are presented in the current build. They are previews from the footage, rather than newly generated video. ✂️ Timeline preparation Selected scenes, audio, and markers can be brought together in a shared timeline. The current interface includes tools for previewing the arrangement, adjusting clips, reviewing musical markers, and trying automatic arrangement as a starting point. This is where the two sides of the project meet: what is happening in the soundtrack and which footage might fit that moment. An automatically suggested arrangement still needs editing. My goal is to make that first pass easier to inspect and refine. 📦 Exports and project packages Beat Studio includes export options for workflows involving Premiere Pro, DaVinci Resolve, and Final Cut Pro. Depending on the selected export options, a project package can contain: A rendered MP4 with music. Timeline files for supported editing workflows. Marker data in formats such as CSV and JSON. Selected clips and reference frames. Project information and included media assets. The intention is to let you carry the preparation into another editor for effects, grading, transitions, and finishing. Export compatibility is still being tested. Having an export option available does not mean every combination of editor version, media format, and project settings has been validated. 🧠 Optional local AI through Model Hub The built-in Model Hub provides a place to download, verify, and connect supported local models. These can add capabilities such as speech transcription, further audio analysis, and visual scene analysis. They are optional downloads rather than models bundled into the base application. Hardware requirements vary by model. RAM, GPU memory, and available storage all affect which setup is practical. 💻 Portable Windows application The current version is distributed as a portable Windows package. You unpack the complete folder and launch the application in its own desktop window. The base package includes Python, FFmpeg, and the libraries needed for the main application. Optional AI models and their additional environments are installed separately. Who am I building it for? Primarily: AMV and GMV editors working with music and large amounts of footage. Creators who want a more organized way to review musical events. Editors who want visual scene selection and timeline preparation in one place. People interested in experimenting with local AI in an editing workflow. Current status and paid beta access Beat Studio is an early beta. I’m developing it solo, and I’m still improving reliability, usability, analysis behavior, and exports. I’m offering paid access to the current beta for people who want to try it on their own projects and share feedback. This is access to a work-in-progress build, so bugs, unfinished features, and changes should be expected. If you’re interested, message me for pricing, current requirements, access details, and known limitations before purchasing. Which part of this workflow would help you most: music markers, scene selection, automatic arrangement, or preparing a project for your main editor?   submitted by   /u/zemondza [link]   [comments]