> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.13.0/helmut4-components/streamdesigner/nodes/actions/adobe-premiere/premiere-project-sequence-to-vidispine-xml.md).

# Premiere Project Sequence to Vidispine XML

## Premiere Project Sequence to Vidispine XML V1

The **Premiere Project Sequence to Vidispine XML** node converts the JSON output generated by the **Premiere Project Index Sequence V1** node into a Vidispine SequenceDocument XML.

The generated XML can be imported into VidiCore/Vidispine to recreate the Premiere Pro sequence using existing Vidispine items. Each media clip is matched to its corresponding Vidispine item by reading a custom metadata field from the JSON data.

The node returns the generated XML as a string, which can be stored, written to a file, or sent directly to subsequent workflow steps.

<figure><img src="/files/SZJkwGLyTSjNDGFiMn0o" alt="" width="349"><figcaption><p>Premiere Project Sequence to Vidispine XML</p></figcaption></figure>

***

### Input Parameters

#### Sequence JSON

The JSON array returned by the **Premiere Project Index Sequence** node.

This parameter expects the raw JSON output containing the sequence together with all referenced media clips.

Example:

```
{node.result}
```

or

```
{stream.last_result}
```

***

#### Vidispine sequence ID

Specifies the Vidispine sequence (collection) ID that should be embedded into the generated XML.

Example:

```
COLLECTION-VX-12786
```

***

#### Item ID metadata field

Defines the name of the custom metadata field that stores the corresponding Vidispine Item ID for each media clip.

During conversion, the node reads this metadata field from every clip in the JSON and inserts the resolved Item ID into the generated SequenceDocument XML.

Example:

```
VS_ItemId
```

If a clip contains the following metadata:

```
{
  "customMetadata": {
    "VS_ItemId": "VX-123456"
  }
}
```

the generated XML references the Vidispine item `VX-123456`.

***

#### Fail on missing item ID

Controls how the node behaves when a referenced clip does not contain the configured metadata field.

**Enabled**

The node fails immediately if one or more clips do not contain the required Item ID metadata.

This option is recommended when every clip is expected to exist in Vidispine.

**Disabled**

Clips without the configured metadata field are skipped silently.

This option is useful when only a subset of clips has already been imported into Vidispine.

***

### Node Result

The node returns the generated **Vidispine SequenceDocument XML** as its result.

The XML can be accessed using:

```
{stream.last_result}
```

or

```
{node.result.?}
```

It can then be written to a file, uploaded to VidiCore/Vidispine, or processed by subsequent workflow nodes.

***

### Typical Use Cases

* Converting Premiere Pro sequences into Vidispine SequenceDocument XML.
* Rebuilding Premiere Pro sequences from media already managed in VidiCore.
* Preparing sequence XML for import into Vidispine.
* Linking Premiere Pro timeline clips with existing Vidispine items using custom metadata.
* Automating sequence exchange between Adobe Premiere Pro and VidiCore.

***

### Practical Tip

This node is typically used directly after **Premiere Project Index Sequence**. Before converting the sequence, ensure that every referenced media clip contains the configured Item ID metadata field (for example `VS_ItemId`) pointing to the correct Vidispine item. This allows the generated XML to reference existing assets instead of creating unresolved media references.