I just shipped a useful update to the subtitle service at mogrt.zinchuk.online.
The main goal of this release was simple: make the tool easier to use on real Premiere projects without adding extra noise to the workflow.
What changed
The biggest addition is a sequence picker.
If your Premiere project contains multiple sequences, the service now reads the project structure after upload and lets you choose the exact sequence you want to process. That sounds small, but in practice it removes a lot of guesswork and makes the service much safer to use on larger or messier projects.
I also cleaned up the download flow.
Instead of returning a zip archive with extra files, the service now gives you exactly what you usually want: a ready-to-open .prproj file. No extra report bundle, no log files in the download, no additional unpacking step.
Why this matters
This project started as a local Python script, then grew into terminal tools, a one-command launcher, a Premiere panel prototype, and finally a web service. I built that progression with a lot of help from Codex, and at each stage the user experience kept revealing the next obvious improvement.
This update came directly from testing. The feedback was clear:
- choosing the target sequence matters,
- downloading only the final project is cleaner,
- the interface should stay simple even when the underlying logic gets more complex.
That is exactly what this release tries to do.
Under the hood
The core subtitle engine is still the same one that powers the local workflow and the Premiere panel experiments. It still handles:
- styled script parsing,
- host vs quote logic,
- language-aware subtitle splitting,
- MOGRT-based subtitle generation,
- timing based on selected anchor tracks.
What changed here is mostly the service layer around it: project inspection, sequence selection, validation, and a more focused output flow.
What is next
There is still more to do. The interface copy will keep improving, the instruction block will likely get richer with images, and there is still room to tighten the connection between the web service and the Premiere-side workflow.
But this is a good step. The service is getting closer to what it should feel like: upload the project, upload the script, choose the right sequence, and get back a clean Premiere file that is ready for the next editing step.
If you want to try it, the current public version is here: