-
-
Notifications
You must be signed in to change notification settings - Fork 270
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
Video and Voice Calling #528
Comments
+1 Support/integration of Element Call (https://github.com/vector-im/element-call). |
|
This would be great, as I could finally replace element with something much nicer to use IMO. I currently have to use element to talk to my friends over VoIP. |
I want to implement this. Does anyone have any pointers? (I have no experience with matrix APIs). |
This is blocked by matrix-org/matrix-js-sdk#2553 |
the pr is now merged |
Could you link it? |
I am currently preoccupied by other projects, so I will not be implementing this in the foreseeable future. I will post a comment if I decide to pick this up again. |
no worries! |
I'd like to mention that I think using element call as a backend would be great, but it would make more sense to develop a user interface for it which follows the cinny design language. This could always be added down the line after just sloppily importing it though, so I'm not too worried about it, but one of the biggest strengths of cinny is how uniform its design language is. |
This comment was marked as off-topic.
This comment was marked as off-topic.
has any progress been made on this topic? |
Pretty sure none has |
well that's kinda sad |
Still the one thing holding me back from really daily driving matrix (including screen sharing with audio, but id at least use it a lot more if any form of calling was implemented) |
The problem is matrix itself is moving away from jitsi and into its own [matrix VOIP](https://element.io/blog/introducing-native-matrix-voip-with-element-call/)
|
@FarisZR This is a temporary solution until Cinny devs figure out how they're going to handle calls, I do not want my draft to be merged. |
Would adding in voice/video call functionality to Cinny include Discord-like voice/video rooms ("Rooms" in the sense of being able to pop in and out)? |
So should we wait for Element Call, hoping that it will replace both Jitsi for conference calls, and Coturn servers for 1:1 calling, or is Element Call only replacing Jitsi? If that's the case, we'd still be missing the regular 1:1 call feature in Cinny, using self-hosted Coturn servers, as available in Element. |
AFAIK element call is just element 1:1 calls but for groups.
|
Element already has this functionality. |
He was probably referring to the UI simplicity of Discord, as in showing small Avatars that are in the voice channel call, and the ability to join by clicking the Channel, and leave with a disconnect button on the bottom of the UI. |
Correct, this is what I am referring to. Popping in and out of a persistent channel is an incredibly useful feature. |
Element has video rooms already and they're pretty stable as far as I know. Is there anything blocking this from being implemented? EDIT: Never mind, element uses Jitsi for video rooms (for now until element call is stable)
|
I think you should just work on embedding element Call inside Cinny similar to how Jitsi currently works in element. In any case, the project should definitely skip implementing Jitsi. |
I am also in favor of adding VoIP to Cinny, however I am not sure whether implementing Element Call is the right way to go. Currently Element Call is a pain to set up and I would not consider version 0.5 to be "almost ready". Element Call feels unfinished and more like a prove of concept, rather than a feature which is ready to be implemented. If I am not mistaken, implementing Element Call in Cinny would mean to add a Room which hosts an iframe to In that case anyone wanting a call feature could just host Element Call separately and link it to their Matrix instance instead. While this is probably not the prettiest way of doing things, its probably more pretty than including Element Call as an iframe in Cinny which breaks the theme consistency and having to implement the feature anew once a proper solution arrives, eg. native VoIP via Matrix. |
I think we should have 1 on 1 voice calling until group calling is fully fledged out. |
The proposals will probably be finished in a couple months and it would be better to wait than to implement a soon-to-be-dated version of calls. I think it would be a great disservice to the much appealing design of Cinny to simply embed Element Call rather than to follow it to its conclusion and implement video rooms like Discord voice channels. |
In the meantime an Element call widget would be really useful though. |
@deepadmax where can these proposals be found? Apparently element call is production ready now 🎉 https://element.io/blog/we-have-lift-off-element-x-call-and-server-suite-are-ready/ Regarding the idea of implementing Discord-like voice channels: Has there been any discussion about this with the core maintainers of Cinny? It would be good to agree on this first, so that if someone starts working on it, they won’t have to make significant changes later on. Personally I think it's a great idea, but I'm not yet sure if Element Call is fast enough to make popping in and out of a call as seamless as it is on Discord. Another thing to note is on Discord, the UI is updated with your profile appearing in the call list before you have actually connected to the call backend. |
I am not sure what the blog post is talking about. Maybe I am misunderstanding the procedure, but the proposals for VoIP via Matrix still have not been merged. I have come to the conclusion that I don't understand what I should expect from Element-X, Element Call or VoIP in Matrix. |
This would be great addition to cinny |
Describe the problem
Currently, there is no way to voice call someone in Cinny.
Describe the solution you'd like
An option to voice call ppl :)
Alternatives considered
Using another matrix client
Additional context
No response
The text was updated successfully, but these errors were encountered: