Running remove bad images upon capture? #894
Replies: 5 comments 2 replies
-
@maphilli14 I just merged the code 10 seconds ago. Quite a few files have changed so you're probably best off doing a complete re-install of allsky. I've been using the code for several weeks and the per-image removeBadImages.sh works well - in fact, it found a few images last night. |
Beta Was this translation helpful? Give feedback.
-
I tried it and it didn't work for me, the images got suck in the tmp directory. I did notice that SHUTTING my custom animation script that runs in the background resulted in no bad images this am! The idea is to take a few photos and ffmpeg them into a gif so I can see the past few minutes of clouds moving! It's more intense than I thought?!
|
Beta Was this translation helpful? Give feedback.
-
Keeps a sorted list of the X (25 in my case) images and pops the oldest one out. Makes a GIF every X seconds and takes new photos every Y seconds.... Here's and older example - https://f002.backblazeb2.com/file/allsky/anim.html |
Beta Was this translation helpful? Give feedback.
-
Really just taking the existing live image that is already saved and issue a python copy and use the current timesamp to sort the image into an time ordered list... |
Beta Was this translation helpful? Give feedback.
-
@maphilli14 Are you using the latest saveImage.sh? It fixed the issue with images getting stuck in allsky/tmp. |
Beta Was this translation helpful? Give feedback.
-
My current workflow is working well. I am able to gen a keogram at end of night. For startrails and timelapse I yank the files in the morning to a Win10 and process via allsky running in WSL. This copy, removebadimages, then end of night is a bit more time consuming than I'd like, has the feature to remove bad images upon capture been implemented yet?
Beta Was this translation helpful? Give feedback.
All reactions