KattandClaude Opus 5.5
6240ed646e
Measured against After Effects 26.3 with the original examples/ae-spatial-tangents.jsx (three paths, ten keys, even and uneven timing): an auto-Bezier key's out tangent is (next - previous) / 6 and the in tangent its mirror, whatever the key times; an end key uses its one neighbour, (neighbour - key) / 6. EffectCraft gave end keys none and scaled middle tangents by segment length, so paths with auto-Bezier keys ran up to 28 px from AE's. All ten tangents now match; path samples are within 0.05 px. Tests that relied on end keys having no tangent now expect AE's: Spatial Bezier keeps auto keys' handles (linear keys still get a third), the motion-path handle is drawn at a sixth, and a straight loopOut path is compared within 1e-9. docs/fidelity records the method and scores. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
4.0 KiB
After Effects 2026 replacement acceptance
Target: reproduce observable After Effects 2026 behavior and output closely enough to replace it in professional motion-design work on Windows, macOS, and Linux. Feature presence, internal CPU/GPU agreement, and a polished interface are separate evidence; none establishes this target on its own. Pin each reference case to the exact AE build, platform, fonts, color settings, source files, and project parameters.
Acceptance gates
| Gate | Evidence required | Current boundary |
|---|---|---|
| Work projects | Representative projects recreated or imported, edited, saved, reopened and delivered without lost state | Native AE project import and third-party AE plug-in execution remain gaps |
| Workflow | Pointer and keyboard cases for all panels, tools, shortcuts, docking, undo, dialogs and selections | Current pass covers 34 panel layouts and selected interaction regressions; every control is not verified |
| Animation | AE-sampled values for scalar, spatial, multidimensional and expression-driven properties, timing and interpolation | Eight scalar Rotation/ease cases, 168 samples verified against AE 26.3x87; auto-Bezier spatial tangents (ten keys, three paths) match AE 26.3; other cases remain open |
| Render fidelity | Original test scenes compared at 8/16/32 bpc, specified color spaces and alpha conventions; edges, impulses, gradients and temporal sequences | Most AE-rendered comparisons remain open; CPU/GPU agreement alone is insufficient |
| Media and delivery | Real footage import, seek, frame rates, audio sync, relinking, image sequences, codec/container metadata and exports checked in downstream tools | Actual work fixtures still required |
| Performance | Matched AE/EffectCraft input-to-present and export timings at 1080p/4K, warm/cold caches, memory/VRAM and long sessions | No claim of beating AE or measured blur response yet |
| Platforms | Native Windows, macOS and Linux runs with recorded GPU, driver, backend, device limits and fault cases | RTX 5090 Vulkan viewer/effect CPU comparisons pass; Direct3D FXC setup fails; other platforms not validated in this pass |
| Recovery | Save/reopen, interrupted render, invalid input, exhausted resources, lost GPU and cache failures without silent corruption | Catching compositor setup failure does not repair an OS graphics bugcheck |
Graphics and technology policy
Keep one shared Rust scene/effect model and portable wgpu shader/render implementation. Use Vulkan on Linux, validated Vulkan or Direct3D 12 on Windows, and native Metal on macOS. Browser WebGPU is a separate deployment/acceptance target. Record the backend actually selected; an available or compiled backend is not a passed compositor test. Use hardware capabilities and measured results to select optimized paths, with a CPU path that preserves output semantics. Newer APIs, SIMD, parallelism, and hardware codecs must preserve color, precision, timing and file compatibility. Avoid making baseline features depend on a specific GPU vendor or an optional advanced device capability.
Use current stable dependencies after regression checks; experimental technology belongs behind an explicit optional path. Driver/compiler combinations and shared-device versus headless initialization need the same diagnostic backend selection policy.
Reference process
Use the official AE 2026 user guide, public scripting documentation, legally available publisher samples, and original scratch projects observed through AESync. Do not copy Adobe implementation code or redistribute Adobe lesson artwork. Record documented expectations separately from live observations. Maintain per-case pass/fail/untested results, tolerances and repeatable commands; do not replace them with a global parity percentage.
Next priorities: qualify the verified Windows Vulkan path on larger workloads; measure Gaussian Blur interaction and output against AE; expand animation/render oracles; exercise representative work projects and required plug-ins; then close each platform acceptance gate.