-
Notifications
You must be signed in to change notification settings - Fork 312
fix(agents): stop forwarding frame processor info #1883
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
Closed
+5
−20
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| '@livekit/agents': patch | ||
| --- | ||
|
|
||
| Stop forwarding frame processor stream info and LiveKit credentials from room input handling. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
🚩 FrameProcessor no longer receives stream context or credentials after track subscription
The removed code at
agents/src/voice/room_io/_input.ts:155-164(old lines) forwarded participant identity, room name, publication SID, token, and server URL to theFrameProcessorwhenever a new track was subscribed, and refreshed credentials on token refresh. After this PR, theFrameProcessorstill receives audio frames viaAudioStream(agents/src/voice/room_io/_input.ts:159-164), but it no longer has access to the stream metadata or LiveKit credentials. If anyFrameProcessorimplementation (e.g., a cloud-based noise cancellation service) relies on these callbacks to authenticate or route audio, it would silently stop working. The changeset description explicitly states this is intentional, so this is likely coordinated with an update in@livekit/rtc-nodewhereAudioStreamnow handles this internally. Worth confirming with the rtc-node team that the FrameProcessor contract no longer requires these calls.Was this helpful? React with 👍 or 👎 to provide feedback.