-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
feat(RTC): add support for creating non-standard tracks #2409
feat(RTC): add support for creating non-standard tracks #2409
Conversation
Hi, thanks for your contribution! |
Yes! I have needed this myself too and was on my list of things, Good to see! |
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.
LGTM with a question. Excellent work!
import { MediaType } from './service/RTC/MediaType'; | ||
import { JitsiTrackErrors } from './JitsiTrackErrors'; | ||
|
||
describe('JitsiMeetJS', () => { |
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.
Thanks for this! ❤️
@@ -90,6 +91,13 @@ interface IJitsiMeetJSOptions { | |||
} | |||
} | |||
|
|||
interface ICreateLocalTrackFromMediaStreamOptions { | |||
stream: MediaStream, | |||
sourceType: string, |
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.
What is this used for, other than documentation?
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.
Purely documentation and typings for the function
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.
Or if you mean the sourceType, then it seems to be a way for client apps to determine the type of stream, e.g.
sourceType: 'proxy', |
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.
Gotcha. We are planning to phase that one out, so I can take of it when the day comes. Thanks for checking!
@DanielMcAssey Thanks for the PR. I will update the handbook. |
* feat(RTC): add support for creating non-standard tracks * fix(RTC): add additional checks for creating tracks via mediastream * fix(RTC): simplify options to create track * fix(RTC): fix tests * fix(RTC): update sourceId documentation
* feat(RTC): add support for creating non-standard tracks * fix(RTC): add additional checks for creating tracks via mediastream * fix(RTC): simplify options to create track * fix(RTC): fix tests * fix(RTC): update sourceId documentation
* feat(RTC): add support for creating non-standard tracks * fix(RTC): add additional checks for creating tracks via mediastream * fix(RTC): simplify options to create track * fix(RTC): fix tests * fix(RTC): update sourceId documentation
* feat(RTC): add support for creating non-standard tracks * fix(RTC): add additional checks for creating tracks via mediastream * fix(RTC): simplify options to create track * fix(RTC): fix tests * fix(RTC): update sourceId documentation
* feat(RTC): add support for creating non-standard tracks * fix(RTC): add additional checks for creating tracks via mediastream * fix(RTC): simplify options to create track * fix(RTC): fix tests * fix(RTC): update sourceId documentation
* feat(RTC): add support for creating non-standard tracks * fix(RTC): add additional checks for creating tracks via mediastream * fix(RTC): simplify options to create track * fix(RTC): fix tests * fix(RTC): update sourceId documentation
* feat(RTC): add support for creating non-standard tracks * fix(RTC): add additional checks for creating tracks via mediastream * fix(RTC): simplify options to create track * fix(RTC): fix tests * fix(RTC): update sourceId documentation
We have this manually patched into our copy of lib-jitsi-meet, but thought it might be worth sharing.
This change allows applications that use lib-jitsi-meet to manually create JitiLocalTracks from some track metadata and mediastream, similar to what the library does internally, but exposing it.
We use it to create a track for our Canvas, that we then add to the conference, similar to below:
This would possibly fix #1593