# Transcript.transcribeClipProjectItem ignores languageCode and uses preference language (Windows, Premiere Beta 27.0)

**URL:** <https://forums.creativeclouddeveloper.com/t/transcript-transcribeclipprojectitem-ignores-languagecode-and-uses-preference-language-windows-premiere-beta-27-0/12162>\
**Category:** Premiere Pro\
**Created:** [September 14, 2026, 6:54am UTC](https://forums.creativeclouddeveloper.com/t/transcript-transcribeclipprojectitem-ignores-languagecode-and-uses-preference-language-windows-premiere-beta-27-0/12162 "2026-09-14T06:54:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mamoworld](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/mamoworld/32/721_2.png) [@mamoworld](https://forums.creativeclouddeveloper.com/u/mamoworld)\
**Post date:** [September 14, 2026, 6:54am UTC](https://forums.creativeclouddeveloper.com/t/transcript-transcribeclipprojectitem-ignores-languagecode-and-uses-preference-language-windows-premiere-beta-27-0/12162/1 "2026-09-14T06:54:53Z")

</div>

On Windows with Premiere Pro Beta 27.0, this direct UXP call appears to ignore the requested language:

```auto
const ok = await ppro.Transcript.transcribeClipProjectItem(
  clip,
  { languageCode: "de-DE" }
);
const transcript = JSON.parse(await ppro.Transcript.exportToJSON(clip));

```

With German audio and Premiere’s default transcription language set to English:

- `ok` is `true`, but `transcript.language` is `"en-us"` and the text is incorrect.
- Enabling language auto detection in Preferences did not resolve this.
- Manually transcribing the same audio with **German** selected produces correct German text and `"de-de"`.

This reproduces directly in the UXP debugger, without any wrapper.

Could you also clarify the intended semantics of `languageCode`: does it select the recognition language, provide a hint that automatic language detection may override, or only set the language metadata in the exported transcript? How should it interact with the default language and automatic language detection preferences?

---

<div class="post-metadata">

**Author:** ![clegleiter](https://avatars.discourse-cdn.com/v4/letter/c/3d9bf3/32.png) [@clegleiter](https://forums.creativeclouddeveloper.com/u/clegleiter)\
**Post date:** [September 14, 2026, 5:15pm UTC](https://forums.creativeclouddeveloper.com/t/transcript-transcribeclipprojectitem-ignores-languagecode-and-uses-preference-language-windows-premiere-beta-27-0/12162/2 "2026-09-14T17:15:25Z")

</div>

Hey @mamoworld

It looks like we have the option here incorrectly documented. Can you try using `language` instead of `languageCode`?

> Could you also clarify the intended semantics of `languageCode`: does it select the recognition language, provide a hint that automatic language detection may override, or only set the language metadata in the exported transcript? How should it interact with the default language and automatic language detection preferences?

It sets which language to use for the transcription. The interaction between these settings is:

- By default use transcription preferences
- The `language` option overrides the transcription preference setting
- If the “auto-detect language” preference is enabled, that overrides both the `language` option and any default preferences.

---

<div class="post-metadata">

**Author:** ![mamoworld](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.creativeclouddeveloper.com/mamoworld/32/721_2.png) [@mamoworld](https://forums.creativeclouddeveloper.com/u/mamoworld)\
**Post date:** [September 15, 2026, 5:39am UTC](https://forums.creativeclouddeveloper.com/t/transcript-transcribeclipprojectitem-ignores-languagecode-and-uses-preference-language-windows-premiere-beta-27-0/12162/3 "2026-09-15T05:39:22Z")

</div>

Thanks, @clegleiter —that explains it! Switching the native option from `languageCode` to `language` fixed our test on Windows Premiere Beta 27.0.

With auto-detection disabled and English set as the default, `{ language: "de-DE" }` produced an accurate German transcript (`de-de`). Omitting the option used English (`en-us`) and produced incorrect recognition of the same German speech.

Thanks also for clarifying the precedence of auto-detection, the API option, and the default preference!