New install (v0.8.3) - RPiHQ camera - images very flat #967
Comments
|
@jcauthen78 You are using "Saturation: 60.0" but for bullseye there is a limit (0...2) - please change it to 1.0 brightness - a little bit the same - please use 0.0
|
|
we will normalize the values in the future, so that there is no dependency on cameras and capture programs |
|
about removeBadImage: maybe this can help: https://unix.stackexchange.com/questions/623672/i-keep-receiving-command-not-found-when-i-try-to-run-my-code-in-bash at the prompt in putty, type |
|
BOOM! you were 100% correct - taking them down to the new lower ranges worked beautifully, both Brightness & Saturation needed changed up to get the image happy. I ran the I'll dig through StackExchange a little more and see what I can find out, see if maybe it's a PiZero specific or a BullsEye thing. I can close this out as resolved for the Flat image issue unless ya want some resolution to the bash failing thing
|
What is 'bc' ? maybe I can do a manual install of whatever it is? Line 126 : |
|
@jcauthen78 Long time no talk. How you're doing well. In 0.8.3 removeBadImages.sh is called on every image because it only takes a couple seconds and catches corrupted images (not common) and too bright or too dark images (common if using fixed exposure times around day/night transitions). @linuxkidd - Someone else had this issue on Bullseye where @AndreasLMeg FYI |
|
Strange... Appears it was added by PR #902 2 weeks back. :) Be sure you're up to date on the latest code and run |
|
For giggles, did a Dist Upgrade & Firmware on the Zero W2, renamed the original allsky folder, re-git & install, reinstall of Gui too. BC is recognized. It looks like I did the first install a little more than 2'ish weeks ago, so missed that #902 PR. This quick fix, and the previous Brightness & Saturation fix - y'all got me fixed up. Thank you. Next on my list is the swap file, as well as the virtual temp folder to reduce card writes. @EricClaeys good to see ya still cranking hard on the updates, keep up the hard work. Any luck with the day/night transition, or did yall have to scrap the idea? |
|
@jcauthen78 Great to hear it's all fixed up for ya! If you run into issues with the swap setup, etc.. please don't hesitate to reach out via a new issue. I'll close this one since it's all wrapped up. Clear skies! o/ |
|
@jcauthen78 Jim, I improved what I could with the transition but there is only so much that's possible as long as we don't use our algorithm at night. |
Started off with a fresh install, on a Raspberry Pi Zero 2W & RPiHQ Camera, trying a slimmed down setup to take camping with me. I've gone through the settings that logically go together, but I'm feeling I missed a step. Didn't see anything in the previous issues The images are coming out very flat in both Day & Night captures. It's not weather-ready, so I can't put it outside just yet for full testing. Any thoughts or suggestions to fix the Flat images? Below is the info from my system and a tail of the allsky.log with the settings and output, and an example of the flat image as well. I can provide whatever other data/logs, just wasn't sure what all to include.
Y'all have done a great job with the updates & upgrades, keep doin what you do!
I'm also noticing the Remove Bad Images is running every capture, but its failing?
Pi Zero 2W running BullsEye
Raspberry Pi HQ Camera
64gb Card.
GUI is installed, page file @ default (soon to be increased to avoid timelapse kill). Also will alias the allsky/temp folder to reduce SD writes (when i can find the instructions again)
tail-f /var/log/allsky.log with Debug @ 4.
The text was updated successfully, but these errors were encountered: