-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
RTC: Fix video and audio track pt_ is not change in player before publisher. v5.0.207 v6.0.111 #3925
RTC: Fix video and audio track pt_ is not change in player before publisher. v5.0.207 v6.0.111 #3925
Conversation
Thank you for submitting the pull request. Could you describe the scenario in which you encountered this issue that results in playback failure?
|
I play a WebRTC URL on the Unity platform first, and then I publish a WebRTC URL on the Web platform. It can occur that the WebRTC track's payload type (PT) does not match the PT of the player, but rather corresponds to the PT of the publisher. During WebRTC streaming, at the player, the WebRTC system ensures whether the track has the correct player PT for streaming. In particular, since I play the WebRTC stream before publishing, SRS defaults to using the default PT (Chrome 102) at the player. However, the default PT does not match the PT of the player's track |
The PT and SSRC do not actually need to be altered; they can be used as provided by the stream. Perhaps consider modifying the SSRC as well while at it?
|
At this code ( negotiate_play_capability ), if I play a WebRTC stream on Unity platform, pt_of_publisher_ of player track will be from Unity track pt and it's not same with web platform ( publisher ).
And then, becuase pt is not same with publisher pt, this code will not execute. Cause Unity platform to receive incorrect pt. WebRTC will regard pkt as an error and unhandled it at frontend.
|
9c49cb8
to
9bb540a
Compare
The pull request has been merged. Thank you very much for your contribution. Due to some modifications in the code style and the integration of other changes, a force push was necessary. As a result, the commits within this pull request will appear as if they were submitted by me. I hope you don't mind.
|
…lisher. v5.0.207 (#3925) For WebRTC: when player before publisher, it will happen track pt didn't change. - At source change step, change track pt --------- Co-authored-by: mingche.tsai <w41203208.work@gmail.com> Co-authored-by: john <hondaxiao@tencent.com>
For WebRTC:
when player before publisher, it will happen track pt didn't change.
Co-authored-by: john hondaxiao@tencent.com