Launched this week
TitlleFlow
Stop styling subtitles manually in Final Cut Pro.
4 followers
Stop styling subtitles manually in Final Cut Pro.
4 followers
Still styling subtitles manually in Final Cut Pro? TitleFlow is an early-stage, free and open-source macOS tool that turns SRT subtitles into styled Final Cut Pro titles automatically. Built for real editing workflows and shared early for feedback. • Batch multiple projects • Multi-track overlap support (podcasts) • 100% offline • Optional Secondary Storylines From SRT → FCP titles in seconds. GitHub: https://github.com/presterx/TitleFlow
Looks like a genuinely useful tool for anyone drowning in subtitle work. My one question: how does it handle edge cases like overlapping dialogue or speaker labels embedded in the SRT, especially with the multi-track setup for podcasts?
@seldaetinit9pb Thanks for the great question!
In the current MVP, TitleFlow lets you turn subtitle styles designed inside Final Cut Pro into reusable templates and export them as separate Secondary Storylines in FCP, making it easier to manage complex subtitle projects.
For overlapping dialogue, the workflow is template-based: you can predefine multiple subtitle templates with different screen positions and assign them to different speakers or tracks. This allows simultaneous dialogue to appear in separate areas of the frame instead of overlapping visually.
In the short-term roadmap, I’m adding a preprocessor that can detect speaker labels in SRT files and automatically group subtitles by speaker, so different subtitle templates can be applied per speaker.
In the medium term, the built-in editor will support manual speaker assignment after import, allowing more flexible restructuring and styling directly inside TitleFlow.
TitleFlow is designed as an offline-first workflow tool by default. In future versions, it may optionally support external AI APIs for speech-to-text workflows, allowing users to generate subtitles from audio while keeping full control over their processing pipeline.
Speaker diarization will also be supported via optional API-based services, requiring user-provided API keys.