@jallamsetty, I tested again last night with 4 clients - 2 different browsers on a mac (mac 1, mac 2), the desktop app on a windows machine (win) and one client connecting through the mobile app (mobile). The camera on the mac only goes up to 720p. Findings are:
Reading from Mac 1
Mac 1 - 1280x720
Mac 2 - 320x180
Win - 320x240
Mobile (Android) app
Reading from Windows Machine
Mac 1 - 320x180 (both in tile view AND speaker view!)
Mac 2 - 240X135
Win - 640x480
Mobile - 320x180
Not sure how well you can see these, but these are screenshots of Mac 1’s feed during the same call:
Mac 1 Local feed (1280x720)
Mac 1 viewed from Mac 2 (320x180)
I then commented out the “minHeightForQualityLvl” settings to set back to default and the results were the same. I tried changing values for layer suspension as well, no change. I didn’t touch “maxBitratesVideo” throughout (remained at default values - commented out). I didn’t see a need to change that because I wasn’t trying to restrict the maximum resolution.
Bandwidth measurement is:
I didn’t see anything significant in the browser js console log, but here’s a snip:
And it just occurred to me you mighthave been asking for the logs from the “save logs” link. Not sure I have one of this actual test, but here’s one from a similar test a day before.
meetlog-test.txt (441.7 KB)
So, there you have it.
One deeply-concerning observation is that the link/feature “Save Logs” is actually available to ALL participants in a meeting (not just the authenticated moderator). This log contains very sensitive information (IP addresses, server details e.t.c…). Not sure why making this information available to all participants was considered a positive, but it’s not an exposure I can risk. So, I’ll be downgrading my Jitsi to a previous version - for that reason and also for these feed quality issues.