> 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/helmut4-components/streamdesigner/nodes/actions/job-action/job-render-proxy-in-ame-action.md).

# Job Render Proxy in AME Action

The **Job Render Proxy In AME Action V2** node renders a proxy file in Adobe Media Encoder and assigns the newly created proxy path to the current Helmut job.

The Helmut panel is required for this operation. After a successful render, the destination file path is returned as the node result and can be used by subsequent workflow steps.

A common use case for this node is generating proxy files for the **Adobe Premiere Pro proxy workflow**. These proxy files can subsequently be transferred to **Cosmo** and linked to their corresponding high-resolution assets, enabling efficient proxy/high-resolution workflows throughout the production pipeline.

***

### Input Parameters

#### AME Path

The full path to the Adobe Media Encoder application that should be used for rendering.

Example:

```
/Applications/Adobe Media Encoder 2026/Adobe Media Encoder 2026.app
```

The configured AME version must be installed on the client executing the stream.

***

#### Source File

The complete path to the source file that should be used for proxy generation.

Example:

```
{job.source}
```

***

#### Destination File

The full destination path for the proxy file, including the file name but without the extension.

The file extension is added automatically by Adobe Media Encoder based on the selected EPR preset.

Example:

```
/Volumes/proxy/{job.name}
```

***

#### EPR Path

The full path to the Adobe Media Encoder `.epr` preset used for proxy generation.

Example:

```
/Volumes/epr/proxy.epr
```

The preset defines the codec, format, resolution, bitrate, and other export settings.

***

#### Render Message

The dashboard message displayed while the proxy is being rendered.

Example:

```
Rendering Proxy with AME as user '{user.name}'
```

***

#### Render Done Message

The dashboard message displayed after the proxy render has completed successfully.

Example:

```
Rendering proxy with AME as user '{user.name}' has been successful
```

***

#### Render IN to OUT

When enabled, only the section between the configured In and Out points is rendered.

When disabled, the complete source is rendered.

***

#### Kill AME When Done

When enabled, Adobe Media Encoder is closed after the render process has finished.

This is useful on dedicated render clients or in automated workflows where AME should not remain running after processing.

***

### Node Result

The path of the newly created proxy file is returned after a successful render.

It can be accessed using:

```
{stream.last_result}
```

or:

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

The returned path can be used by subsequent nodes for further processing.

***

### Typical Usage

```
AME Path:
/Applications/Adobe Media Encoder 2026/Adobe Media Encoder 2026.app

Source File:
{job.source}

Destination File:
/Volumes/proxy/{job.name}

EPR Path:
/Volumes/epr/proxy.epr

Render IN to OUT:
false

Kill AME When Done:
false
```

***

### Important Notes

* The Helmut panel must be installed and available.
* Adobe Media Encoder must be installed on the client executing the stream.
* The source file and EPR preset must be accessible from the executing workstation.
* The executing user requires write access to the destination directory.
* The destination path should be provided without a file extension. The extension is determined by the EPR preset.
* After a successful render, the generated proxy path is automatically assigned to the current job.