[React] Implement multi-participant handling & state #148
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.
This PR implements handling for multi-participant sessions. The local participant and bot are still referenced via
"local"
and"bot"
. Remote participants are returned through theusePipecatClientParticipantIds
hook (can include "local" and "bot", too). We keep track of the bot's participant id to correctly distinguish between bot and remote participant tracks.I have already outlined the changes in the changelog:
Added
usePipecatClientParticipant()
hook to access individual participant datausePipecatClientParticipantIds()
hook to get all participant IDs with filtering optionsChanged
PipecatClientVideo
component now requiresparticipantId
prop whenparticipant
is set to"remote"
PipecatClientAudio
component now renders audio for all participants automaticallyPipecatClientVideo
component now supports remote participantsusePipecatClientMediaTrack()
hook signature updated to support remote participants