Files
jhonny-editor/code/docs/recommendations/2026-08-19-round-3/50-keyframe-semantic-verification.md
T
João Henrique b541f502ba feat: initial commit - Jhonny Editor
- Adicionado estrutura completa do projeto
- Configurado MCP server para Premiere Pro
- Adicionado documentação e skills
- Configurado Gitignore para o projeto
2026-09-08 09:59:31 -04:00

22 lines
1.2 KiB
Markdown
Executable File
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# Recommendation 50: keyframe semantic verification
## Evidence
Adobe’s stable `ComponentParam` API exposes keyframe lists, values at time, and interpolation actions; `Keyframe` exposes position, value, and temporal interpolation mode.
- [Adobe ComponentParam reference](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/componentparam)
- [Adobe Keyframe reference](https://developer.adobe.com/premiere-pro/uxp/ppro-reference/classes/keyframe)
## Proposed improvement
Extend typed effect automation with a dry-run keyframe plan that canonicalizes tick positions, parameter value types, interpolation modes, and expected pre-state. After one transaction, read back the complete affected range and report semantic differences.
## Acceptance criteria
- Duplicate ticks, unsupported value shapes, invalid interpolation, and out-of-range times fail before mutation.
- Confirmation binds component identity, parameter identity, sequence revision, and plan digest.
- Unknown commit state is never automatically retried.
- Licensed-host fixtures cover scalar, boolean, color, and point parameters where supported.
Keyframe readback proves parameter state, not rendered visual correctness.