> 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/v4.10.0/helmut4-components/streamdesigner/nodes/actions/avid-pro-tools/beta-pro-tools-bounce-session-action.md).

# (Beta) Pro Tools Bounce Session Action

This node is specifically designed for use with Avid Pro Tools. When triggered, it initiates the Bounce Mix command on the currently opened session. The node takes parameters from the cosmo webexport dialog to customize the session bounce process. It automates the bounce operation by directing the output to a specified destination folder.

**Input Parameters:**

* **Destination Path:**\
  The path to the parent folder where the bounced session file will be stored.\
  **Note:** The destination path should not include the session name or the file extension.

For further information see also [WEB\_EXPORT - Pro Tools Session Bounce](/helmut4-releases/v4.10.0/helmut4-components/helmutco/streams/co-event-triggers/web_export.md#pro-tools-session-bounce)

<figure><img src="/files/tWAdkgj5IhngsMTiiSXU" alt="" width="345"><figcaption><p>Pro Tools Bounce Session Action</p></figcaption></figure>

{% hint style="warning" %}
The destination path isn’t used for rendering because the Pro Tools API endpoint is currently unavailable. Instead, the bounced file will be saved in the **Bounced Media** folder alongside the project file.
{% endhint %}

{% hint style="danger" %}
The Pro Tools integration is currently in beta.

For this reason, it includes an expiration date of **June 30, 2025**.

We’ll remove this limitation in a future release once the integration exits beta.
{% endhint %}


---

# 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/v4.10.0/helmut4-components/streamdesigner/nodes/actions/avid-pro-tools/beta-pro-tools-bounce-session-action.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.