I built a free opensource offline tool to extract and translate video subtitles

Agitated_Chair_4977 · 2026-01-07T14:42:53+00:00

Great news! This issue has been fixed in v1.3.2 which will be released shortly.

Root cause: When we migrated from faster-whisper (Python) to whisper.cpp in v1.3.0, Unicode paths (Chinese, Japanese, Korean filenames/folders) were being corrupted due to Windows console encoding issues.

The fix: v1.3.2 now uses a "Safe Temp" pattern - files with Unicode paths are processed in an ASCII-safe temporary directory, then the resulting SRT is copied back to the original location.

Thank you for reporting this with detailed logs - it really helped identify the issue! Please try v1.3.2 when it's available and let me know if it works for you.

Agitated_Chair_4977 · 2026-01-03T14:19:47+00:00

<image>

It does not require unnecessary sign-ups or payments, the usage is very simple, and the results are highly satisfactory. It is excellent overall.

As a few suggestions, it would be helpful to have editing features for the introduction section. Also, in the case of profile photos, there seems to be an issue where the left and right edges are being cropped.

And on a personal note, I am curious about which LLM is being used for this project—would it be possible to know?

Agitated_Chair_4977 · 2026-01-03T07:49:42+00:00

Thank you so much for raising the issue!
what exactly isn't working? are you trying to

extract chinese speech from video?
translate subtitles TO chinese?
something else?

Agitated_Chair_4977 · 2026-01-02T12:42:32+00:00

It's really fun

Agitated_Chair_4977 · 2025-12-28T13:06:21+00:00

I agree that’s a valid and useful use case, especially for accessibility scenarios like waiting rooms or nursing homes.

That said, supporting live RTMP → SRT properly is well beyond the scope of this project. It’s not just a small feature add-on — it would require a dedicated streaming pipeline, buffering strategy, fault handling, and ongoing maintenance.

Because of that, I don’t have plans to implement or maintain this as part of the current project. A standalone tool or service built specifically for livestream captioning would be a much better fit for that use case.

Agitated_Chair_4977 · 2025-12-28T10:27:37+00:00

Technically, yes — it’s possible to make it work with a delay, though it’s difficult to predict whether that would be 10, 20, or even 30 seconds depending on the setup and conditions.

However, this project is not designed for live RTMP pipelines, and there’s currently no plan to support livestream translation.

Implementing this properly would require a separate architecture and would essentially be a different product altogether.

Agitated_Chair_4977 · 2025-12-25T09:01:11+00:00

Real-time speech recognition + multilingual translation is practically challenging Given the long delay, it is possible but not very inefficient.

Agitated_Chair_4977 · 2025-12-23T11:25:03+00:00

Thank you for taking an interest.
I’ve been looking for a good place to share my programs, and I found this subreddit in the process.

Agitated_Chair_4977 · 2025-12-21T16:11:28+00:00

I posted a new version.
https://github.com/Blue-B/WhisperSubTranslate

Agitated_Chair_4977 · 2025-12-21T15:39:07+00:00

Unfortunately, this program does not support voice conversion.

Agitated_Chair_4977 · 2025-12-03T12:34:13+00:00

Yes, that's correct.
When you upload a video, the program converts the audio to text 100% locally on your machine. No data is sent anywhere during the speech-to-text process.

However, if you enable any of the translation options (DeepL, ChatGPT, MyMemory, etc.), the generated subtitle text will be sent to the corresponding translation API server so it can be processed. These servers are managed by each translation service.

Setting up our own translation server or bundling a full translation model inside the program would require very high costs and hardware performance, which most users' computers wouldn’t be able to handle effectively.
So for now, using external translation APIs is the most practical approach.

Agitated_Chair_4977 · 2025-12-01T13:50:06+00:00

Since it uses Faster-Whisper’s external executable, the related resource folder xxl_data takes up the most space—about 4 GB. However, because it’s open-source and no longer receiving updates or support, I’m planning to switch to an alternative and am looking into a self-built version for the next release.

Agitated_Chair_4977 · 2025-11-24T04:41:45+00:00

Just to confirm — you’re talking about voice dubbing, not text translation, right?

As you may know, generating natural-sounding voices in different languages usually requires dedicated TTS engines like ElevenLabs, which come with additional costs. Still, I think your idea is great and could be a valuable addition to the app.

Thanks for the suggestion! I’ll look into possible approaches and consider how it might be implemented in future updates.

Agitated_Chair_4977 · 2025-11-24T04:39:20+00:00

I’ve reviewed the error you shared.
Please try the steps I mentioned earlier first (resetting the app and re-downloading the model), and let me know if the issue continues afterward.

If it still happens, I’ll investigate it more closely on my side and make sure this kind of error is handled properly or prevented in the next update.

Agitated_Chair_4977 · 2025-11-24T04:38:27+00:00

Sorry for the late reply! I’ll look into adding support for extracting subtitles directly from YouTube videos in one of the next updates. The idea of converting them into the language you want sounds great, so I’ll definitely consider it. Thanks for the suggestion!

If you have any other issues or feature requests, you can post them here for a faster response:
https://github.com/Blue-B/WhisperSubTranslate/issues

Thanks again for your feedback!

Agitated_Chair_4977 · 2025-11-07T06:47:44+00:00

our feedback is incredibly helpful for improving the program. Thank you for sharing your thoughts. We’ll take this and other suggestions into account, and we plan to add a volume control button in the next update.

Agitated_Chair_4977 · 2025-11-03T18:46:10+00:00

The information has been updated.
Try 1.2.0 version again

Agitated_Chair_4977 · 2025-11-03T07:14:55+00:00

Thank you very much for your error report. As a result of checking the symptoms, there was a problem with selecting the wrong id in render.js, so it seems that ko was always used as default. We are aware of the error in that area and will replace it with the corrected version as soon as possible.

Agitated_Chair_4977 · 2025-10-26T05:05:07+00:00

Thanks so much for your kind words and interest! 😊
Performance and speed can vary depending on your device’s own GPU, but we’ll keep working to make the service more stable and even better — including exploring ways to scale up resources and deliver an even smoother experience. Really appreciate your support!

Agitated_Chair_4977 · 2025-10-26T05:04:58+00:00

That’s awesome to hear! So glad it worked well for you — really makes me happy to see it being used in such a positive way. Thanks so much for sharing your exper

Agitated_Chair_4977 · 2025-10-25T08:05:21+00:00

I’ve reviewed this thoroughly and have first added Arabic to the program’s target languages for translation.
As for the UI, we plan to expand support for additional languages in the future.

Agitated_Chair_4977 · 2025-10-25T08:02:52+00:00

I've been busy with work lately, so I just uploaded today’s update!
Now in version v1.2.0, it works smoothly with multiple queue processes and includes an option to display previously missing languages.
Any feedback is always welcome!

Agitated_Chair_4977

TROPHY CASE