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

Transcriber not working for firefox clients #579

Closed
HighwayStar opened this issue Jan 13, 2025 · 5 comments
Closed

Transcriber not working for firefox clients #579

HighwayStar opened this issue Jan 13, 2025 · 5 comments

Comments

@HighwayStar
Copy link

I have up and running jitsi meet installed from docker-compose by offiicial guide based on latest stable images. I've setup vosk transcribtion and it works fine when clients using Chrome based browser, but if client using Firefox conference works overall, but not transcribtion.

When firefox client enable microphone, transcriber log looks like that

2025-01-13 21:37:05.711 INFO: [87] net.java.sip.communicator.service.protocol.media.MediaHandler.registerDynamicPTsWithStream: PT overrides []
2025-01-13 21:37:05.756 INFO: [87] net.java.sip.communicator.service.protocol.media.CallPeerMediaHandler.start: Starting
2025-01-13 21:37:06.008 INFO: [86] JvbConference$JvbCallChangeListener.callStateChangedInternal#1785: [ctx=1736775420678547489719] JVB conference call IN_PROGRESS.
2025-01-13 21:37:06.053 INFO: [96] JitsiOpenSslProvider.<clinit>#52: jitsisrtp successfully loaded for OpenSSL 3
2025-01-13 21:37:06.570 INFO: [96] Aes.benchmark#367: AES benchmark (of execution times expressed in nanoseconds): OpenSSL 1142, SunJCE 1137, BouncyCastle 14839 for AES/CTR/NoPadding
2025-01-13 21:37:06.571 INFO: [96] Aes.createCipher#433: Will employ AES implemented by SunJCE for AES/CTR/NoPadding.
2025-01-13 21:37:06.811 WARNING: [117] Transcriber.bufferReceived#731: test@muc.meet.jitsi: reading from SSRC 1023204585 while it is not known as a participant
2025-01-13 21:37:06.830 WARNING: [117] Transcriber.bufferReceived#731: test@muc.meet.jitsi: reading from SSRC 1023204585 while it is not known as a participant
2025-01-13 21:37:06.851 WARNING: [117] Transcriber.bufferReceived#731: test@muc.meet.jitsi: reading from SSRC 1023204585 while it is not known as a participant
2025-01-13 21:37:06.870 WARNING: [117] Transcriber.bufferReceived#731: test@muc.meet.jitsi: reading from SSRC 1023204585 while it is not known as a participant
2025-01-13 21:37:06.890 WARNING: [117] Transcriber.bufferReceived#731: test@muc.meet.jitsi: reading from SSRC 1023204585 while it is not known as a participant

while with Chrome client it looks like

2025-01-13 21:38:03.420 INFO: [87] net.java.sip.communicator.service.protocol.media.MediaHandler.registerDynamicPTsWithStream: Dynamic PT map: 126=rtpmap:-1 telephone-event/8000; 111=rtpmap:-1 opus/48000/2 fmtp:useinbandfec=1;minptime=10; 
2025-01-13 21:38:03.420 INFO: [87] net.java.sip.communicator.service.protocol.media.MediaHandler.registerDynamicPTsWithStream: PT overrides []
2025-01-13 21:38:03.429 INFO: [87] net.java.sip.communicator.service.protocol.media.CallPeerMediaHandler.start: Starting
2025-01-13 21:38:03.450 INFO: [60] JvbConference$JvbCallChangeListener.callStateChangedInternal#1785: [ctx=17367754819711423358889] JVB conference call IN_PROGRESS.

In log file attached I've connected as single user first using Firefox and next Chrome.

transcriber.log

@damencho
Copy link
Member

We have discovered an issue with Firefox on the latest stable release of jitsi-meet. We will push a new stable shortly and you can try with it.

@damencho
Copy link
Member

Can you update to https://github.com/jitsi/docker-jitsi-meet/releases/tag/stable-9955 and see whether you reproduce it? Thank you.

@HighwayStar
Copy link
Author

Can you update to https://github.com/jitsi/docker-jitsi-meet/releases/tag/stable-9955 and see whether you reproduce it? Thank you.

I've just update, now works fine both in Chrome and Firefox, thank you for such fast fix!

@HighwayStar
Copy link
Author

Now it looks like there is regression in chrome - chat stops working on first subtitle message recieved. I've created new report in docker because didnt know where to place it, but seems related. jitsi/docker-jitsi-meet#1997

On previous releases chrome was woking fine, Firefox broken, but now Firefox Ok, chrome broken.

@damencho
Copy link
Member

That was fixed now. You can use latest my nightly/unstable to try it out

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

No branches or pull requests

2 participants