search

luvolondon / fvtt-module-jitsiwebrtc

Jitsi WebRTC client for FVTT
32 stars 8 forks source link

Low Frame Rate with 0.5.3 #71

Closed Dick-K closed 3 years ago

Dick-K commented 3 years ago

Please ignore, more analysis at my end required.

ETA: Yes, it appears to be an issue with the integral webcam in the old laptop I use for testing. Apologies.

bekriebel commented 3 years ago

Actually, something does seem to be going on. I can repro this as well, but not just with 0.5.3. I think it may actually be a change that has happened on the beta.meet.jit.si servers. If I switch to using meet.jit.si, framerate improves.

Dick-K commented 3 years ago

Okay, I'll give that a shot. Thanks for getting back to me anyway, and so quickly. Many thanks, your module is a life-saver 👍cheers

On Wed, Mar 31, 2021 at 6:28 PM Brint E. Kriebel @.***> wrote:

Actually, something does seem to be going on. I can repro this as well, but not just with 0.5.3. I think it may actually be a change that has happened on the beta.meet.jit.si servers. If I switch to using meet.jit.si, framerate improves.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/luvolondon/fvtt-module-jitsiwebrtc/issues/71#issuecomment-811272822, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARSPGOBEZYY72WFFOQGKRFTTGNLS7ANCNFSM42E7MWFQ .

bekriebel commented 3 years ago

I've found the issue as well. It looks like they've enabled an experimental feature on the beta servers that is causing the lag. I can override the setting to fix it. I'll push an update later today with this change. Thanks for reporting it!

Dick-K commented 3 years ago

Yes, I concur. I previously specified the signalling server as the embedded Public Jitsi Meet Beta and the relay server as meet-jit-si-turnrelay.jitsi.net http://meet-jit-si-turnrelay.jitsi.net.

Using meet.jit.si http://meet.jit.si on its own with the relay server set to meet-jit-si-turnrelay.jitsi.net http://meet-jit-si-turnrelay.jitsi.net made no difference but using meet.jit.si http://meet.jit.si with the relay server set to Provided by signalling server appears to have restored an acceptable framerate.

Thanks again.

On Wed, Mar 31, 2021 at 6:30 PM Dick Keable @.***> wrote:

Okay, I'll give that a shot. Thanks for getting back to me anyway, and so quickly. Many thanks, your module is a life-saver 👍cheers

On Wed, Mar 31, 2021 at 6:28 PM Brint E. Kriebel @.***> wrote:

Actually, something does seem to be going on. I can repro this as well, but not just with 0.5.3. I think it may actually be a change that has happened on the beta.meet.jit.si servers. If I switch to using meet.jit.si, framerate improves.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/luvolondon/fvtt-module-jitsiwebrtc/issues/71#issuecomment-811272822, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARSPGOBEZYY72WFFOQGKRFTTGNLS7ANCNFSM42E7MWFQ .

Dick-K commented 3 years ago

Nice job with such a quick and informed response.

bekriebel commented 3 years ago

This should be resolved with v0.5.4.

Dick-K commented 3 years ago

Just upgraded, it's working fine now. Many thanks Brint, all the best 👍

On Wed, Mar 31, 2021 at 8:18 PM Brint E. Kriebel @.***> wrote:

This should be resolved with v0.5.4.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/luvolondon/fvtt-module-jitsiwebrtc/issues/71#issuecomment-811365296, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARSPGOAEYTPN46FIVT7ETKLTGNYOTANCNFSM42E7MWFQ .