This describes an https://meet.jit.si meeting held recently, with specific purposes to test/diagnose issues causing problems on Jitsi. We had max 12 connections (11 users) simultaneously, with some connections being manually disconnected due to technical reasons (then reconnected).
This complements recent reports by community member @cjfsyntropy. This provides additional details on the same video conf/meeting intended to test and collect real-world data, for purposes of helping to diagnose what aspects of a user’s connections/setup may have contributed, or what aspects can be ruled out as non-causal to problems.
Participants: We had max 12 connections (11 users). 9-10 users were connected at all times. (User S3 was connected 2x, simultaneously from the same PC using 2 browsers)
Duration: 1 hour 40 minutes (approx)
Server: Jitsi’s public Meet server (https://meet.jit.si)
Encryption Point-to-point encryption was enabled during the entire Meet,
between browser-clients and the Jitsi server.
Bandwidth All users were asked to set their session to use “Low Definition”.
We believe most (90%) of users did this.
This setting gave little improvement, compared to reducing the number of active cameras.
Devices: 10 participants used a computer (non-mobile). Most used a Windows PC.
(user S3 had one computer but stayed connected twice, on two browsers)
2 users (M & E) used only a smartphone for the entire meeting.
(M’s smartphone had JITSI app; E tried both Safari browser then JITSI app)
Later, user J stopped using PC and used an Android phone with JITSI app.
Internet: All users had high-speed broadband and/or high-speed cellular service.
All had used the same device/internet with Zoom with no/few problems/lag.
Microphone: Everyone had their microphone enabled during the test meeting’s first part.
Only after painful occurrences of audio feedback did we mute everyone.
During the 2nd part, many people muted their mics after we all heard
echoing/feedback coming from 1-2 unknown users. Most users remained
self-muted for a majority of the meeting’s 2nd part (1-3 unmuted at a time).
Cameras: Initially 10 participants had cameras turned on. 8-9 set it for “Low definition”.
(user E’s smartphone Safari browser did not permit the camera;
subsequently user E switched to using the JITSI app) – so 11 cameras total.
After about 40 minutes, most users turned off their cameras due to
excessively poor video quality irrespective of the browser/device used.
That allowed everyone to get/see better video (no lag, no distortion) from
the main speaker who had their camera on. During this period (total 1 hour),
only about 3-5 users had their camera on/transmitting at any time.
User profiles: 1-2 users were not tech-savvy. 4 were tech-experienced. Remaining
users had moderate experience using their device, and followed instructions.
Users/Initials: R M J E N A V C S1 S2 S3; (I am user S3)
Browsers tested: Chrome, Chromium, Firefox, Safari, Opera, Iridium, Edge, Edge (old)
Test format: This was not a fully controlled test scenario. At times users were trying
unscripted things, with others not knowing what they did until later. Generally
we informed each other by voice or in chat, about what we did/experienced.
This should be considered a real-world test, with non-systematic testing.
(additional details to be provided in a follow-on post)