-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Chat not working after transcript announce message recieved #1997
Comments
And seems it happens only on chrome based browsers, when Firefox clients have chat working |
did some tests, looks more like chat stops working on first subtitle message recieved. If I starting transcribtion with switched off mics chat works until mic enabled and subtitle message sent. |
I did some js debugging, and it seem
in middleware.js function _endpointMessageReceived(store, next, action) result is undefined, and next it crashes in _getPrimaryLanguageCode() |
I've tried to lunch minimal eaxample, here is my env file attached. starting like
vosk container running on separate machine I also checked with previous release 9909 and here chrome working fine, but Firefox was broken. Will try one older. |
Thanks for digging all the way down! |
If we are not requesting any transcription, `language` will be `null` so take that into consideration when checking if we should stop processing a transcription message after firing the API event. Fixes: jitsi/docker-jitsi-meet#1997
Fix: #1997 |
Now works fine, thank you for fix. |
Thanks for confirming! |
I'm using docker installation of jitsi stable-9955 with vosk transcription, JIGASI_TRANSCRIBER_ADVERTISE_URL=true
Faced strange issue:
When conference created and users connected thay could use chat wihout issue, but when moderator enables Subtitles and Announcement message appeared in chat it became broken. Users who post messages in chat cannot see its own messages, while moderator can see it.
Chat became broken on clients after such error in js console
Full js log attached.
meet-1736933516132.log
The text was updated successfully, but these errors were encountered: