Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Initial implementation of Gladia transcriptions to BBB 2.7 #19091

Merged
merged 28 commits into from Nov 30, 2023

Conversation

lfzawacki
Copy link
Collaborator

@lfzawacki lfzawacki commented Nov 8, 2023

Still a work in progress, adds few UI/UX elements to support gladia options and a new message used for configuring the transcription backend.

Should be used with this branch of bbb-transcriptions-controller

HTML5 settings in setting.yml:

To enable Gladia support in the HTML5 client:

 audioCaptions:
   enabled: true
   # makes the CC button visible by default
   alwaysVisibile: true
   provider: gladia

For the transcription pad:

 captions:
   enabled: true
   # Hides the old CC button that was used to open the transcription pad.
   # This makes less sense when used together with transcriptions so we hide it
   showButton: false 

The current transcription settings can be configured via userdata parameters on join. Here are the parameters:

userdata-bbb_transcription_partial_utterances -> Boolean: [true, false]
    Enables/disables the use of partial utterance results. These
    are lower quality results that have the advantage of arriving
    faster than the final, and more accurate, results.
    
    The default value is *true*.

userdata-bbb_transcription_min_utterance_length -> Integer: [0,5]
    This value is measured in seconds and denotes the minimum
    size of a partial utterance for it to be considered as valid. Lower
    values will yield quicker and more inacurrate results and vice-versa.
    This can be a good way to balance speed with more accurate results.

    The default value is *3*

userdata-bbb_transcription_provider -> [webspeech, gladia, vosk]
    Sets the transcription provider for this user. 'webspeech' will use
    the old browser based system which is enabled by default on
    most BBB instances. Both 'gladia' and 'vosk' will make BBB use
    the new 'transcription controller' system. 

TODO

  • Long results coming from gladia should be split so we don't lose any text

@antobinary antobinary added this to the Release 2.7 milestone Nov 8, 2023
@antobinary antobinary marked this pull request as draft November 8, 2023 19:58
@antobinary antobinary marked this pull request as ready for review November 24, 2023 18:42
@jqueguiner
Copy link

Long results can be handled with endpointing. We are thinking also to add an option to force transcription to maximum Xsec. It should take the min(speech_with_endpointing_trigger, max_Xsec)

Copy link

Automated tests Summary

All the CI tests have passed!

@antobinary antobinary changed the title Initial implementation of Gladia transcriptions to BBB 2.7 feat: Initial implementation of Gladia transcriptions to BBB 2.7 Nov 30, 2023
Copy link

sonarcloud bot commented Nov 30, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 57 Code Smells

No Coverage information No Coverage information
2.9% 2.9% Duplication

@antobinary antobinary merged commit 125d706 into bigbluebutton:v2.7.x-release Nov 30, 2023
16 of 18 checks passed
antobinary added a commit to antobinary/bigbluebutton that referenced this pull request Mar 18, 2024
…bluebutton#19091)

---------

Co-authored-by: Anton Georgiev <anto.georgiev@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants