-
Notifications
You must be signed in to change notification settings - Fork 380
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
MSC3077: Support for multi-stream VoIP #3077
MSC3077: Support for multi-stream VoIP #3077
Conversation
Signed-off-by: Šimon Brandner <[email protected]>
Signed-off-by: Šimon Brandner <[email protected]>
Signed-off-by: Šimon Brandner <[email protected]>
Co-authored-by: Tulir Asokan <[email protected]>
Signed-off-by: Šimon Brandner <[email protected]>
…atrix-doc into msc/sdp-metadata
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
screenshare when 👀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Follow-up: I would suggest adding some more explanation to what m.usermedia
and m.screenshare
actually means in this (new?) context, to understand what this adds exactly, but otherwise, this looks good.
Signed-off-by: Šimon Brandner <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
otherwise this looks great - congrats on your first MSC :)
I would be tempted to skip the capability advertisement for this and just say that the absence of stream metadata means clients just take the first or whatever MSC2746 says. I can't think of anything the capability advertisement caters for specifically? - Dave Signed-off-by: Šimon Brandner <[email protected]>
Signed-off-by: Šimon Brandner <[email protected]>
Signed-off-by: Šimon Brandner <[email protected]>
Signed-off-by: Šimon Brandner <[email protected]>
proposals/3077-multi-stream-voip.md
Outdated
|
||
+ `purpose` - a string indicating the purpose of the stream. For compatibility | ||
between clients values `m.usermedia` and `m.screenshare` are defined. | ||
`m.usermedia` is the stream that contains the webcam and microphone tracks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
continuing thread on whether we should identify front/rear facing cameras with this, for purposes like when the user rotates the camera and the same stream changes to a different camera (eg. FaceTime displays an animation on the remote side to show that the camera has changed). I feel like this is probably something for separate MSC, unless we want two separate purposes for front/rear camera.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, unless we want a separate purpose
for that probably a separate MSC. If we wanted a separate purpose
, would we have m.usermedia
, m.usermedia.front
and m.usermedia.rear
or something else?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
eg. FaceTime displays an animation on the remote side to show that the camera has changed
This bit seems more like a stream replacement problem rather than a purpose
problem. But... maybe we could allow sending both and set a main stream which would tell the client on the other side to do the animation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My suggestion would be adding something like camere_type
to further distinguish the cameras - this way not all clients need to support this and we avoid having two purpose
s that are almost the same
Co-authored-by: Richard van der Hoff <[email protected]>
Co-authored-by: Richard van der Hoff <[email protected]>
Co-authored-by: Richard van der Hoff <[email protected]>
The final comment period, with a disposition to merge, as per the review above, is now complete. |
* Draft of multi-stream MSC Signed-off-by: Šimon Brandner <[email protected]> * Remove unnecessary article and don't use CamelCase Signed-off-by: Šimon Brandner <[email protected]> * Fix naming and MSC number Signed-off-by: Šimon Brandner <[email protected]> * Make it prefixy Co-authored-by: Tulir Asokan <[email protected]> * Be more descriptive about keys Signed-off-by: Šimon Brandner <[email protected]> * Add more info about usermedia and screenshare Signed-off-by: Šimon Brandner <[email protected]> * Simplifie backwards compatibility I would be tempted to skip the capability advertisement for this and just say that the absence of stream metadata means clients just take the first or whatever MSC2746 says. I can't think of anything the capability advertisement caters for specifically? - Dave Signed-off-by: Šimon Brandner <[email protected]> * Reword parts of backwards compatibility section Signed-off-by: Šimon Brandner <[email protected]> * Improve explanation of backwards compatibility Signed-off-by: Šimon Brandner <[email protected]> * Add missing spaces to unstable perifix table Signed-off-by: Šimon Brandner <[email protected]> * Remove support for stream-replacement Signed-off-by: Šimon Brandner <[email protected]> * Apply suggestions from code review Co-authored-by: Andrew Morgan <[email protected]> * Fix concerns Signed-off-by: Šimon Brandner <[email protected]> * Link to specific spec version Co-authored-by: Richard van der Hoff <[email protected]> * Be more readable Co-authored-by: Richard van der Hoff <[email protected]> * Clarify Co-authored-by: Richard van der Hoff <[email protected]> * Don't ref non-existing thing Co-authored-by: Richard van der Hoff <[email protected]> * Remove confusing words --------- Signed-off-by: Šimon Brandner <[email protected]> Co-authored-by: Tulir Asokan <[email protected]> Co-authored-by: David Baker <[email protected]> Co-authored-by: Andrew Morgan <[email protected]> Co-authored-by: Richard van der Hoff <[email protected]>
Spec PR: matrix-org/matrix-spec#1602 |
Spec PR: matrix-org/matrix-spec#1735 |
Merged 🎉 |
Fixes https://github.com/matrix-org/matrix-doc/issues/560
Requires #2746
Rendered
js-sdk
implementationreact-sdk
implementationMy first MSC, please try not to kill me 😅
FCP tickyboxes