Set Component Param Value At Time
Known native Undo limitation: on macOS Premiere 26.5.2, updating an existing Motion/Scale LINEAR key through the native Add action changed its value correctly, but one physical Undo removed the original key instead of restoring it. A separate direct SDK Add reproduced this without DSL conversion. This is a measured existing-key limitation, not a proven nearest-tick regression or a result for every parameter/version. Keep an independent saved copy when modifying existing keys; no Runtime workaround is applied. timeSeconds is converted to the nearest native Premiere tick, not rounded to a frame. Computed values such as 0.7999999999999999 and exact 0.8 address the same tick. The value-type read used to prepare this write uses that same normalized TickTime; numeric, Boolean, string, PointF and Color handling is unchanged. A tick count outside JavaScript's safe-integer range retains the native seconds-factory fallback with a precision warning. Native parameter behavior can still affect the committed result; this conversion is not a live frame-raster, wrapper-lifetime or Undo guarantee. The usual queued Action/atomic transaction behavior is unchanged. Use onError to decide whether errors stop the script, continue, or return false when the block supports it. If storeResultIn is set, the block also writes a result variable back to your graph.
Inputs
| Input | Required | Value Kind | Types | Enum Values |
|---|---|---|---|---|
param | yes | expression | — | — |
timeSeconds | yes | expression | — | — |
value | yes | expression | — | — |
onError | no | expression | enum-string | STOP, CONTINUE, RETURN_FALSE |
storeResultIn | no | variable-name | — | — |
Notes
- Known native Undo limitation: on macOS Premiere 26.5.2, updating an existing Motion/Scale LINEAR key through the native Add action changed its value correctly, but one physical Undo removed the original key instead of restoring it. A separate direct SDK Add reproduced this without DSL conversion. This is a measured existing-key limitation, not a proven nearest-tick regression or a result for every parameter/version. Keep an independent saved copy when modifying existing keys; no Runtime workaround is applied.
timeSecondsis converted to the nearest native Premiere tick, not rounded to a frame. Computed values such as0.7999999999999999and exact0.8address the same tick. The value-type read used to prepare this write uses that same normalized TickTime; numeric, Boolean, string, PointF and Color handling is unchanged.- A tick count outside JavaScript's safe-integer range retains the native seconds-factory fallback with a precision warning. Native parameter behavior can still affect the committed result; this conversion is not a live frame-raster, wrapper-lifetime or Undo guarantee. The usual queued Action/atomic transaction behavior is unchanged.
See Also
- Premiere Reference Paths: Explains Premiere reference path strings for project items, sequences, tracks, timeline items, markers, components, and parameters.