Permalink to Hypit StudioHypit Studio

Studio opens an editable video project in the browser. Play the composition, move through its frames, select words or graphics on the timeline, and change the properties a component exposes. Switch to Comments for a larger picture and timestamped feedback. Both views work before export.

Permalink to open-the-work-you-want-to-editOpen the work you want to edit

bash

cd /path/to/my-video
hypit studio --run build.svrun

Open the address printed by the command. Studio uses the Author Source and material selected in that Run. To keep generated material while editing, select completed Outputs with build-record and satisfy.

The globe menu, to the left of Studio / Comments, selects the interface language. English and Simplified Chinese are included. The first visit follows your browser language; later visits remember your choice. Switching preserves the playhead, selection and comment draft. It changes the interface, while your Script, video captions and comments keep their own content.

Argument	Use
`--run <file.svrun>`	Select the Run to open.
`--runtime <profile.json>`	Select a Runtime Profile; otherwise use the project's saved Runtime selection.
`--workspace <directory>`	Set the project boundary for Source access and edits.
`--port <number>`	Request a browser-server port; the default is `5179`.

The selected target must lead to one Film and its Timeline. Placed Takes add their semantic anchors; an animation can use a Timeline with an explicit end and no Takes. Both support visual components and property editing. The material needed to display the composition must already be available through the Run. Studio can perform media preparation supported by the selected Runtime; submit generation and encoded renders through hypit build.

Permalink to review-together-in-commentsReview together in Comments

Open the printed URL ending in #comments to watch the current composition with a notes column. Click the picture to play or pause, then leave a comment at the selected time. Clicking a saved note returns to that frame. Notes appear in time order; their numbers follow submission order.

Comments are saved in the project's FEEDBACK.json. You and your Agent can read, edit and mark them complete. Sending a note saves it; tell your Agent when the feedback is ready to work through. Switch to Studio to explore the timeline, Sources, Results and the controls components expose. Opening either view does not encode a video or submit an export Build.

Permalink to explore-the-projectExplore the project

The library at the left has three views:

Source lists the selected Run and its Author and Recipe files. Select a file to inspect or edit it.
Tasks shows completed project Builds and, with a selected Runtime, active execution information.
Artifacts lets you inspect public files retained in Build Results.

Choosing an Artifact opens it for inspection. To use it in the composition, update the Run's Candidate selection. This keeps the material choice in the editable project.

Permalink to picture-timeline-and-inspectorPicture, timeline and Inspector

The central Preview draws the composition with HyperFrames. It uses the same component layout, media sampling and motion as an encoded render. Check the actual picture when adjusting caption placement, graphic emphasis or coverage.

The Timeline shows component appearances on a shared clock. A semantic composition also shows Segments, Words, Selections and Moments. Select an entity to seek to it; playback, frame stepping, zoom and scrolling help examine a particular transition or layout.

The Inspector shows the selected entity's properties. Editable fields and timeline handles depend on the component's Studio Companion, which describes the component to Studio. A project component can supply its own Companion alongside its rendering code. Renderability and the available editing controls are separate: a field or gesture needs a clear source value to change.

Permalink to make-an-editMake an edit

Source edits change the selected .svml, .svs or .svrun file. Supported Inspector changes and timeline gestures write to the corresponding author value, then recompile the same Run. Moving a shared Selection or Moment changes its position in the Script, so all consumers follow that change. Editing a shared Frame or Recipe can likewise affect several appearances.

Check the save status after an edit. If recompilation fails, Studio reports the error and restores the previous files. List and record controls save complete, valid values when editing ends and show a completion hint for incomplete values. The Run and loaded Source files are watched; restart Studio after changing installed packages, component code or Runtime selection so those changes are loaded too.

Permalink to sound-and-deliverySound and delivery

Preview playback includes the AudioTracks selected in Film, such as speech, music and effects. The exported video's audio is assembled by the render's media pipeline. When the composition is ready for delivery, run its export Build to create the encoded video. Studio and Comments remain available to explore the editable work and discuss further changes.

For component authors, Studio Temporal Lineage explains semantic editing, and the Companion SDK explains how to expose component entities and controls.

To add another interface language, load a local JSON translation with --locale-pack ./language.json. The localization guide explains translation files, checking missing entries and sharing a language pack.