Set Component Param Keyframes

Category: Pr Tracks & Clips

The existing-key Undo limitation is also confirmed for one clearMode=NONE bulk write on macOS Premiere 26.5.2 Motion/Scale: replacing the original LINEAR key with value150/HOLD produced the expected exact-tick key, but one physical Undo removed the original key. This scoped result does not establish all bulk/parameter/version behavior. A direct native Remove+Add in one transaction restored one measured LINEAR baseline, but that does not establish public ALL/RANGE Undo or HOLD/BEZIER/tangent preservation. No Runtime workaround is applied. Every supplied time uses the nearest native tick for both the value-type read and added keyframe position; it does not snap to a frame. The unsafe-integer seconds fallback emits a precision warning. Existing value conversion, list validation, interpolation preparation and pending-action boundaries remain unchanged. RANGE/ALL removal retains the original native TickTime objects from the existing keyframe list. RANGE uses the existing seconds/epsilon inclusion rule; listed times are not reconstructed from seconds before removal. prClearComponentParamKeyframes also retains native TickTimes and its existing range policy. 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. Use clearMode to decide how existing keyframes should be treated before the new set is applied. Use interpolationMode to choose the interpolation that newly written keyframes receive.

Inputs

Input	Required	Value Kind	Types	Enum Values
param	yes	expression	—	—
times	yes	expression	—	—
values	yes	expression	—	—
clearMode	no	expression	—	—
interpolationMode	no	expression	—	—
onError	no	expression	enum-string	STOP, CONTINUE, RETURN_FALSE
storeResultIn	no	variable-name	—	—

Notes

• The existing-key Undo limitation is also confirmed for one clearMode=NONE bulk write on macOS Premiere 26.5.2 Motion/Scale: replacing the original LINEAR key with value150/HOLD produced the expected exact-tick key, but one physical Undo removed the original key. This scoped result does not establish all bulk/parameter/version behavior. A direct native Remove+Add in one transaction restored one measured LINEAR baseline, but that does not establish public ALL/RANGE Undo or HOLD/BEZIER/tangent preservation. No Runtime workaround is applied.
• Every supplied time uses the nearest native tick for both the value-type read and added keyframe position; it does not snap to a frame. The unsafe-integer seconds fallback emits a precision warning. Existing value conversion, list validation, interpolation preparation and pending-action boundaries remain unchanged.
• RANGE/ALL removal retains the original native TickTime objects from the existing keyframe list. RANGE uses the existing seconds/epsilon inclusion rule; listed times are not reconstructed from seconds before removal. prClearComponentParamKeyframes also retains native TickTimes and its existing range policy.

See Also

• Premiere Reference Paths: Explains Premiere reference path strings for project items, sequences, tracks, timeline items, markers, components, and parameters.