Skip to main content

Set Sequence Property

Category: Pr Sequences Set Sequence Property block screenshot

IN_POINT_SECONDS, OUT_POINT_SECONDS and ZERO_POINT_SECONDS queue Actions that are built inside the committing Premiere transaction. PLAYER_POSITION_SECONDS moves the transient playhead directly and does not require an atomic transaction. Work Area is not a settable property here; use prSequenceSetWorkArea. These four time properties convert seconds to the nearest Premiere tick, without rounding to frames. This avoids sending a tick below an intended boundary for computed values such as 0.7999999999999999 instead of 0.8. If the tick count exceeds JavaScript's safe-integer range, the conversion falls back to the native seconds factory and emits a precision warning. Premiere may still quantize the resulting property; read it back after committing. Read the corresponding getter after the mutation has committed to obtain the actual native value. Premiere can quantize Sequence ZERO to its frame boundaries: the tested positive values on a 25-fps Sequence in Windows Premiere 26.5.2 read back at the frame boundary at or before the requested value. On that same fixture, tested playhead positions preserved the requested ticks. These observations do not establish a rounding rule for other frame rates, versions or negative offsets, and are separate from Project Item source In/Out behavior. Omitted, empty, whitespace-only or null sequence uses the active Sequence. FRAME_SIZE accepts a positive integer WIDTHxHEIGHT string such as 1920x1080. Blockly supplies a text default of 1920x1080 when choosing this property; imported explicit values and connected expressions are preserved. Premiere applies the new frame rectangle through a sequence-settings action, preserving the other settings derived from the sequence preset or matching source. If sequence is omitted, the block uses the active sequence when supported. 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​

InputRequiredValue KindTypesEnum Values
sequencenoexpressionreference, string, null—
propertyyesstringenum-stringIN_POINT_SECONDS, OUT_POINT_SECONDS, ZERO_POINT_SECONDS, PLAYER_POSITION_SECONDS, FRAME_SIZE
valueyesexpression——
onErrornoexpressionenum-stringSTOP, CONTINUE, RETURN_FALSE
storeResultInnovariable-name——

Notes​

Work Area is not a settable property here; use prSequenceSetWorkArea.

  • IN_POINT_SECONDS, OUT_POINT_SECONDS and ZERO_POINT_SECONDS queue Actions that are built inside the committing Premiere transaction. PLAYER_POSITION_SECONDS moves the transient playhead directly and does not require an atomic transaction.

  • These four time properties convert seconds to the nearest Premiere tick, without rounding to frames. This avoids sending a tick below an intended boundary for computed values such as 0.7999999999999999 instead of 0.8. If the tick count exceeds JavaScript's safe-integer range, the conversion falls back to the native seconds factory and emits a precision warning. Premiere may still quantize the resulting property; read it back after committing.

  • Read the corresponding getter after the mutation has committed to obtain the actual native value. Premiere can quantize Sequence ZERO to its frame boundaries: the tested positive values on a 25-fps Sequence in Windows Premiere 26.5.2 read back at the frame boundary at or before the requested value. On that same fixture, tested playhead positions preserved the requested ticks. These observations do not establish a rounding rule for other frame rates, versions or negative offsets, and are separate from Project Item source In/Out behavior.

  • Omitted, empty, whitespace-only or null sequence uses the active Sequence.

  • FRAME_SIZE accepts a positive integer WIDTHxHEIGHT string such as 1920x1080.

  • Blockly supplies a text default of 1920x1080 when choosing this property; imported explicit values and connected expressions are preserved.

  • Premiere applies the new frame rectangle through a sequence-settings action, preserving the other settings derived from the sequence preset or matching source.

Examples​

Render Sequence Marker Ranges

Renders one safely named file per non-zero-duration active-sequence marker. The setup dialog offers an optional `.epr` preset; leaving it empty uses the Premiere-installed H.264 Match Source - Adaptive High Bitrate preset.

kind: Recipe · format: persisted-document · validation: Schema only

Topics: markers, rendering and export, sequence export, presets, filename patterns, file dialogs, folder dialogs, collision handling

Source: recipes/ex-markers-render-active-sequence-ranges-with-preset.json

Download JSON