[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #33700 [Internal Services/Services Admin Team]: audio- and video-conferencing considerations

#33700: audio- and video-conferencing considerations
-------------------------------------------------+-------------------------
 Reporter:  anarcat                              |          Owner:  (none)
     Type:  project                              |         Status:
                                                 |  needs_revision
 Priority:  High                                 |      Milestone:
Component:  Internal Services/Services Admin     |        Version:
  Team                                           |
 Severity:  Major                                |     Resolution:
 Keywords:                                       |  Actual Points:
Parent ID:                                       |         Points:
 Reviewer:                                       |        Sponsor:
-------------------------------------------------+-------------------------

Comment (by anarcat):

 also, on linux jitsi eats CPU like crazy, apparently because it doesn't do
 hardware acceleration. this reddit thread has some more information:

 https://old.reddit.com/r/linux/comments/fxcyyw/jitsi_meet_features_update_april_2020/

 important quotes:

 > I've noticed high cpu usage on Linux side due to no hardware
 acceleration. Haven't noticed it in the windows side
 >
 > Chrome and Firefox don't have hardware acceleration in Linux unless you
 are running a patched version of chromium with va-api added.
 >
 > It was supposed to be enabled in Firefox 75 when using Wayland.
 >
 > To see if things would be hardware accelerated you could play a YouTube
 video 4k and see how the CPU is spking vs gpu

 > that's correct but slightly misleading. In order to get WebRTC VAAPI
 decoding support on Linux the upstream WebRTC project code would need to
 support it.
 >
 > The VAAPI work on Chromium and Firefox regarding videos is separate.
 AFAIK, no upstream support looks like it will be added soon.

 Firefox particularly has problems working with Jitsi and WebRTC because of
 missing features.

 They (Jitsi) did improve their support for non-chrome browser, apparently:

 https://github.com/jitsi/jitsi-meet/issues/4758#issuecomment-614063335

 Jitsi are also working on E2E encryption but that requires "insertable
 streams":

 https://bugzilla.mozilla.org/show_bug.cgi?id=1631263

 In general, here are the issues tagged with jitsi in the firefox
 bugtracker:

 https://bugzilla.mozilla.org/buglist.cgi?status_whiteboard_type=substring&status_whiteboard
 =jitsi-meet

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33700#comment:29>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online

_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs