Announcements

Braus comes to the Forte community: start with Pro Tools

Braus reaches Forte’s audio community with a free Pro Tools beta. Here is why we’re starting there, how it fits alongside existing tools and a first request to try.

Back to Blog

Today we’re introducing Braus to Forte’s audio community, with Pro Tools as the focus of this beta. Connect your own ChatGPT or Claude subscription inside Braus, describe a task in plain words, and let it work in your session in the background. Braus is free during the beta.

If you already follow Braus, this is a practical next step: putting it in front of people who work in Pro Tools every day. If you found us through Forte, welcome. Start with a request small enough that you can inspect the result yourself.

Why start with people who live in Pro Tools?

A session contains a lot of work around the creative decisions: identifying tracks, fixing names, checking states, bringing in files and preparing the next step. Each task may be straightforward. Together, they consume attention that could go into the session itself.

An AI chat can explain how to do those things. For a working engineer, the useful next step is letting that assistant carry out a request in the app, with a result you can check.

That is where we’re starting with the Forte community. Braus is built by the Forte team, which also builds fMusic and fPost. Those products address specific preparation and export jobs. Braus adds a way to ask for individual tasks in your own words, using the AI subscription you already have.

Keep using the tools that already fit your workflow. Give Braus a bounded piece of work, then judge it by what changed in Pro Tools.

A useful first request needs no changes at all

For a first session, ask:

Which tracks are muted or record-armed?

Braus can read the track states and report what it finds. Compare its answer with the session. You get a concrete way to check that it understands the right project before asking it to edit anything.

For the next step, use a copy of a session with four tracks named Audio 1, Audio 2, Audio 3 and Audio 4:

Rename Audio 1, Audio 2, Audio 3 and Audio 4 to Kick, Snare, Bass and Vox, respectively.

Inspect the names after the request. The useful outcome is four correctly renamed tracks in the intended session. A confident reply alone does not establish that.

These are deliberately small requests. They make the starting state, intended change and finished result easy to understand. Once you know what to expect, move to another supported task with an equally clear result.

What this Pro Tools beta covers

This release can read session information and work with tracks, selections and files. Examples include reading the session’s sample rate and bit depth, renaming tracks, changing mute states, creating named audio tracks and importing stems as new tracks.

You can also ask for a short combination of supported actions, such as muting Kick and Snare, then renaming Bass 2 to Synth Bass. Specify the exact tracks and the intended state. Check the result in the session, especially when a request contains several changes.

The scope matters. This beta starts with individual requests in Pro Tools. A successful track rename establishes that the rename worked; a larger production workflow needs its own checks. Work on other Mac apps is early, and it is outside the promise of this Forte launch.

Background work still needs a clear handoff

Braus is designed to carry out supported Pro Tools tasks in the background while you use your Mac. That makes the handoff important: say what it should change, give it a clear target and let it report what happened.

For the first few tasks, leave the tracks Braus is changing alone until it finishes. You can use that time elsewhere, then return to inspect the result. Editing the same track state simultaneously makes it harder to tell whose change you are seeing.

Braus checks changes where it can and reports when a result could not be verified. An unverified result needs inspection before another attempt. You can stop Braus from the app; stopping does not undo edits already delivered.

This is the standard we want the beta to meet: a request you understand, work you can follow and a result you can verify in your session.

Getting started through Forte

Use the Braus page on Forte for this beta and its download. Sign in with your existing Forte account, or create a free account, then connect your own ChatGPT or Claude subscription inside Braus.

For this release, you need:

  • macOS 15 or later on an Apple silicon Mac. Intel Macs have not been tested for this beta.
  • A Forte account, which is free to create.
  • Your own ChatGPT or Claude subscription, connected inside Braus.

Braus is free during the beta. Your AI subscription is a separate requirement.

For the Pro Tools experience described here, relevant app state is prepared as text on your Mac and sent with your request to the AI you connect. Braus’s app knowledge and conversations are stored locally. The connected model still receives the text needed for the request; local app control does not make remote inference local.

Help us choose the next useful task

The most useful beta feedback names the job you were trying to finish. Tell us what was open, what you asked, what you expected and what actually happened. Include your Braus, Pro Tools and macOS versions, using a test session or removing private project details.

A small task that fails consistently gives us something concrete to fix. A task that succeeds tells us which part of the workflow deserves a closer look next.

Get Braus through Forte, start with one read-only question and share what you find in the Braus Discord. We want the next steps to come from work people actually need done in their sessions.

All posts