-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Voice/Video Conference Wishlist #1487
Comments
See also element-hq/element-web#1869 |
I would add screen-sharing. This is mainly why we are still using Skype at work (there might be other solutions, but that is not the question). Surprisingly, Slack doesn't have that yet either. Screen-sharing is extremely useful: for peer-reviewing, for explaining something that is easier to explain when seen, etc... |
@MightyCreak screen-sharing already exists, although it is hidden (Shift-click on the video call button), and it requires special things to be done for the browser to allow it (setting a config option in Firefox (#1312) and either a command-line argument or a custom extension (#238) for Chrome). However, it should just work in the desktop version. |
My wishlist: |
These are all excellent wishes. Right now we're focused on making it work at all(!), and have just kicked off work on a new conferencing server which can hopefully evolve in this direction. It's based on our old pre-Matrix proprietary codebase, but we're assuming we'll FOSS it if it works out okay. @superdump has the conn here :) |
It would also be nice to be able to control volume per person (user setting). From what I heard right now all streams are mixed into 1 by the homeserver, so I guess that new conferencing server could help in this. And of course simple things like push to talk and send-on-voice-detection (although I'm not sure if the latter is possible within a web-app). |
One thing that IMHO is quite important is adaptive bandwidth management. What I mean with that is that the Voice/Video part should be able to adapt to bandwidth restrictions ( static or dynamic ) by scaling the codec bandwidth used to encode the data. |
Ability to share screen and video at the same time |
I'd really like to see jitsi/jitsi-meet#688 and jitsi/jitsi-meet#30 but AIUI they would have to be handled upstream Should this and element-hq/element-web#1869 be merged into #1482? |
IMHO, this, element-hq/element-web#1869, and #1482 have slightly different scopes. #1482 seems to be more about 1:1 calls, element-hq/element-web#1869 seems to be mostly about improving quality, while this issue is more of a long-term wishlist. |
@uhoreg ah, that makes sense. has the new Jitsi integration taken care of any of the items listed in these three issues? |
I haven't tried the Jitsi integration, so I don't know, but looking over this list, it doesn't look like much has been fixed, aside from "ability to invite others by sending them a link without requiring a Matrix account (similar to meet.jit.si or appear.in)" (though I don't know how discoverable the link is, so it might be better to leave that open), and maybe "adaptive bandwidth management", if Jitsi does that. @superdump would probably know better, especially regarding whether any of the issues from element-hq/element-web#1869 are fixed. |
So how soon before we can get push to talk or other stuff hammered out? Last update was Sept of last year (2017). |
Not sure how I unassigned @superdump ?_? |
i think that's a bug in github. @superdump is sadly no longer part of the matrix core team, and GH presumably only just noticed and unassigned. right now we're not working on new features but prioritising getting the current ones polished and stable to a 1.0 release. |
@ara4n is there a target timeline for 1.0 release? PTT is pretty paramount for a lot of riot usage that I and others are looking to do. |
This looks interesting (video transport architecture that outperforms WebRTC, Skype, FaceTime, Hangouts, etc), albeit probably something that would need to be done upstream: https://snr.stanford.edu/salsify/ I filed an issue against Jitsi-Meet to look into it: jitsi/jitsi-meet#2819 |
Screen Sharing feature implemented more that year ago, but why it still hidden via Shift+click hack? |
Well, I believe the default VoIP and video call systems are to be replaced by Jitsi, which already has screen sharing working as well. Wouldn't make sense imo to spend effort on the old system if it's going to be replaced (and already is on mobile) anyway. |
Wait, it's a hidden feature? WUT? Is the current screen sharing Jitsi or Freeswitch, or what? |
Jitsi widget is too hard to find for regular users, so all use "Video call" button near to file upload. And using it there are no way to switch between camera & screen sharing, we can only initiate screen sharing call via shift+click, but nowhere is written about this in Riot interface. |
Does moving to Jitsi mean that for private, isolated (not federated, not relying on any external infrastructure) homeservers you need to setup an integration server (or possibly use vector.im) to get screen sharing to work? |
Definitely: why?! Where to Shift-click to activate it? Ha, found: Shift-click on camera call. |
Moderators At the moment the user starting the conference becomes the moderator. |
As explain in here, Native Group Voice/Video Conferencing is coming and this is very exciting. I would like to write some wishes I have for this native video conferencing system :
|
This comment was marked as spam.
This comment was marked as spam.
@BloodyIron that's been requested here: element-hq/element-call#202 |
Actually it was originally requested, by me, over 4 years ago, here : element-hq/element-web#5993 Also, element-hq/element-web#202 was closed. I have also brought up the request in element-hq/element-web#218 since that may be the latest issue on the matter. |
The fact that you need a camera to even get the option to share your screen is pretty annoying and an artificial limit that doesn't make much sense. |
Here are a bunch of things that I would like to see support for in conferencing, in order to support different uses.
Additional suggestions from the comments below:
The text was updated successfully, but these errors were encountered: