> 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/support/debug-or-log-collection/helmut4-client/retrieve-the-ame-panel-log.md).

# Retrieve the ame panel log

The AME log file records all execution actions triggered through Helmut4 and performed by the local Media Encoder.

To locate the log file, click the Helmut4 tray icon (available on both Windows and macOS) while the application is running, then select the log button.

Next, navigate one level up in the folder to find the ame.log file.

<figure><img src="/files/heEzNCVWCSfn6dh1AqkE" alt=""><figcaption><p>Helmut 4 client</p></figcaption></figure>

The log for the corresponding operating system can be found here:

<table><thead><tr><th width="219.1951904296875">Operating system</th><th>Log-path</th></tr></thead><tbody><tr><td>Windows</td><td>/Users/{user.name}/MoovIT GmbH/ame.log</td></tr><tr><td>Macintosh</td><td>C:\Users\{user.name}\MoovIT GmbH\ame.log</td></tr><tr><td>Linux</td><td>On Linux, AME is not available, so the ame.log file does not exist</td></tr></tbody></table>

<details>

<summary>Example ame.log for an export</summary>

```
3.4.2025 9:54:24 -> New world enabled
3.4.2025 9:54:57 -> encodeDLItem
3.4.2025 9:54:57 -> Queue cleared
3.4.2025 9:54:57 -> add item to batch
3.4.2025 9:54:59 -> Work area mode 0
3.4.2025 9:54:59 -> Start batch
3.4.2025 9:54:59 -> onEncodeProgress -> 0
3.4.2025 9:55:3 -> Start batch
3.4.2025 9:55:6 -> onEncodeProgress -> 0
3.4.2025 9:55:7 -> progress: 0, status: Running!, encode complete?: false
3.4.2025 9:55:17 -> outputFiles: 
3.4.2025 9:55:18 -> onEncodeProgress -> 41
3.4.2025 9:55:18 -> onEncodeProgress -> 69
3.4.2025 9:55:18 -> progress: 69, status: Running!, encode complete?: false
3.4.2025 9:55:18 -> outputFiles: 
3.4.2025 9:55:19 -> onEncodeProgress -> 100
3.4.2025 9:55:19 -> Job finished with progress 100
3.4.2025 9:55:19 -> ["/Volumes/Helmut/helmut480-test/Helmut4/Media/Exports/VIDEO/2025-03-31-br-test/2025-01-16-My litte project.mp4"]
3.4.2025 9:55:19 -> onEncodeComplete
3.4.2025 9:55:19 -> encodeComplete with errors
3.4.2025 9:55:19 -> progress: 100, status: Running!, encode complete?: true
3.4.2025 9:55:19 -> outputFiles: /Volumes/Helmut/helmut480-test/Helmut4/Media/Exports/VIDEO/2025-03-31-br-test/2025-01-16-My litte project.mp4
```

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.helmut.de/helmut4-releases/support/debug-or-log-collection/helmut4-client/retrieve-the-ame-panel-log.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.