-
Notifications
You must be signed in to change notification settings - Fork 0
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
track事件笔记 #1
Comments
潜在的BUG进入房间,A首次单推视频流,对方B拿到视频流。
MDN 说明:
TODO:那么通过 |
获得track/stream时,到底用哪个?用stream:当获得同时具有 用track:与以上相反 pc.addTrack(track, stream)
注意这句话:
|
可参考的项目以下项目都值得深入研究 |
track id的问题有啥解决思路吗?真是惊了,什么腊鸡标准~ track id两端竟然能够不一致,更坑的是,理论上除了这玩意没有任何办法绑定双端的track。那票制定标准的人是以何种脑回路搞出这样的玩意的? |
XPeer/src/index.ts
Line 123 in 0eea244
在通过修改
sdp
来辨别track
的类型时,需要注意以下情况首次协商,推多个track(video/audio)
次多个
track
仅在首次协商发生,此时trackId
双端保持一致。类型匹配:不能单匹配display/user字段,因为同一个sdp中有多个tag被打上。此时需要
类型/ID
来匹配。后期变动产生新的协商,推单个track
后期
track
有任何变化(添加、移除),都是单个track
,且双端trackId
不一致。类型匹配:只匹配display/user字段,不匹配id。
MDN Official notes:
相关:
How to handle removing and re-adding remote streams/tracks - possible ID collisions?
The text was updated successfully, but these errors were encountered: