Marker Create

Category: Pr Markers

storeResultIn stores boolean creation success, not a marker reference. Use storeMarkerIn when later blocks need the marker that was just created, for example to call prMarkerSetProperty, prGetMarkerProperty, prMarkerMove, or prMarkerDelete. When storeMarkerIn is set, the runtime commits any currently pending Premiere actions before creating the marker, then commits the marker creation before continuing to the next block. In MANUAL_GROUPED transaction mode, storeMarkerIn therefore acts as an implicit transaction boundary around marker creation. This makes the created marker ref immediately usable, but it can split undo/atomicity compared with a fully grouped transaction. If marker creation fails with onError=RETURN_FALSE, storeResultIn is set to false and storeMarkerIn is not written. The runtime identifies the created marker by comparing marker state before and after the creation commit. If Premiere produces an indistinguishable duplicate marker and the created marker cannot be identified uniquely, the block fails instead of guessing. The marker-ref capture does two marker-list reads around the creation commit, so one storeMarkerIn use is linear in the current marker count for that owner. In loops that create many markers and capture each one, this can become significant on timelines or project items with many existing markers. If you do not need the created marker ref immediately, omit storeMarkerIn to preserve the surrounding transaction grouping behavior. 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. If durationSeconds is set, the marker is created with that duration instead of being just an instant.

Inputs

Input	Required	Value Kind	Types	Enum Values
owner	yes	expression	reference, string	—
name	no	expression	string	—
type	no	expression	enum-string	COMMENT, CHAPTER, FLVCUEPOINT, WEBLINK
startSeconds	no	expression	number	—
durationSeconds	no	expression	number	—
comments	no	expression	string	—
onError	no	expression	enum-string	STOP, CONTINUE, RETURN_FALSE
storeResultIn	no	variable-name	variable-name	—
storeMarkerIn	no	variable-name	variable-name	—

Notes

• storeResultIn stores boolean creation success, not a marker reference.
• Use storeMarkerIn when later blocks need the marker that was just created, for example to call prMarkerSetProperty, prGetMarkerProperty, prMarkerMove, or prMarkerDelete.
• When storeMarkerIn is set, the runtime commits any currently pending Premiere actions before creating the marker, then commits the marker creation before continuing to the next block.
• In MANUAL_GROUPED transaction mode, storeMarkerIn therefore acts as an implicit transaction boundary around marker creation. This makes the created marker ref immediately usable, but it can split undo/atomicity compared with a fully grouped transaction.
• If marker creation fails with onError=RETURN_FALSE, storeResultIn is set to false and storeMarkerIn is not written.
• The runtime identifies the created marker by comparing marker state before and after the creation commit. If Premiere produces an indistinguishable duplicate marker and the created marker cannot be identified uniquely, the block fails instead of guessing.
• The marker-ref capture does two marker-list reads around the creation commit, so one storeMarkerIn use is linear in the current marker count for that owner. In loops that create many markers and capture each one, this can become significant on timelines or project items with many existing markers.
• If you do not need the created marker ref immediately, omit storeMarkerIn to preserve the surrounding transaction grouping behavior.

See Also

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

Examples

Import SRT As Sequence Markers

Prompts for marker text-target options, optionally clears existing active-sequence markers, then imports subtitle entries from an `.srt` file as sequence markers.

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

Topics: markers, subtitles, SRT import, file dialogs, marker comments

Source: recipes/ex-markers-import-srt-as-sequence-markers.json

Download JSON

Import YouTube Chapter Text As Sequence Markers

Prompts for a pasted chapter block or a text file, optionally clears existing active-sequence markers, then imports YouTube-style chapter lines as sequence markers.

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

Topics: markers, YouTube chapters, text import, file dialogs, multiline prompts, marker comments

Source: recipes/ex-markers-import-youtube-chapter-text-as-sequence-markers.json

Download JSON