Keeps Chinese source text visible instead of replacing it with translation.
Personal Language Layer
A personal language layer is the structured set of Chinese text, pinyin, meaning, timing, and subtitle output that SubChinese adds to a video the user already cares about.
A focused path from speech to subtitle file.
Adds pinyin as a reading layer, not as a separate disconnected transcript.
Keeps English optional so meaning helps without taking over the video.
Turns a single viewing session into a reusable review surface.
How this capability fits the SubChinese workflow.
- 01
Start from a Chinese video the user already has. The product begins with the source rather than assuming a useful platform caption track exists.
- 02
Create timed Chinese segments. Each sentence becomes an addressable unit that can be replayed, checked, corrected, and exported.
- 03
Connect the reading and meaning layers. Pinyin belongs to the Chinese characters, while English remains an optional interpretation layer.
- 04
Choose the output that matches the job. SRT carries portable timed language. ASS carries more deliberate learning layout.
The capability in context.
| Layer | User-facing role | What it helps protect |
|---|---|---|
| Chinese source | The written record of speech | Accuracy and accountability |
| Pinyin | The reading path | Pronunciation-to-character connection |
| English | The meaning check | Comprehension without source replacement |
| Timing | The playback structure | A phrase’s place in the video |
| Export | The portable result | Reuse beyond the browser |
Why a personal language layer is stronger than a transcript.
A transcript is a document. A personal language layer is a relationship between the document and the video. That difference matters because a viewer does not only want to know what was said; they want to connect what they hear with what they see and what they understand. If the text is separated from the source, the learner loses the timing, tone, and context that made the sentence meaningful.
SubChinese frames the result as a layer because the video remains central. The Chinese line, pinyin, English note, and export format are all placed around the original speech. The viewer can pause, replay, correct, and return to the same line later. This creates a more durable asset than a one-time transcription result.
The word personal also matters. The videos are not generic practice clips. They may be interviews, dramas, tutorials, short clips, lectures, or recordings that the user chose. The language layer lets the user turn that chosen content into something easier to understand without forcing it into a fixed course structure.
Why the capability matters in real content
Real Chinese videos are not arranged like beginner material. They contain names, unfinished sentences, cultural references, casual reductions, repeated phrases, and changes in speaking speed. A useful product has to support understanding without pretending that every line can be reduced to a perfect textbook example.
That is why SubChinese keeps the source, timing, reading support, and meaning support connected. The user can decide which layer deserves attention at a particular moment: listen first, read the Chinese, check pinyin, reveal English, or return to the same phrase later.
The result is a more respectful kind of assistance. It does not replace the content that made the video valuable. It gives the viewer a clearer way to approach it.
Why this is a product capability, not a marketing label
A capability should be visible in the user workflow. It should explain an action the user can take, a problem the user can avoid, or a result the user can keep. The SubChinese capability pages are designed around that standard: each concept appears in the preview, editor, playback, history, SRT export, or positioned ASS export.
This distinction also keeps the product language honest. We can describe a language layer, a reading relationship, or a frame-aware layout without claiming that automatic output is perfect. The value is in the structure that makes understanding and correction easier.
Why paid users should care about continuity.
A free user needs to confirm that the workflow works. A paid user needs continuity. They want previous work to remain accessible, editable, and exportable. The personal language layer explains why saved history, subtitle files, and re-exporting are worth paying for: the result is not disposable text, but a reusable study surface tied to content the user already values.
More minutes are useful, but they are not the emotional reason to pay. The stronger reason is ownership: the user is building a private library of Chinese content with language support attached.
Start from a file, not an existing subtitle track.
Sign in first, then upload a local video, review the generated transcript, keep English optional, and download a subtitle file.
When this capability is not the right emphasis.
- If the user only needs a one-time summary, a full subtitle language layer may be more structure than necessary.
- If the source does not contain Chinese speech, the Chinese-focused workflow is not the right fit.
- If the destination player cannot support the chosen layout, the user should choose the more compatible output.
The product should make the useful layer available without forcing every viewer to display every layer at once.
Questions about personal language layer.
Is this an implementation document?
No. It explains the user-facing product theory and capability. Internal infrastructure and provider details are intentionally not part of the public page.
Does automatic output still need review?
Yes. Names, context, homophones, segmentation, and translation nuance can require human judgement. The product makes review structured and reusable.
How do the capabilities connect?
They share the same timed language segments, so Chinese, pinyin, English, playback, editing, and export stay connected.