Closed AstroAlan closed 1 day ago
indi-allsky balances the exposure by measuring the average brightness of the central 50% of the image. Pixels outside the central region are not used for brightness calculations. When you have those extremely bright clouds, they do not affect the exposure until they approach the central region of the image.
On the Image tab, you can see the default setting of 50% for ADU FoV
. You can expand this range to 66% or 100%.
A better option would be to use a detection mask, where you can draw arbitrary boundaries for the brightness calculations (and other functions). https://github.com/aaronwmorris/indi-allsky/wiki/Detection-Masks
Hello, Thanks for your reply. Just an update. I've tried altering the ADU FoV and I'm still getting the effect. Probably worse. I've looked at the mask but I keep getting a line on the images which I don't want. I'm going to try re-installing the software. I've been altering the settings to try and find a cure and may have changed some detrimentaly. ATB Alan
Do you have an example image with the line?
Weird thing happening here. When I view the timelapse via the local network I get the artifacts, both on my Samsung S24 or my HP laptop. When I load the video to Dropbox and view it from there the video is perfect. No flaws or clipping at all. How can that be? Don't understand that at all. Thanks Alan
That makes more sense. I just viewed the video on dropbox and I did not see the problem. I just assumed the problem was the bright areas.
Try adding -level 3.1
to the extra ffmpeg options and restart indi-allsky. Other users have reported this fixes the artifacts in the videos. This is actually now a default in indi-allsky, but you installed before it became a default option.
Hello, That's cured it. I've done 2 nights timelapse and it's perfect. Many thanks for your help. It's very appreciated. It's a superb price of software. Well done.
ATB Alan
Hello, I'm hoping someone can help please. Firstly well done to AM for a great (and free) piece of software. Had no real issues once I increased the memory swap size to 5gb. But I've been trying to sort an issue out for about a month now. I'm a novice with the raspberry pi so I'm now just guessing at the cause. When a timelapse has been created there's an artifact on the video that appears to be clipping the brightness of the video making it appear blocky and pixelated in patches. This dances around the screen as the video progresses.. Non of these artifacts are present on the individual frames taken throughout the night, so I believe it's a time lapse processing error/setting fault. Camera is a ZWO 676MC. Here's a Dropbox link to the time lapse video (340mb so exceeds the 10mb allowed to post here) and below the support info.
https://www.dropbox.com/scl/fi/xzemmgw6cisk6hcpcz0km/allsky-timelapse_ccd1_20240901_night-2.mp4?rlkey=v4ezhx1e9eqni1npkp3jsdhm3&st=q81ho60s&dl=0
Support info (Sorry it's so long!!!)
/home/alans/indi-allsky/misc/support_info.sh: line 62: warning: command substitution: ignored null byte in input #################################
indi-allsky support info
#################################
indi-allsky config (passwords redacted) 2024-09-02 07:00:30,722 [INFO] MainProcess config._dump() [1024]: Dumping config
#################################
end support info
#################################