obsproject / obs-studio

OBS Studio - Free and open source software for live streaming and screen recording
https://obsproject.com
GNU General Public License v2.0
60.26k stars 7.98k forks source link

Captions failed to start #8895

Open TheBoxyBear opened 1 year ago

TheBoxyBear commented 1 year ago

Operating System Info

Windows 11

Other OS

No response

OBS Studio Version

29.1.1

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/2XcjDSRDWgZ2xJQp

OBS Studio Crash Log URL

No response

Expected Behavior

When starting captions, no error message appears

Current Behavior

A "Failed to start captions" error message appears when enabling closed captions.

Steps to Reproduce

  1. Go to Tools>Closed Captions (Experimental)
  2. Configure and Enable

Anything else we should know?

Found a fix by installing the English United States language pack for Windows, all features included.

Fenrirthviti commented 1 year ago

What is your system's base language? Are you on a Windows N or other stripped version that doesn't have this installed by default, or was there another language pack installed? The captioning functionality uses the built-in Windows speech APIs, but I don't believe it should require the English US specifically to work.

TheBoxyBear commented 1 year ago

Vanilla Windows 11 Professional with Canadian French installed.

RytoEX commented 1 year ago

What does the "Language" drop down in the "Captions (Experimental)" window look like? Ideally, with and without the English (US) language pack installed.

TheBoxyBear commented 1 year ago

The dropdown is the same regardless of if English is installed.

RytoEX commented 1 year ago

The dropdown is the same regardless of if English is installed.

Could you please provide a screenshot?

TheBoxyBear commented 1 year ago

After uninstalling the English language pack and rebooting, the error doesn't occur. image

Fenrirthviti commented 1 year ago

It looks like the core of the issue here is that Windows captioning supports only specific languages, but our error message is not explicit enough to communicate that. I haven't checked if MS provides a support matrix for languages, but it might be possible to link this in the error itself.