CASE STUDY

From an Odette pull to a complete story.

A long Genshin Impact stream gave ShadyCut something much harder than a simple highlight hunt: a character pull, personal stories, testing, mistakes, reactions, combat and a payoff spread across the session. ShadyCut connected those moments into a single Odette story and produced an editable first-cut draft.

1ceStream’s session moved through several different threads: discovering Odette, talking about his connection to dance, testing the character, pulling her, experimenting with teams and eventually seeing where she worked — and where she did not.

Instead of treating those moments as isolated highlights, ShadyCut followed the changing goal of the session and built a story around the streamer’s decisions, reactions and eventual payoff.

What ShadyCut prepared

  • A Story Blueprint connecting the strongest Odette moments into one narrative.
  • A Director Plan defining scene order, trims, pacing, transitions and editorial guidance.
  • A structured first-cut video assembled from moments spread across the original stream.
  • Editor-facing context for scenes that needed bridging, clarification or additional material.

This case study also became an important development run for ShadyCut itself. Over roughly a month, we repeatedly reviewed the generated story and edit, identified where context or continuity could break, and refined the pipeline around real editorial problems rather than synthetic tests.

The result was not just a better Odette video. It materially improved how ShadyCut understands long-form creator content and how it turns that understanding into a usable editing draft.

How ShadyCut improved

  • Streamer camera activity became part of the understanding layer, helping the system recognize reactions and visually important creator moments.
  • The understanding pipeline was reorganized so speech, gameplay, game knowledge and supporting signals contribute to one coherent session model.
  • Story generation was substantially rebuilt around goals, decisions, turning points, payoffs and what the viewer must actually see for each beat to work.
  • Continuity checks were strengthened so missing setup, unresolved intentions, unexplained reactions and broken scene transitions can be detected and bridged.
  • Director planning was refined to treat selected material as editable source rather than sacred blocks, allowing tighter pacing while preserving story coherence.

The first generated drafts were already able to identify the central story, but review exposed the difference between finding the right moments and making those moments play as a complete video. Some scenes needed tighter trims, some reactions needed their causes restored, and some transitions needed additional context.

Those iterations moved ShadyCut closer to the actual product goal: not simply producing highlights, but delivering a coherent proposed edit that an editor can understand, review and refine instead of starting from hours of raw footage.

PROJECT FILES

Explore the Output

HTML · STORY

Story Blueprint

The selected narrative arc, story windows, turning point, and payoff behind the draft.

Download file
HTML · EDIT PLAN

Editing Plan

The proposed presentation order, trims, transitions, pacing notes, and dialogue candidates.

Download file