-
Notifications
You must be signed in to change notification settings - Fork 468
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
RTSP sdp parsing exception #1472
Comments
Apologies for the delay. Actually, the SessionDescriptionParser is not choking on the I am working on submitting some code that will ignore your custom TP-Link track. I will update this bug when it has been submitted so you can test. |
Some RTSP servers may provide media descriptions for custom streams that are not supported. ExoPlayer should skip the invalid media description and continues parsing the following media descriptions. To start, ExoPlayer will still error on malformed SDP lines for media descriptions, but will now skip media descriptions with "non-parsable" formats as described by [RFC 8866 Section 5.14](https://datatracker.ietf.org/doc/html/rfc8866#section-5.14). Issue: #1472 PiperOrigin-RevId: 660826116
Thanks for your submission! After testing, it works fine. |
Some RTSP servers may provide media descriptions for custom streams that are not supported. ExoPlayer should skip the invalid media description and continues parsing the following media descriptions. To start, ExoPlayer will still error on malformed SDP lines for media descriptions, but will now skip media descriptions with "non-parsable" formats as described by [RFC 8866 Section 5.14](https://datatracker.ietf.org/doc/html/rfc8866#section-5.14). Issue: #1472 PiperOrigin-RevId: 660826116 (cherry picked from commit 8b33ad5)
Version
Media3 1.3.1
More version details
The TP-LINK network camera, when using rtsp connection, there is an exception in parsing sdp. Through breakpoint tracking, the complete sdp data is as follows:
An error occurred when parsing the following media description, which does not comply with the rules of RFC 8866 Section 5.14:
FFmpeg
ignored this part when parsing because the media typeapplication/TP-LINK
is not one of the media types allowed byFFmpeg
:video
,audio
,application
,text
SessionDescriptionParser did not ignore the above situation when parsing
Devices that reproduce the issue
All devices
Devices that do not reproduce the issue
None
Reproducible in the demo app?
Not tested
Reproduction steps
Expected result
Media playback successful
Actual result
Media
Not applicable
Bug Report
adb bugreport
to android-media-github@google.com after filing this issue.The text was updated successfully, but these errors were encountered: