-
Notifications
You must be signed in to change notification settings - Fork 326
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
ERROR: unable to open RTSP for listening / Cannot assign requested address #1143
Comments
FFmpeg 4 not supported |
Sorry - what does that mean - any suggestion for a work around ? |
Update ffmpeg version |
OK - switched to docker and had success with Chrome, while FF (125.0.3) now - with MSE is OK - but with WEBRTC complains:
|
Trying to use a RTSP (h.265) camera (Steinel L620) stream in browser with go2rtc-1.9.2 I only get errors on address.
The errors only appear when using a URL of type "ffmpeg:rtsp://MYIP:554/MYPATH" -- whereas "rtsp://MYIP:554/MYPATH" doesn't give errors - but Chrome&FF browser do not support h.265 with WebRTC an therefor I need to use ffmpeg for transcoding to h.264.
with go2rtc.yaml:
running go2rtc and and just using web-ui/"probe" or access "stream" URL results in:
Interesting other information:
FFPLAY works OK as ..
Any hints what I could be doing wrong here or how I can further debug this.
The text was updated successfully, but these errors were encountered: