Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • fairmeeting fairmeeting
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 49
    • Issues 49
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • hosting
  • fairmeetingfairmeeting
  • Issues
  • #172
Closed
Open
Created Jan 26, 2022 by Roland Alton@roland.altonOwner

Screenshare blurs when sent from Chrome

We had feedback from customers https://git.fairkom.net/clients/ronge-partner/wlfairmeeting/-/issues/35 https://git.fairkom.net/clients/ekir/jitsi/-/issues/24 that in some constellations shared screen blurs at end users.

After doing a lot of testing and reading in the Jitsi community forum @dimitri.hofer found the recommendation, that the default setting of 5 fps should NOT be changed.

If the frame rate is different than the default 5 fps, Chrome is doing simulcast and may send lower resolution to some or all users.

  // desktopSharingFrameRate.max now determines whether simulcast will be enabled
  // or disabled for the screenshare.

  // Optional desktop sharing frame rate options. Default value: min:5, max:5.
  // desktopSharingFrameRate: {
  //     min: 5,
  //     max: 5
  // },

If higher frame rates are needed (e.g. for sharing a video), a user can change the fps in the UI. Firefox is recommended in that case.

meet.jit.si has not anymore set the fps in the config at all

Edited Jan 26, 2022 by Roland Alton
Assignee
Assign to
Time tracking

gitlab project and software management by fairkom.eu - more open source web apps at fairapps.net