-
Notifications
You must be signed in to change notification settings - Fork 101
Add frame processor support for audio streams (node version) #583
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
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 793ae90 The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
… expected by plugin implementations
I think this isn't actually all that helpful for an end user. I'll put this somewhere else instead.
| abstract setEnabled(enabled: boolean): void; | ||
|
|
||
| abstract onStreamInfoUpdated(info: FrameProcessorStreamInfo): void; | ||
| abstract onCredentialsUpdated(credentials: FrameProcessorCredentials): void; |
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.
issue: these two have a default implementation in python and aren't treated as abstract. We should make them non-required also for node.
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.
Ah, I see, I think I missed that. Fixed!
Some of these aren't even related to this pull request, so I'm quite confused by they are showing up now, I didn't rebase this or something like that...
This is a copy of livekit/python-sdks#533, adapted for node.
I'm letting @lukasIO take the lead on this, and will adjust this once the python version gets merged to match the same interface.