Live Caption language pack constraints and automatic switching behavior
0 reputation · 29 Sept 2023, 02:12 UTC
0 reputation · 29 Sept 2023, 02:12 UTC
Chrome's Live Caption feature relies on on-device machine learning models to provide real-time transcription of audio. To maintain privacy and offline functionality, the browser downloads specific language packs to handle the audio-to-text conversion process.
While the feature supports multiple languages, there is uncertainty regarding how the browser manages transitions between different languages within a single audio stream or across multiple open tabs playing different languages simultaneously.
Does Chrome support automatic language detection for Live Caption, or must the user manually select the language pack for each session? How does the feature handle mixed-language audio streams?
34775 reputation · 29 Sept 2023, 11:59 UTC
Chrome Live Caption does not support automatic language detection. The feature requires a specific language pack to be downloaded and active to perform on-device transcription. If the audio language changes, the user must manually update the selection in the browser settings; the system will not dynamically switch packs based on the audio stream's content.
Because only one transcription model can be active at a time, the following behaviors occur during complex audio scenarios:
To manage language packs or verify the current state, use the following steps:
chrome://settings/accessibility to enable Live Caption and add or remove supported language packs.chrome://media-internals/.This behavior is based on the standard implementation of Chrome's on-device ML models. We assume a stable internet connection for the initial download of language packs, as transcription is performed locally once the pack is cached. Because browser updates frequently modify accessibility features, users should verify their specific version's support for additional languages in the settings menu.
Diagnostic Detail Needed: Are you experiencing this across different operating systems (e.g., Windows vs. macOS), as some OS-level accessibility hooks can occasionally interfere with browser-level transcription?
Use comments to ask for clarification. Post a solution as an answer.
34,775 reputation · 29 Sept 2023, 11:41 UTC
A useful distinction to test is between “no automatic switching” and “no automatic language detection.” Chrome releases and operating systems can expose different Live Caption controls, so the blanket statement should be checked against the current UI rather than inferred from an old settings screenshot.
For a Chrome stable build, record the exact version at chrome://version, then open chrome://settings/accessibility → Live Caption → Language. Note whether an Auto or Detect language choice appears, which packs are installed, and whether any detection option is limited to particular languages. Test short clips in each candidate language, including one that changes mid-clip.
That matrix can reveal whether detection switches the pack, labels the caption only, or is unavailable on that platform. Until the current build is verified, describe the behavior as version-dependent rather than universal.