A Closer Look at Sequence 1.4

Hello,

Last month I wrote about the groundwork going into Sequence 1.4. This month I can share more of what it brings.

The release has taken longer than we hoped. Speaker detection, multicam and the new timeline need to work together, and we have been testing those connections rather than bolting on features one at a time. We are getting closer, and I think the extra work will make a real difference to your experience.

Speakers and multicam

Speaker detection stays local. NVIDIA’s Nemotron 3 will be the default, with SortFormer available as an alternative. Sequence builds encrypted local voice profiles, so a returning host or guest can be associated with the same speaker in later recordings. Give each speaker a name, profile image and color, then find the transcripts associated with them. It is included in your purchase, without an extra speaker-detection charge.

Multicam builds on the folders introduced in the last release. Its angles use that same library navigation, keeping the recording organized. Each angle can have its own variants: edit an angle independently, then choose which variant the main multicam project uses. Those edits carry through, rather than being restricted to the main assembly.

You can also assign camera angles to speakers. That is why we wanted multicam and speaker detection to arrive together, and why they have needed more testing.

A timeline, assets and reusable edits

The new timeline is another view of the same editing data. Transcript cuts and reordered sentences appear as clips, alongside external audio and multicam tracks. You can right-click an angle to open it directly.

Assets bring images and video into that view, too. Trim their start and end in the timeline, then position and resize them in the video player. Think watermarks, title cards, sponsor graphics or a subscribe reminder. This is the first timeline release; media support and polish will continue beyond 1.4.

A project or variant can also become a reusable asset. Early testers have been editing a sponsor break in Sequence, then bringing it into the main podcast as a linked asset. It stays dynamic without rendering a separate file first; rendering happens at export or handoff.

Speakers and assets are scoped to their catalog. The library also gains an expanded view which splits into a two-column view, giving projects, speakers and assets more room to breathe.

Take the project with you

A Sequence Package (.sqbundle) carries the transcript and editing decisions to another Mac or another editor’s Sequence. Include the source media for a self-contained handoff, or reference material the recipient already has. Double-click the package to import it.

Optional encryption protects the transcript and editing data, not the source media. Sequence shows you an encryption code to send separately to the recipient, who needs it to open the protected editing data.

Automation and the everyday improvements

The updated CLI 1.1.3 is already released, with more capabilities and a more robust workflow. Sequence 1.4 is needed to take full advantage of it. Compatible chat apps will also be able to show a visual MCP result card, with a summary and status alongside the assistant’s text reply.

There is plenty of less visible work, too:

• Faster app startup, project loading and switching, with improvements to auto-sync, export and normalization.
• A tidier shared transcription and speaker pipeline, with improvements to transcription speed and accuracy.
• In-app update notes, so you can see what an update brings before installing and review the changes afterward.
• Support for three devices per account, giving multi-Mac and agent-assisted workflows more room.

Setapp and Sequence Circle

We also plan to bring the full Sequence app to Setapp this month. I am excited to introduce it to that community and see how it fits into people’s existing workflows.

Sequence Circle is our free early-access programme. The latest build will let you join for TestFlight access and try beta updates before the public release.

Beta builds can have issues. Error reporting is enabled automatically and cannot be switched off while you remain a Circle member; scrubbed diagnostic reports help us find and fix problems. Product analytics remains optional. Join only if you are comfortable testing unfinished builds, and read the Sequence Circle terms first.

A couple of recent reads

• Local vs Cloud Transcription for Podcasts: Cost, Privacy and Editing - costs, privacy and choosing the workflow that fits your recordings.
• Building an Outcome Machine - why the less visible foundations matter as Sequence grows.

The goal is still a focused experience for you as the editor, with a powerful way to work through the CLI and MCP if you prefer your agent to handle some of the tasks.

Thanks for your patience, and for helping shape Sequence.