Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Don't use event.SFUTrackDescription internally for track identification #56

Closed
SimonBrandner opened this issue Dec 5, 2022 · 0 comments · Fixed by #59
Closed

Don't use event.SFUTrackDescription internally for track identification #56

SimonBrandner opened this issue Dec 5, 2022 · 0 comments · Fixed by #59
Assignees
@daniel-abramov
Labels
T-Task

Comments

@SimonBrandner
Copy link
Contributor

See #52 (comment)
@SimonBrandner SimonBrandner mentioned this issue Dec 5, 2022
Merged
daniel-abramov added a commit that referenced this issue Dec 5, 2022
@daniel-abramov
conference: use TrackID as identifier for tracks
ec5841b 
Theoretically we don't need to use a combination of TrackID and StreamID
to uniquely identify tracks inside as long as the GUIDs are used for the
tracks.

Closes #56.
@SimonBrandner SimonBrandner mentioned this issue Dec 6, 2022
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@daniel-abramov daniel-abramov

Labels
T-Task
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

More elegant handling of the RTCPs matrix-org/waterfall
2 participants
@daniel-abramov @SimonBrandner