Jev music edit operation

Identify the requested music edit and any lock conflict

Describe the requested edit, available operations and note locks. Separate parameter changes from note regeneration and locked-scope conflicts before a music editor decides what to do.

Which operation fits this edit?Live API
Try an example

The operation changes a named project parameter.

Source: API-collected workflow inspiration; original demonstration below

Source and example scope

The API-collected roundup links the cited project. Its pinned source defines the decision adapted here. These synthetic inputs and explicit missing-context outcomes are original to this demonstration. The window returns a label; it does not run the linked application, execute its downstream actions or verify its performance claims.

Classify one edit.

Decision rules and labels
Parameter editRegenerate notesOther supported editLocked-scope conflictUnsupported requestNeed edit context
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

Changing tempo and rewriting a locked phrase need different handling.

The tempo preset changes a project parameter. The regeneration preset instead asks for new notes within a named, unlocked range. Both requests identify their target, which gives the classifier enough context to choose an operation.

The locked-range preset asks to replace notes while leaving their lock intact. That conflict takes priority over regeneration. The transposition preset remains a supported edit; it is not treated as unsupported merely because it changes pitches.

The linked music project defines edit operations and lock constraints. This original text demonstration exposes a smaller catalog and explicit missing-context outcome. It returns a label and probability distribution; it does not produce audio, render MIDI or apply an edit.

The API-collected roundup links the cited project. Its pinned source defines the decision adapted here. These synthetic inputs and explicit missing-context outcomes are original to this demonstration. The window returns a label; it does not run the linked application, execute its downstream actions or verify its performance claims.

Illustration of choosing one tool from the supplied alternatives
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 music edit requests.

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

    Add the information to check

    Describe the requested edit, available operations and note locks.

  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 Parameter edit, Regenerate notes, Other supported edit, Locked-scope conflict, Unsupported request. 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 Need edit context 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
Tempo parameterParameter edit100%
Regenerate a rangeRegenerate notes100%
Transpose a phraseOther supported edit100%
Locked note rewriteLocked-scope conflict100%
Generated vocalsUnsupported request100%
Selection absentNeed edit context95.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

Replay the saved synthetic requests to inspect each recorded decision

Replay the saved synthetic requests to inspect each recorded decision. Authored expectations and model disagreements remain available; these examples are not a production accuracy benchmark.

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.

Runnable offline example

Run one sample, then inspect the local packet

View the code example
Single-request replay
npm install @typesafe-ai/sdk@0.6.0
# Set TYPESAFE_API_KEY privately in your shell.
node run-choice-sample.mjs samples.json case-1
python preview_choice_workflow.py samples.json saved-api-results.json
Scope of this demo

Where this decision fits

Useful scope

  • Testing edit intent before a music-tool call
  • Separating parameter changes from note regeneration
  • Making missing selections and lock conflicts visible

Outside this demonstration

  • Generating a song in this window
  • Executing edits on a project
  • Assuming omitted lock state is unlocked
Example FAQ

Questions about music edit operation.

Input scope and downstream handling determine what this judgment means.

Can this page generate the regenerated notes?

No. It classifies the request. A separate music system must generate or apply notes after validating the selected range.

Why is transposition supported?

The cited edit schema includes it. This demonstration groups it with duplication and lock changes rather than labeling every non-parameter operation unsupported.

Is the leading probability an accuracy measurement?

No. It is one value in the returned distribution over this request’s choices. The six synthetic fixtures have authored expectations; they do not measure production accuracy.

What happens on an API failure?

The window displays an error without a fresh judgment. An incomplete-input outcome describes the supplied evidence and is not used as a fallback for provider failure.

Try your own music edit operation input

Edit the input above, or open the Playground to explore another decision.