Skip to content

Julien H.@julienEditor
Question
Hearted by @julien
Question
Hearted by @julien
Behind the scenes: translation moves inside cinemaOS
One change for the next build. It has been in our main code since 26 September.
In Build 7, subtitle and dub-script translation uses Apple's on-device translation by default, and some languages need support installed in macOS first. In the next build, translation runs on the language model that ships inside cinemaOS, for every language that model handles well enough. Nothing downloads, nothing leaves your Mac, and there's no account or service behind it.
"Well enough" is measured. We ran every candidate language through the model and scored whether the meaning survives a round trip. A good score means the meaning came back. It doesn't prove the grammar.
102 languages were measured, and 65 reached our score floor.
7 of those are held back because the saved output drifted into a different language. Asturian came out as Spanish, for example.
That leaves 58 languages on offer. Four reached Good: Dutch, French, German and European Portuguese. The other 54 are Draft or Rough.
Each language shows its tier where you pick it. Good means spot-check it. Draft and Rough mean a fluent person reads it before anyone else sees it. Every translated line stays marked as machine translation until someone approves it.
Which languages do you subtitle into, and who checks them today? Your answers tell us where to measure next. Hearted by @julien
Archive a finished project so you can check it and restore it later
When a job is delivered, a Verified Archive puts the project and every media file it uses in one folder, with a checksum for each file. Later, cinemaOS can prove nothing has changed and restore the project from it.
Written against Build 7, the current public build.
Make the archive
Save the project with File ▸ Save Project (⌘S). Create Verified Archive stays greyed out until the project has been saved to a file.
Choose File ▸ Verified Archive ▸ Create Verified Archive….
Pick where it should go. A different drive from your working media is the point. cinemaOS makes a new folder there, named after the project and ending in Verified Archive.
Read the confirmation. It says how many media files will be copied and how much space they take. Every file is copied, checksummed and reopened before the archive folder appears, and an existing folder is never replaced.
Choose Create Verified Archive. It runs as a job in the queue. When it's done, the status line reads Verified archive complete and Finder shows the folder.
Check it later
Choose File ▸ Verified Archive ▸ Verify Archive… and pick the archive folder.
cinemaOS checks every file against its SHA-256 checksum and reopens the project. It changes nothing. A pass reads Archive verified, with the number of files.
Restore it
Choose File ▸ Verified Archive ▸ Restore Archive… and pick the archive folder.
Pick where the restored project should go. cinemaOS creates a new folder named after the project and ending in Restored, checks every restored file against its checksum, and leaves the archive untouched.
The restored project is added to your recent projects and shown in Finder.
Worth knowing
Don't add anything to an archive folder. Verify treats any file that isn't in the archive's manifest as a failure. Finder's own .DS_Store file is the one exception.
If the destination already holds a folder with the same name, nothing is replaced. Choose another destination.
Tried it on a real project? Reply with how big it was, what drive you used and how long it took. If a step didn't match what you saw, tell us which one. Hearted by @julien
Question
What do you still need before you can leave Adobe?
Honest question. We'd rather hear the hard answer.
Here's what the current public build, Build 7, already does with work from Adobe apps:
XML exported from Premiere Pro brings over cuts, transitions, speed changes, volume, transforms, markers and captions.
Premiere Pro projects (.prproj) open through an experimental reader: cuts, timing and media links only. If it can't read one, it stops and walks you through an XML export instead.
Anything that doesn't come across is listed in the conform report before the timeline opens. Effects, styled titles (they arrive as markers), multicam angle cuts and audio plug-in chains don't translate.
View ▸ Customize Keyboard Shortcuts… has a Premiere Pro key layout.
So what would still stop you? Name the app, the thing you'd miss, and one real job where you'd miss it. The more specific, the more useful.
Adobe and Premiere Pro are either registered trademarks or trademarks of Adobe in the United States and/or other countries. cinemaOS is not affiliated with or endorsed by Adobe. Hearted by @julien
Question
Hearted by @julien
Hearted by @julien