His Japanese viewers wanted the repair videos in Japanese
By David
Hafiz Rahman fixes old film cameras in a rented corner of a workshop in Bukit Merah. Shutters that stick, light seals that have turned to tar, rangefinders that no longer line up. Twice a month he films one repair from start to finish and posts it to YouTube. The videos run about eleven minutes. He talks the whole way through, half explaining and half muttering at screws.
I'm David, and I work on VoxStudio. Hafiz is made up, but his problem comes from creators who have written to us about the same thing. People in another country want their videos, and the creator doesn't speak the language.
The comments he couldn't answer
About a third of Hafiz's views come from Japan. That makes sense. Many of the cameras he repairs were made there, and there is a large community of collectors who still shoot film. The comments under his videos are often in Japanese. He pastes them into a translator, and the request comes back the same each time, in slightly different words. Could he make a Japanese version? Subtitles are fine, people wrote, but it is hard to read them while watching his hands.
He tried once. Last year he paid a freelance translator to do Japanese subtitles for his most popular video, a Canon rangefinder with a jammed shutter. It took nearly three weeks. The file came back as a Word document, not a subtitle file, so he spent a Sunday copying lines into his editor and lining them up by ear. Halfway through, the timing drifted, because he had trimmed a section after sending the script. He fixed it, uploaded it, and decided he would not do that for every video.
Recording the narration himself was never an option. He had tried reading a few Japanese sentences off his phone for a joke at the end of a video. The comments were kind about it, which was worse.
One video, start to finish, on his Mac
Hafiz edits on a MacBook Pro with an M1 Pro chip, which is enough for VoxStudio for Mac. It needs Apple silicon and macOS 15 or later. He picked his newest video for the test: an Olympus compact where the lens would not extend, eleven minutes and twenty seconds long.
He opened Transcribe in the sidebar, clicked Import files, then Choose media, and picked the finished video. In the Processing options window he left Input language on English. Then he typed into Hotwords the words he knew any speech model would get wrong: the camera model, "flex cable", "helicoid", "light seals", and the name of the shop in Tokyo where he buys parts. He turned on Segment subtitles, because he wanted subtitle-sized lines at the end, and clicked Transcribe. The speech model had already been downloaded in Settings under Local Features, so the transcription ran on his Mac. The offline transcription guide covers that setup if you are starting from zero.
The transcript came back with timestamps. He read it with the video playing, which is the dull part and the part that matters. Twice he had said "this one" while pointing at a part, which works on screen and means nothing in another language. He changed both to name the part. He also fixed one number. He had said "two millimetres" when the screw he was holding was clearly the 1.7, and he would rather the Japanese version be right than match his slip.
Translation is the step that leaves the Mac
Next to the Transcript tab there are three small icons: Export, Translate (a book with the letter A), and Open folder. He clicked the middle one, chose Japanese as the target language, and clicked Continue. The translate guide is plain about what happens here. Speech recognition runs on your Mac, but translation uses the AI provider you set up in Settings, so the transcript text is sent to that service. For a repair video he planned to publish anyway, that was fine. He would think twice before doing it with something private.
When it finished, a language tag appeared beside the Transcript and Subtitles tabs, and a menu let him switch between Original and Japanese. He cannot read Japanese, so he did the only sensible thing. He exported a Bilingual TXT from the Export window and sent it to Kenji, a collector in Osaka who had commented on almost every video for two years. Kenji replied the next morning with four corrections. Two were part names that had been translated literally. One was a sentence that was too polite for the tone of the channel. One was a joke that did not survive, so Hafiz cut it from the English as well.
That took a day, but not three weeks, and the fixes went straight into the session instead of a Word document.
A voice that isn't his, used carefully
VoxStudio's Mac FAQ describes dubbing in one line: translate the transcript, then create the dub in the voiceover builder with a reference voice you have permission to use. That last part is not decoration. Hafiz did not want to clone anyone he had not asked. He used a reference recording of his own voice, a short clean clip, read without the workshop fan running. The Voice Library guide says a clean sample of a few seconds works better than a long noisy one, and that matched what he heard.
In Voiceover he added the reviewed Japanese text as the script, chose that voice, and generated. Local dubbing creates the speech on the Mac. Before running the whole eleven minutes, he did what the voiceover guide suggests and auditioned a short section with the camera name and the shop name in it. One name came out wrong. He spelled it the way it sounds in the script, ran the test again, and then ran the full pass.
Then the edit. From the original session he chose Create clip, which opened the video in VoxStudio's editor with its subtitles on a track. He opened Sessions in the editor and dragged the finished dub onto the timeline. It landed on a new audio track. He moved it to line up with his first sentence, then muted the original English audio. That took the workshop sounds with it, including the shutter firing at the end, the moment the whole video builds to. He decided the first Japanese version could live without it and noted it as something to solve next time.
He watched the whole thing through once with headphones on, checking that the Japanese voice was not talking about the lens while his hands were already on the battery door. In three places it ran a little long. He cut the voice track at those points and nudged the pieces later, rather than speeding anything up.
Subtitles too, from the same session
Some viewers like both, so he went back to the session and opened Export one more time. Content: Subtitles. Variant: Translation. Language: Japanese. Format: SRT. He downloaded it, opened the file to check that the first and last cues were at the right times, and added it to YouTube as a Japanese subtitle track. Because the subtitles and the dub came from the same reviewed text, they say the same thing. That was the problem with last year's freelancer file, which was translated from a script he had changed afterwards.
He posted the Japanese version as a separate upload with a link back to the English one. Kenji was the first comment. He said the voice was a little calm for a man fighting a stuck lens, which is fair.
What it cost him
The first video took most of a Saturday, much of it reading, and a day of waiting for Kenji. The second took an afternoon. He now keeps a list of hotwords and part names in a note and pastes it in every time, because the fixes he makes before translation are the ones that save him later.
If you want to try the same thing, VoxStudio for Mac gives you 14 days with all the local features. After that you can keep using it on recordings up to 15 minutes long, which covers an eleven-minute repair video. The pricing page has the current plans, including the Mac Lifetime option. Start with one short video you have already published, translate it, and send the bilingual file to someone who reads the language before you generate a single word of audio. That step is the one I wouldn't skip.



Comments
Post a Comment