Phantom Editor AI Logo
Back to Blog

AI Transcription in Premiere Pro with Echoe Scribe

8 min readBy Phantom Editor Team
AI Transcription in Premiere Pro with Echoe Scribe

AI Transcription in Premiere Pro with Echoe Scribe

If you edit in Adobe Premiere Pro, you already know the pain: you want accurate captions, but you don’t want to bounce between websites, exports, and re-import steps every time you tweak formatting.

Echoe Scribe is built to keep transcription inside Premiere while giving you multiple AI engines to choose from, plus quick caption “reflow” controls so you can change line breaks without having to re-transcribe.

It’s also a strong option when you’re working with languages Premiere’s native Speech-to-Text doesn’t support. Adobe publishes its official supported language list here: Languages supported by Speech-to-Text (Adobe).

Featured Snippet Summary: With Echoe Scribe, you can transcribe a Premiere sequence using local Whisper (offline) or cloud engines like Deepgram, Speechmatics, and AssemblyAI (BYOK). After transcription, use Reflow Lines → Reflow & Import to change the number of words/lines per caption without re-transcribing.

Here’s the full walkthrough video (this blog is a written version of it):

What Echoe Scribe does (in plain English)

Echoe Scribe helps you:

  1. Transcribe a sequence using the engine you prefer (local or cloud).
  2. Import the transcription as captions back into your Premiere timeline.
  3. Reflow captions (change words-per-line / lines-per-caption) without running transcription again.

Step 1: Open Echoe Scribe and choose your sequence

Open Echoe Scribe inside Premiere (left panel), then choose what you want to transcribe (in the video, the demo uses a full sequence).

Step 2: Pick your transcription engine and language

Echoe Scribe lets you select from multiple engines:

  • Local Whisper (downloadable models that run on your computer)
  • Deepgram (cloud)
  • Speechmatics (cloud)
  • AssemblyAI (cloud)

Then pick your language before you transcribe. Each provider has different language coverage, so if you work across languages, it’s useful to have multiple options available in one workflow.

Step 3: Set caption formatting (words per line + lines per caption)

Before transcription, set how you want captions to be structured:

  • Words per line (ex: 6 or 8)
  • Lines per caption (ex: 1, 2, or 3)

This is the “editor-facing” part of captions that affects readability the most, especially for social formats.

Step 4: Click Transcribe (what happens behind the scenes)

When you hit Transcribe:

  • For cloud models, Echoe Scribe exports the sequence audio to the selected provider and receives back timed text.
  • For local Whisper, you can download the Whisper model and transcribe locally (useful if you want offline transcription).

In the demo, Deepgram is called out as being particularly fast, with strong word and timing accuracy.

Step 5: Reflow lines and import (without re-transcribing)

This is the feature that makes Echoe Scribe feel “Premiere-native.”

After you’ve already transcribed, you can go to Reflow Lines, change your formatting (words/line, lines/caption), then hit Reflow & Import.

The key point from the video:

  • Echoe Scribe re-uses the existing transcription and adjusts the caption line breaks based on your new settings.
  • You don’t have to transcribe again just to change formatting.

Examples shown in the video:

  • Switching to two lines per caption card
  • Trying one word per line (not always practical, but demonstrates the control)

Choosing the right model (quick guide)

Different engines have different trade-offs. Here’s a practical summary based on what’s explained in the walkthrough:

EngineRuns where?When to use
Deepgram (Nova 3)CloudGreat default when you want fast turnaround with strong timing.
SpeechmaticsCloudStrong accuracy; can be slower than Deepgram.
AssemblyAICloudA balanced option (often “in the middle” on speed vs Deepgram/Speechmatics).
OpenAI Whisper (local)Your computerUseful for offline workflows and broad language support; larger models tend to be more accurate but heavier. The walkthrough notes timing may be less tight than some cloud engines.

Add your API keys (BYOK) for cloud engines

Deepgram, Speechmatics, and AssemblyAI require an API key.

In Echoe Scribe, go to:

  1. Settings
  2. API Keys
  3. Paste your provider key(s)

Important security note from the walkthrough: API keys are basically passwords. Don’t share them publicly, and treat them like any other credential.

If you’re deciding whether to set this up: most providers offer some kind of free tier or trial at various times, but those details change—so it’s best to check each provider’s current terms directly.

How to get an API key (provider links)

The exact UI changes over time, but the flow is usually the same: create an account → open your dashboard/portal → generate an API key → copy it once → paste it into Echoe Scribe.

  • Deepgram: Start at Deepgram → sign up → open your dashboard → generate an API key.
  • Speechmatics: Start at Speechmatics → sign up → open your dashboard → generate an API key.
  • AssemblyAI: Start at AssemblyAI → sign up → open your dashboard → generate an API key.

Once you’ve generated the key, return to Echoe Scribe and paste it into Settings → API Keys.

Multi-language tips (formatting matters)

The video shows a few language examples:

  • Mandarin/Chinese: “one word” may map differently than in English (and can display as multiple characters). If captions feel too dense, try fewer words per line and/or fewer lines per caption.
  • Dutch: the demo switches language and transcribes successfully with Deepgram.
  • Hindi: the demo uses AssemblyAI on a Hindi podcast and imports caption cards back into the timeline.

If you regularly work in multiple languages, the most practical workflow is:

  • pick the best engine for the language and speed you need
  • transcribe once
  • iterate on caption formatting using Reflow & Import until it matches your style

Next steps

If you run into bugs or want a feature added, send us a note—feedback from real editing workflows is what shapes what we build next.


Phantom Editor FAQ

© 2026 Phantom Editor. All rights reserved.