-
Notifications
You must be signed in to change notification settings - Fork 8
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
Help needed: Snapshot address #54
Comments
Hey @Morcegolas, Thank you for reaching out. To capture an image, you can give this URL a try: I'm not very familiar with OctoPrint, so I'm not sure what Octolapse expects for the snapshot. |
If I use that it just starts taking snapshots and instead of getting the snapshot image I get an message "ok", I need the link for the current snapshot to use in octolapse. Thanks. |
Ok, i'll see what i can do. |
Hi @Morcegolas, I wanted to let you know that I've added two new API commands in the latest release of the application. https://github.com/Lillifee/raspiCam/releases/tag/v2.0.7 Here are the details of the new commands:
I would greatly appreciate it if you could try out both commands and provide me with feedback on whether they are functioning as expected. Thank you very much! |
Thanks for helping out. I'm getting this error in octolapse when using /api/stream/mjpeg/snapshot and also /api/capture. This is the help page: The default value is {camera_address}?action=snapshot, which works well for mjpg_streamer (bundled with octopi). If you are using Yawcam you probably want to use {camera_address}out.jpg The default full url after replacing the {camera_address} token with the default 'Base Address' above would be would be http://127.0.0.1:8080/?action=snapshot for mjpg_streamer and http://127.0.0.1:8888/out.jpg for Yawcam. If the 'Test' button does not work, you can also enter a full snapshot url here. If the URL works in a browser window and returns a JPEG image, it will likely work in Octolapse.` |
This is the log:
|
Hey, thanks for the fast response. Did the api request work in your browser? This sounds it should work if it's returning a jpeg But sounds i have to install octoprint and try a little bit around. |
The api request worked in the browser, the both of them, but none in octolapse :/ |
Hey @Morcegolas, I've installed OctoPrint with Octolapse, but I don't have a printer connected yet to conduct a complete test. You need to provide either the full URL or use the arguments as follows: Base address: http://192.168.3.58:8000/ During my tests, the MJPEG snapshot always worked, but the api/capture only worked when I reduced the timeout and image resolution. It seems that Octolapse doesn't wait as long for the image. Maybe it's only during test webcam and we could increase the timeout during a real print. Settings worked for me with the api/capture: Base address: http://192.168.3.58:8000/ Raspicam photo settings |
Thanks, it's strange it started working, maybe needed a reboot I don't know. Since I'm using raspiCam I never got this to work, until yesterday that I open here a question, many thanks. I'm also having a problem of having to reboot a lot my raspiCam, since the beginning, and it's powering it off/on because it becomes very unresponsive. I suspect that as I use it with multiple devices/apps (octoprint web, iOS app) and I have two routers with the same Wi-Fi names, as is always jumping between them maybe it overloads the raspberry I don't know. Anyway, this problem is solved. |
Hey @Morcegolas i had a similar problem yesterday where i had to reboot. Maybe i broke something in the mjpeg streaming in one of the latest releases. I will review them and test a little bit more. If you find a way to easy reproduce, let me know. Thanks |
Hey @Morcegolas, I believe I've identified a possible reason for the unresponsiveness of the raspicam. In one of the recent updates, I made enhancements to the h264 streaming. However, as a consequence, the mjpeg streams are not being closed correctly. This could be the cause of multiple devices running simultaneously, resulting in numerous lingering mjpeg streams in the background. I have addressed this issue in version 2.0.8, which can be found at https://github.com/Lillifee/raspiCam/releases/tag/v2.0.8. |
Thanks a lot, yesterday I made two big prints, the first one had 5 failed of 35 photos, the second print it didn't take any photo. I will update to this version and give you some feedback tomorrow. |
I couldn't install because when I run wget it gave me an error, but I build it from source and it's running the latest build now, I'll do some tests and let you know. |
Uh i forgot to add the compiled verison to the release. |
I thought the problem was on my side, so instead of complaining I compiled it and updated. Thanks one more time for being so helpful. |
I'm uncertain if the full capture has been improved. The capture process in libcamera-still takes a considerable amount of time, and if it exceeds a certain duration, octolapse fails. I'm unsure if this behavior persists during printing. Perhaps we could initiate a test print with a timeout of 100ms and low resolution. Then we can gradually increase the values during the print to identify the limits and determine if the behavior remains consistent. The latest release primarily focuses on enhancing the stability and performance of the mjpeg streamer. Unfortunately, the capture process still requires the same amount of time. If you have the time, it would be great if you could share your setup and how you utilize raspicam. While uploading videos of such lengthy timelapse prints might not be feasible, some photos would be greatly appreciated. #28 |
Thanks.
The text was updated successfully, but these errors were encountered: