-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
[BUG] FFMPEG bug causes Obico not to respect RFC2396 for stream URLs causing compatible mode to run at 0.1 fps #174
Comments
Good catch. Feel free to send a PR for it. |
I'm not really a Python programmer, but I think this should work (feel free to correct my crude "style")
|
Alternatively, you could more broadly (and cleanly) add the patch to the definition of webcam_full_url in webcam_capture.py
|
Any reason this patch (or similar) has not been included in latest updates? |
It'll be a lot easier for me if you can submit a PR so that we can discuss the specific code. |
In Octoprint settings, under "Webcam & Timelapse", if you set stream url to:
http://myrpi:8080/?action=stream
which is a valid RFC2396 URL, then ffmpeg will fail to recognize the URL and returns:http://myrpi:8080?action=stream: Server returned 400 Bad Request
This is actually an ffmpeg bug
See the bug report: https://trac.ffmpeg.org/ticket/8466
Obico doesn't detect this bug and merrily launches ffmpeg with the faulty URL.
This causes ffmpeg fails (silently) and then Obico defaults to 0.1fps snapshots.
Suggested fix is either:
Of course, until ffmpeg or Obico code is adjusted, users can avoid the problem by making sure there is a "/" before the '?'.
i.e., change
http://myrpi:8080?action=stream to http://myrpi:8080/?action=stream
The text was updated successfully, but these errors were encountered: