# Job Render in AME Action

Using the Job Render in AME Action, it is possible to render a file or sequence/composition using a defined encoding preset (epr) in Adobe Media Encoder. This is equally possible for imports and exports and can be run on either a Mac or Windows client (a licensed Media Encoder instance is required here).\
\
Media Encoder returns the progress of the encoding process to Helmut, which is displayed in the dashboard when the node is used as part of a workflow that creates a job object. This is always the case when the Helmut4 panel (Autoimport, Export, Web.Export, ...) is involved or a watch folder monitored by the server.

The node does not need any information about the file extension of the target format in the source path, as this is defined by AME itself (it is defined in the .epr file). If desired, AME also counts whether the file already exists in the destination path. (setting in AME). The node sets the placeholder {job.destination} in the payload job, which contains the destination path of the file defined in the node including the file extension in the further course of the stream.\ <br>

<figure><img src="/files/DLD5HhYk3C2tuZHMJUOK" alt="" width="375"><figcaption><p>Exporting {job.source} from an export trigger</p></figcaption></figure>

#### Asset stitching

In addition to exporting/transcoding files and project timelines, it is also possible to convert multiple files into a single file. The native stitching function of the media encoder is used for this purpose.

see: [Adobe Media Encoder stitching documentation](https://helpx.adobe.com/au/media-encoder/using/overview-media-encoder-user-interface.html)

The source file is filled with the full file paths, the individual files are separated by a semicolon.

Example: /Volumes/path/asset1.mov;/Volumes/path/asset2.mov;/Volumes/path/asset3.mov

<figure><img src="/files/Ttlnfs83fs1CFKGDFpWd" alt=""><figcaption></figcaption></figure>


---

# 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/v4.6.1/helmut4-components/streamdesigner/nodes/actions/job-action/job-render-in-ame-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.