Skip to content

RTSP UDP->TCP failover inconsistency #11069

Closed

Description

@Docteh

Hi, this is related to #9884

ExoPlayer has a feature with RTSP that if a UDP stream isn't received within a few seconds, it'll try again with TCP (Good feature)

If the server tells ExoPlayer that a UDP stream isn't available, and "RTSP/1.0 461 Unsupported Transport", it will NOT try TCP

Where this becomes a problem: If WMPlayer connects to a server with UDP available, and it doesn't receive a stream within a few seconds, it doesn't failover to TCP

I can do a work-around to tell WMPlayer clients that UDP is unavailable as a transport based on the User-Agent, but this does leave ExoPlayer clients waiting a few more seconds for video to start.

  • VRChat
  • AVPro (video widget)
  • Windows Media API or ExoPlayer depending on platform

Is there a reason to not understand the "Unsupported Transport" response? I notice that a LibVLC supports this.

Activity

  1. microkatz commented on Apr 4, 2023

    @microkatz
    Contributor

    @Docteh

    Thank you for reporting your issue! I added functionality to handle the 461 error code in bbd45c8. The fix has been pushed into the dev-v2 branch. Hopefully this fixes your problem!

  2. locked and limited conversation to collaborators on Jun 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions