Build log · Audio editing plugins

Audio editing plugins for podcast editors working in Pro Tools, Reaper, Cubase and Audition

Plugins for Pro Tools, Reaper, Cubase and Audition that bring client comments, cleanup suggestions and uploads into the editor's own software.

The answer first

We built Fame's audio editors plugins for the four apps they use - Pro Tools, Reaper, Cubase and Audition - that show client comments on the timeline, suggest cleanup edits from the transcript, check levels and upload finished files, all without leaving the editor. Main result so far: 10%+ time saving on editing, in an audio editor's own words, after a manual prep pass.

The firm

Who we built it for

Fame is a B2B podcast agency that has been running for six years. Its team finds and books guests, produces episodes and promotes each show for around 100 clients, and Fame Crew finds local videographers for shoots and handles the editing. Team size: about 97 people (estimate), most of them freelancers and contractors. Fame is Forge's own sister company, so we built these tools for ourselves first and still run every one of them.

Who uses it: audio editors.

The problem

Three windows for every edit

An editor read client comments in the review tool, found each moment by hand in their audio software, cleaned up filler and silences by ear, then exported and uploaded the file to Drive. Every step meant switching windows.

Editors spent around 45 minutes per episode on prep and cleanup - about 35 hours a week across the team (estimate).

What we built

The review tool, inside the editor's own software

Comments on the timeline

Client comments appear as markers at the exact moment, and jump the playhead there.

Cleanup suggestions

Filler and silences found from the transcript, offered as edits the editor accepts or skips.

Levels check

A loudness check before export, so files meet the show's standard.

Render and upload

Finished files upload to the right place in one step.

Screenshot: the editor plugins hub
The editor plugins hub
What it replaced

What the audio editors used before

Switching between the audio software, the review tool and Drive for every edit.

Monthly cost of what came before: £0 a month (estimate)

What changed

What changed for the audio editors

~35 hrs/weekTime back for the audio editors (estimate)
September 2026Running sinceSource: all three Reaper phases and the Pro Tools plugin live 8 September 2026
4Audio apps supportedSource: Pro Tools, Reaper, Cubase, Audition
10%+Editing time saved, per an audio editor's reviewSource: editor feedback, September 2026
85Plugin updates releasedSource: commits: Pro Tools 42, Reaper 29, Audition 14
97%Uptime, last 90 days
How we run it

How we look after the audio editing plugins

Forge built this for Fame and looks after it: errors are reported automatically to an error tracker, and anything that stops someone doing their job is fixed the same day.

Plugins change with real editors' feedback: rounds with working editors shaped cut quality, speaker labels and how cleanup is grouped. The Audition plugin is the newest and has not yet been used on a real episode.

What broke, and how we fixed it

  • 14 September 2026: The transcription provider retired a setting the plugins relied on, so cleanup suggestions stopped for all four plugins. We switched to the new setting with an automatic fallback, the same day.
  • 17 September 2026: A change to how audio was decoded broke the level adjustments on the server. We rolled the fix out across four releases and now verify decode changes against a fresh analysis before release.
Stack

What it's built with

  • Electron
  • Pro Tools PTSL
  • Lua (ReaScript)
  • Adobe CEP
  • AssemblyAI
  • Next.js
  • Vercel

Connects to: AssemblyAI, the asset review tool, Google Drive.

Cost

What it would cost a client today

Start with the 2-week ops audit ($2,500 / £2,000, credited to your first month). A tool like this then fits the embedded plan at $7,500 / £6,000 a month, with this as the first build included. Four plugins in four apps, changing with editors' feedback, is a continuous backlog, so it fits embedded.

Plans have a 3-month minimum. AI usage is passed on at cost, and the tool runs on your own accounts, so you own it. See pricing for the full breakdown.

Fit

Would this work for your firm?

If your specialists work in desktop software and copy information in and out of it, a plugin puts the information where they already work. It suits production and post-production agencies.

See what we build for agencies, or read about our AI implementation work.

FAQ

Questions about building a audio editing plugins

Can you build plugins for Pro Tools and other audio software?

Yes. Fame's editors use plugins for Pro Tools, Reaper, Cubase and Audition, each built on that app's own scripting interface.

Does the plugin edit the audio automatically?

No. It suggests cleanup edits from the transcript; the editor accepts or skips each one.

How much time does it save editors?

One of Fame's audio editors put it at 10% or more, after a manual prep pass first. As a rough guide, that is about 30 minutes back per episode (estimate).

Who owns the tool once it's built?

You do. It runs on your own accounts and you pay those tool costs directly; we monitor it, fix it and keep improving it on the monthly plan.

Want a audio editing plugins shaped to your firm?

Start with a 2-week ops audit - $2,500 / £2,000, credited to your first month.

Updated October 2026 · By Tom Hunt, founder of Fame and Forge