# Cosmo Add Proxy To Project Action

The **Cosmo Add Proxy to Project Action** node allows you to attach or update a proxy file for an existing high-resolution (HiRes) asset in Cosmo.

The proxy is linked to a previously registered asset. If the corresponding HiRes asset does not already exist in Cosmo, the node will fail.

This node is typically used in transcoding or proxy-generation workflows where a render system creates lightweight editorial media after the master file has been ingested.

#### Important Timing Note

Avoid executing this node immediately after [Cosmo Add Asset to Project Action](/helmut4-releases/helmut4-components/streamdesigner/nodes/actions/cosmo-16/cosmo-add-asset-to-project-action.md).\
The asset may not yet be fully available in the database. If both nodes must be used in the same stream, insert a [Sleep node](/helmut4-releases/helmut4-components/streamdesigner/nodes/actions/misc-21/sleep-action.md) between them (recommended delay: **at least 4000 ms**).

#### How the Proxy Is Assigned

The node determines which asset receives the proxy based on the provided inputs. The following priority order applies:

**1. Highest Priority — Asset ID**

If **Asset ID** is provided, the proxy is attached to exactly that single asset.

**2. Medium Priority — Project ID**

If no Asset ID is provided but a **Project ID** is specified, all assets inside that project that match the provided HiRes path will receive the proxy.

**3. Lowest Priority — HighRes Path Only**

If neither Asset ID nor Project ID is provided, Cosmo searches the entire database for matching HiRes paths and assigns the proxy globally to all matching assets.

This allows updating multiple projects at once without iterating through them individually.

#### Input Parameters

**Asset ID**\
ID of the asset to which the proxy should be attached.\
If present, this parameter overrides all other matching methods.

**Project ID (optional)**\
Limits proxy assignment to assets within a specific project.

**HighRes Path**\
Full file path (including extension) of the associated high-resolution media.

**Proxy Path**\
Full file path (including extension) of the proxy media file.

#### Synchronization Options

**Auto Sync**\
If enabled, the proxy is automatically synchronized when the project is opened.\
If disabled, the asset will appear as pending synchronization in the panel and must be synced manually.

**Skip Metadata Sync**\
If enabled, metadata synchronization in the panel is skipped.

**Skip Markers Sync**\
If enabled, marker synchronization in the panel is skipped.

**Don't change Asset name**\
If enabled, markers sync will be skipped in panel

**Don't change Asset breadcrumb**\
If enabled, the breadcrumb of the asset will not be changed after synchronisation, if it has been changed in premiere

When Auto Sync is disabled, the panel indicates pending updates and increases the counter of items requiring synchronization.

#### Execution Behavior

* Requires an existing registered HiRes asset in Cosmo
* Can update a single asset, a project, or all matching assets
* Typically used after proxy generation/transcoding
* Supports asynchronous execution

<figure><img src="/files/yGDvSSQ9p0wNLXo92BCq" alt="" width="351"><figcaption><p>Cosmo Add Proxy To Project Action</p></figcaption></figure>

#### Practical Example

A typical workflow:

1. A master file is ingested and registered in Cosmo.
2. A transcode system generates an H.264 proxy.
3. This node attaches the proxy to the HiRes asset.
4. Editors immediately receive an online/offline-switchable clip in Premiere Pro or After Effects after synchronization.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.helmut.de/helmut4-releases/helmut4-components/streamdesigner/nodes/actions/cosmo-16/cosmo-add-proxy-to-project-action.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.