-
Notifications
You must be signed in to change notification settings - Fork 79
Some pointers about DASH (MPD) streaming #1045
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
Comments
Many thanks for the info. I actually figured out the The problem I have now is getting this information into the stream component. I can modify the component to accept a |
And I just saw your comment about the android user agent - it still returns an RTSP stream. Sorry I missed that, there was a lot of activity the last few days and it got buried in the deluge of people telling me they had the same issue... I'll add that user agent to |
Np, thanks for your awesome work keeping on top of Arlo's server side changes! |
Something else possibly worth looking into is replacing cloudscraper with curl_cffi, which in my experience does a pretty good job at bypassing cf for the login and works with sseclient. |
Thanks. I'll take a look. I've realised I need to refactor the auth code so I'll take a look at this as well. |
Hi @twrecked, I saw in the 0.8.1.13 release notes that you're looking into getting MPEG-DASH streams working. We have it working inside Scrypted, using ffmpeg as the client. Here are a few findings from our previous investigation:
-headers
flag to pass headers, e.g. https://github.com/scryptedapp/arlo/blob/main/src/arlo_plugin/camera.py#L743-L749From personal experience, the DASH stream is not very stable compared to RTSP, and in Scrypted's persistent streaming mode, sometimes fails to load the stream even when a new URL is requested. My guess is that ffmpeg is missing compression algorithms that the browser may support, but I haven't looked into it. The Scrypted Arlo plugin typically prefers either the RTSP or the WebRTC streams instead.
The text was updated successfully, but these errors were encountered: