BBB version 3.0.23
latest bbb-livekit-stt
When choosing "Auto Detect" in the language dialog of closed captions the feature does not work.
I had contact w/ an engineer @gladia who helped me tracing down the issue.
the failure comes specifically from BBB sending the user-selected locale “auto" through the integration, which then ends up as languages: ["auto"].
I checked the path more closely: the “Auto detect” option does appear to come from BBB core/UI, while the actual mapping into the Gladia request is done in bbb-livekit-stt. So the most practical fix is in the integration layer: when BBB sends "auto", we should omit the initial language parameter and, on updates, send an empty languages list instead of ["auto"]. Gladia’s API supports that and falls back to auto-detection in that case.
I’ve already prepared that fix on a branch and opened it upstream here: #14 . I have not signed the BBB Contributor License Agreement , so they may not be able to review or merge it until that is in place. If useful on your side, you can still copy the change from the PR and re-open it as you’ve signed the License Agreement?
I tested the PR from from @lrossillon-gladia in our setup and the issue went away.
@fcecagno @lfzawacki As I know you are working on this topic could you please have a look if you can reproduce this?
BBB version 3.0.23
latest bbb-livekit-stt
When choosing "Auto Detect" in the language dialog of closed captions the feature does not work.
I had contact w/ an engineer @gladia who helped me tracing down the issue.
I tested the PR from from @lrossillon-gladia in our setup and the issue went away.
@fcecagno @lfzawacki As I know you are working on this topic could you please have a look if you can reproduce this?