Jev shot transition choice

Choose a transition between two described shots

Compare the previous and current spoken shots to select plain, wipe, flash or glitch under supplied editing rules. Missing neighboring context stays unresolved; the example does not edit video.

shot transition choiceLive API
Try an example

The second shot continues the same walkthrough.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

This independently authored text exercise adapts an edit decision defined in the linked Jev Shorts Editor repository. Its synthetic shots, simplified rules and missing-input outcomes are original to this page. It does not reproduce a rendered edit, inspect video, or verify the repository’s timing and cost claims.

Select the cut treatment: Plain for continued explanation; Wipe for a smooth topic change; Flash for a sudden reveal or punchline; Glitch for a specifically digital disruption.

Decision rules and labels
PlainWipeFlashGlitchUnclear
A real response from the Jev API

Edit any input to explore a different decision. No request is sent until you run it.

Your next decision

Not run yet

Choose an example or write your own input, then run it to see the ranked choices.

Results are not stored by this site. Your submitted text is processed by the API provider.

The decision

What the decision checks

A transition is a relationship between neighboring shots. The same sentence can continue one sequence or reveal something surprising after a different setup. Both lines therefore belong in the input.

The options are a simplified editorial policy inspired by the linked editor. No effect is applied here, and the classifier does not inspect motion, exposure or accessibility needs in the actual footage.

This independently authored text exercise adapts an edit decision defined in the linked Jev Shorts Editor repository. Its synthetic shots, simplified rules and missing-input outcomes are original to this page. It does not reproduce a rendered edit, inspect video, or verify the repository’s timing and cost claims.

Illustration of selecting a caption token for emphasis in an edit timeline
Illustration of the decision flow.
How it works

Try the example in four steps

Use the sample to understand the rule, then test your own input for shot transition matching.

  1. Illustration of adding the text or evidence for a decision

    Add the information to check

    Compare the previous and current spoken shots to select plain, wipe, flash or glitch under supplied editing rules.

  2. Illustration of defining a question and its allowed choices

    Confirm the question and labels

    Open the decision rules and keep the intended distinction between Plain, Wipe, Flash, Glitch, Unclear. Edit the choices only when testing your own rule.

  3. Illustration of sending one input and comparing the returned choices

    Run the decision

    Use a sample first, then try your own input. Compare the selected label with the other returned probabilities.

  4. Illustration of reviewing a result and an uncertain item before using it

    Review the next step

    Review Unclear before using a result. The label is a decision about the supplied information, not an executed action.

Our API test

Recorded API observations

Recorded API observations
Original inputObserved labelLeading probability
Continue a walkthroughPlain100%
Move to pricingWipe74.0%
Unexpected revealFlash73.0%
Digital breakGlitch98.0%
A word is not a cuePlain100%
Missing earlier shotUnclear93.0%

These are six original synthetic inputs, tested once per request revision. The percentage is the leading option probability, not measured accuracy. Authored expectations and any disagreements remain in the downloadable evidence. 6 of 6 results matched the authored fixture expectations.Verified

Understand the results

Shot transition matching: six recorded examples

The downloads contain six original inputs, their expected labels and one recorded API observation per input revision. Disagreements stay visible.

Using the result in your application

The single-request SDK runner uses your private TYPESAFE_API_KEY. The offline consumer reads saved observations, checks request hashes and prints a pending output. It does not call the model or change any external system.

Replay options

Inspect saved outputs or request a new decision

View the code example
Two independent commands
# Offline: inspect the downloaded saved observations. No API key is needed.
python preview_choice_workflow.py samples.json saved-api-results.json

# Optional live request: install the SDK and set TYPESAFE_API_KEY privately.
npm install @typesafe-ai/sdk@0.6.0
node run-choice-sample.mjs samples.json case-1
# The live response prints to the terminal; it does not update saved-api-results.json.
Scope of this demo

Where this decision fits

Useful scope

  • Comparing text-based edit choices before rendering
  • Replaying the same synthetic shot with changed context
  • Keeping the selected option and its distribution for an editor

Outside this demonstration

  • Uploading or inspecting video footage
  • Rendering, cutting or exporting a video
  • Proving audience retention or visual quality
Example FAQ

Using this example

The input contract and these limits define what the result means.

Why include the previous line?

A cut can only be interpreted relative to what came before. Without that context the example returns Unclear instead of inventing a relationship.

Must I apply the suggested effect?

No. Check the footage and viewer needs first. A plain cut can remain preferable even when a more expressive option has the highest probability.

Does the leading probability measure accuracy?

It describes the distribution over the supplied choices for this request. These six synthetic examples are functional tests with authored expectations, not a production accuracy benchmark.

Will a result change an external system?

No. The demo displays a label and distribution. The downloadable consumer produces a pending preview packet. Application code and a separate authorization policy would control any real action.

Test a different input

Edit the example above to see how a changed fact affects the decision, or open the Playground for another task.