# WEB\_EXPORT

## Export Asset or Adobe Project Sources

This CO event will be triggered when the 'Export' [profile](https://docs.helmut.de/helmut4-releases/helmut4-components/helmuthk/profiles) of a specific element within the Cosmo project views is invoked through the action button menu.

Depending on the underlaying stream, various workflows can be triggered like exporting the element via Adobe Media Encoder.

<figure><img src="https://content.gitbook.com/content/cJYkTyk9qgh7aCR6dHIm/blobs/EUVOJitkR0DKa7WquM5l/image.png" alt=""><figcaption><p>Asse / element trigger in Cosmo</p></figcaption></figure>

When clicking the dedicated profile, an overlay window will open, allowing the input of various job-related information, depending on the [metadata set](https://docs.helmut.de/helmut4-releases/helmutio/metadata#metadata-set).

<figure><img src="https://content.gitbook.com/content/cJYkTyk9qgh7aCR6dHIm/blobs/noOkmrrvUdXlQpxSVMGq/image.png" alt=""><figcaption><p>Export a sequence via Cosmo Web_Export</p></figcaption></figure>

#### Metadata Order for Metadata Set

Please refer to [Metadata Order for Metadata Set](https://docs.helmut.de/helmut4-releases/helmutio/metadata/metadata-set#metadata-order-for-metadata-set) for further information.

### Export/Cancel Button

Clicking "Export asset" will start the job.\
Clicking "Cancel" or the "X" closes the dialog without saving.

{% hint style="info" %}
Setting up a trigger within CO requires an appropriate profile with a selected stream relevant to the current trigger.
{% endhint %}

## Pro Tools Session Bounce

When viewing a Pro Tools project in Cosmo’s Project view, you can bounce (export) the session. To begin an export, you need two prerequisites:

1. **Pro Tools** is running with the target session open.
2. A **Web Export** profile and stream have been configured.

<figure><img src="https://content.gitbook.com/content/cJYkTyk9qgh7aCR6dHIm/blobs/UjwnnHcVl8BJeWv5AB9O/image.png" alt=""><figcaption><p>Project view of a Pro tools project</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/cJYkTyk9qgh7aCR6dHIm/blobs/46ozXSumaWHxW9ln6LJ4/image.png" alt=""><figcaption><p>Exporting a Pro Tools session</p></figcaption></figure>

<figure><img src="https://content.gitbook.com/content/cJYkTyk9qgh7aCR6dHIm/blobs/rhJl2ClForWbYPSdkwAK/image.png" alt=""><figcaption><p>Pro Tools Session is inactive</p></figcaption></figure>

Once those are in place, the Pro Tools export overlay presents these dedicated options:

**Status**

* Pro Tools session is active
* Pro Tools session is inactive

**File Type**

* WAV
* AIFF
* MP4
* M4A

**Mix Source**

* Placeholder

**File Format**

* Interleaved
* Mono
* Multiple Mono

**Bit Depth**

* 16‑bit
* 24‑bit
* 32‑bit float

**Sample Rate**

* 44.1 kHz (SR\_44100)
* 48 kHz (SR\_48000)
* 88.2 kHz (SR\_88200)
* 96 kHz (SR\_96000)
* 176.4 kHz (SR\_176400)
* 192 kHz (SR\_192000)

Select your desired settings, then click **Export** to trigger the Pro Tools Bounce Session Action node via its native API integration.

## Host Assignment

{% hint style="warning" %}
Any stream with this trigger must have "CLIENT" as the host type. Since this stream needs to be assigned to any user/client, server execution is not possible.
{% endhint %}