> For the complete documentation index, see [llms.txt](https://docs.hudson-ai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hudson-ai.com/dubbing-studio-guide-jp/help-center/faq.md).

# FAQ

#### #1. “I clicked Export, but it downloaded the unedited version. Was my dubbing not saved?”

<figure><img src="/files/lpHCvKljDv9Hnd5ByX7J" alt="" width="375"><figcaption></figcaption></figure>

No worries—your edits are safe!

On the export screen, the first video/subtitle in the list is the unedited version.\ <mark style="color:red;background-color:yellow;">**To download your final version with all edits applied, make sure to click the orange “Export” button first.**</mark>

Only then will the changes be included in the downloaded file.

***

#### #2. “Sometimes words starting with J are pronounced like a Y. How can I fix incorrect pronunciations?”

<figure><img src="/files/hG238zyfUSb03gPh8oAX" alt=""><figcaption></figcaption></figure>

If regenerating takes doesn't fix the pronunciation, try entering the word <mark style="color:red;background-color:yellow;">**in your project’s original language (source language).**</mark>

This method works across all versions of Timbr Studio: ATC, TC, and CC.

{% hint style="success" %}
If "Jung-gu" isn’t pronounced correctly;&#x20;

It's raining in "Jung-gu". ➡️ (If your source language is Korean)  It's raining in "중구".
{% endhint %}

***

#### #3. “The dubbed voice sounds slow—like it's in slow motion. What should I do?”

This happens when the original script is long but the translated dubbing is short, leaving too much silence.

Here's how to fix it:

* Shorten the clip duration in the Timeline <mark style="color:red;background-color:yellow;">**by clicking and dragging the clip forward.**</mark>\
  This naturally increases the speech speed.
* Use the <mark style="color:red;background-color:yellow;">**AI Translation Tools**</mark> to rewrite the line with longer, richer phrases. Try clicking “Lengthen Translation” to fill the space more naturally.
* You can also fine-tune the rhythm using punctuation:
  * <mark style="color:red;background-color:yellow;">**... (ellipses)**</mark>
  * <mark style="color:red;background-color:yellow;">**\~ (tilde)**</mark>
  * <mark style="color:red;background-color:yellow;">**- (dash)**</mark>\
    These help stretch words or insert subtle pauses.

***

#### #4. “Why isn't the original speech being transcribed?”

If your content includes unsupported languages, the auto-transcription won’t work.

In that case, you need to manually <mark style="color:red;background-color:yellow;">**edit the script in your project’s source language.**</mark>

> For example:\
> If your video contains Burmese, which isn’t currently supported by Timbr, transcription will not work for those sections. In this case, translate the Burmese audio into your project’s source language (e.g. English) and **manually input** the text into the transcription field.

{% hint style="success" %}
ကျေးဇူးတင်ပါတယ်(Burmese section) ➡️ Thank you (English translation)
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hudson-ai.com/dubbing-studio-guide-jp/help-center/faq.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.