Closed bendenajones closed 3 months ago
EricClaeys
commented
3 months ago Do you specify the Image Width and Height in the WebUI? If so, set them to 0. If they are both non-zero then the -s option is added to the command line, and any image not that size is rejected.
Also, FYI, the keogram and startrails commands don't like having images of multiple sizes.
EricClaeys
commented
3 months ago Are you aware of the generateForDay.sh script that can be used to manually create a timelapse, keogram, or startrails?
bendenajones
commented
3 months ago Crap! I left those set from the binn testing. Reverted them to 0.
I can just run those scripts w/o inputs? I am aware of the diff image resolution issue (why I use binned for day & night).
bendenajones
commented
3 months ago Ok the generateForDay script is working correctly and thus my reported issue is not an issue. thanks.
EricClaeys
commented
3 months ago Run generateForDay.sh --help for a list of options.
Glad you figured things out.
Pi HQ Camera 4056x3040 resolution; binned is 2028x1520
So I have the PiCapture.cpp "fix" in for binning (see https://github.com/AllskyTeam/allsky/discussions/1685#discussioncomment-9073792) and since enabled binning 2x2 support for both Day and Night Keogram and Startrails fail. Timelapses (mini and full) generate ok.
In the log file:
I see the cmd line to generate the said outputs are specifying the unbinned resolution. Me thinks this is the issue. I am going to try to override the issue by using the "extra parameters" setting for each capability.
I wish there was a way (outside of creating your own cmd via terminal) to trigger the AS keogram/startrails/etc. processes to help test issues. This would help validate in/out paths and other operational capabilities from the AS context. Just a thought...