For Jianying timeline and editing console: tracks, segments, playhead, split, trim, move, copy, delete, keyframes, as well as undo/redo, magnetic snapping, snapping, linkage, recording, and zoom.
When to use
- Operate timeline segments and tracks, or read precise console state.
- Use keyframes, trimming, speed, volume, opacity, picture-in-picture, and composite modes.
- Control session-level undo/redo, magnetic snapping, snapping, linkage, recording, or view zoom.
Capability boundaries
- ✅ Can do: track/segment inspection, split, trim, move, copy, delete, keyframes, and controlled session actions.
- ⚠️ Requires conditions: draft writes need snapshots; session actions need exact version, ownership, and before/after readback.
- ❌ Should not use: do not restore user's parallel edits, do not use fixed UI positions, do not repeat button actions without stateless readback.
Quick start
You can say directly: "split the current segment at 2.4 seconds", "move the B-Roll to 5 seconds", "turn on magnetic snapping and verify the state", "fit the timeline to all segments". On first use, load feature flow。
Run contract
- Trigger conditions: the user requests the editing console, timeline, tracks, segments, keyframes, or session-level control.
- Required capability:
timeline.edit、timeline.show、timeline.duplicate、timeline.remove、timeline.keyframe、runtime.control_catalog、runtime.controls。 - Minimum CLI version:
1.6.19; draft protocol actions can be executed directly, session control requires exact editor version and state readback. - Default risk:
reversible_write。 - Input facts: isolated draft copy, track/segment ID, frame rate, time range, target parameters, editor version, and current session ownership.
- Confirmation points: confirm separately for delete/batch move, recording, affecting the current GUI session, and overwriting existing keyframes.
- Success evidence:
playback; a command returning success does not mean the pacing, visuals, and session state are correct. - Prohibited behaviors: must not use undo to restore the user's parallel edits, use fixed UI positions, treat relative drags as absolute state, or repeat session actions without readback.
Workflow
Step 1 — Establish timeline facts
timeline show/tracks/segments/get Establish facts; run the control directory/Surface Inventory to audit UI entry points.
Step 2 — Choose route
Follow feature flow to choose the draft protocol or Runtime Control route.
Step 3 — Snapshot and execute
Create a snapshot before draft writes; read state before and after session control and confirm the session is owned by the plugin.
Step 4 — Verify
Run structural checks and diffs; when a perceptual conclusion is needed, play to verify.
Step 5 — Restore
Restore draft actions from snapshots; for session actions, perform the reverse operation only when the state can be verified.
Rules
- Draft protocol actions always take priority over GUI session control.
- Time uses absolute values and is quantized by the project frame rate.
- Session control only applies to Jianying processes/sessions owned by the plugin.
- Unresolved items in Surface Inventory remain coverage gaps.
Gotchas
- Undo affects the user's parallel edits: Do not use session undo in place of draft snapshots.
- Relative drags cannot be reproduced: The plan saves absolute targets and segment IDs.
- Cut point falls between frames: Run the quantization report first.
- Delete shared material: Check material references before deciding the retention policy.
- Claim control as long as the button is visible: There must be a semantic ID, state, and version evidence.
Security and Data
Console operations only access user-specified drafts and sessions launched/owned by the plugin; they do not read unrelated windows, account information, or content from other applications.
Minimal Job see examples/minimal-job.json。