Review a session

Studio plays a session's picture, webcam and mic together with the events your game marked. Notes, drawings and transcripts live beside it, on the same timeline.

1. Add your folder or bucket

A recording on your own PC or a network share is a local or network folder: Add folder in the library, or the first-run screen. Sessions from remote testers are in a bucket. In Studio's library, open the Folders panel and add a bucket folder: the same endpoint, region, bucket and prefix as the campaign, plus your own read key. A reviewer's own credentials are kept in Windows Credential Manager, and are never Mulno's and never the upload key. For R2 this is a read-scoped API token to the same bucket. Sessions that went to Mulno Cloud are reviewed in the web app: Studio 0.4.1 keeps the platform's screens switched off, so it doesn't open them.

Sessions appear as soon as their metadata lands. One still uploading shows Uploading; once its manifest is in, it shows In the bucket.

2. Open a session

Download and prepare pulls its media into a local cache, with progress and Cancel, and decodes playback proxies. From then on it plays like a local recording: exact seeks, the mixer, drawings, and the pop-out monitor.

3. Take notes

• Press C at the playhead for a quick note, or Shift+drag on the timeline for a note over a range.
• Draw on the picture with a pen, box, arrow or text while you review. The drawing is saved with the note.
• The right dock has Notes, Events, Info and, once transcribed, Transcript (Ctrl+1 to Ctrl+4).

Notes live in your bucket cache and are never evicted by the disk-space cap that trims old media.

4. Transcribe a tester's voice

Mulno doesn't run its own transcription service or hold a key for you. In the Transcript tab (Ctrl+4), link a provider, OpenAI or ElevenLabs, with your own API key. Studio checks the key and keeps it in Windows Credential Manager.

Every run is something you start, never automatic. Words appear in the tab and as a lane on the timeline; click one to seek, or find spoken moments through search.

5. More in Studio

• Bug reports. A tester's F7 report is a flag with a bug attached. The timeline draws a bug icon on the flag's tick and the stretch it covers as a band; the inspector's Bug report tab shows the kind, how bad, the tester's words and Play the stretch. The Events tab has a Bug reports chip, and the CSV export gains the bug columns.
• Live review. A session that is still being recorded, on this PC or in a folder something else fills, opens in Studio and grows under you. Jump to live plays about 16 seconds behind the edge, since the picture trails the events. Export and Pop out are off while it is live.
• Across the campaign. Click a span or a region and the inspector compares it with every other session in your library from the same campaign (or the same build): each tester's time in it, the median, and how many ran past the Catalog's expected maximum. It reads the folders Studio has open, so nothing goes to a server.
• Find and share. Ctrl K finds an action, a session or a moment. Ctrl Shift C copies a link to the moment, and Share in the palette copies it for Jira, Trello or Markdown: Moment links and trackers.
• A voice note on a flag or bug report has a play key in the Events list and the bug report's inspector. The session's playback pauses when it starts. It is the flag-note-<n>.wav in the session's folder; the web app can't play it yet.

Reviewing in a browser tab, with nothing installed, is built but not open: Review in the browser.

You can also review in a browser tab, with nothing installed, at app.mulno.com, which is where a Mulno Cloud project's sessions open: Review in the browser.