star trail problem

[Aripaule]

Hello, I have a problem with my star trail.

I tried to make some changes, such as lowering the threshold value from 1 to 0.5, but I was unsuccessful.

Time lapse and keograms work perfectly.

These images are the ones that appear in the startrails tab. It looks like they're not being stacked or something.

Any suggestion?

[ericofpendom]

Hi, I followed the Troubleshooting section on this page...https://htmlpreview.github.io/?https://raw.githubusercontent.com/AllskyTeam/allsky/master/html/documentation/explanations/startrails.html
and it worked for me. I tried settings from 0.3 to 0.7 and they all came out slightly different.
Just follow exactly and you should get some results.

[EricClaeys]

@ericofpendom, thanks. I think everyone who's followed the tips on that page got startrails working.

[Jasonshobbie]

Did you make your adjustments inside the WebUI? I haven't been able to see any startrails but am not receiving any error messages that I see. I'm sort of mixed up on the answer in the trouble shooting. These are changes made in the WebUI or with the command prompt? Just confused.

[EricClaeys]

@Jasonshobbie,
The BRIGHTNESS_THRESHOLD setting is in the config.sh file, which you edit via the WebUI's "Editor" page.

[EricClaeys]

You change it, then recreate a startrails via the generateForDay.sh command that you run on the command line.

[Jasonshobbie]

Thank you. I think that I understand it now. I did change to .3 yesterday but still nothing was generated. The night before, my timelapse failed but I believe that was because the Northern Lights appeared at two separate times. But then last night, no timelapse again. Sounds like I need to make some adjustments there as well.

[EricClaeys]

@Jasonshobbie, the BRIGHTNESS_THRESHOLD has nothing to do with timelapse videos. They should include ALL saved images for the prior 24 hours.
See the Troubleshooting -> Timelapse documentation page for instructions on determining why timelapse aren't being created, and how to fix it.

[Jasonshobbie]

Later today I realized that I had both a time lapse and startrails from last night. I'll have to figure out when those will be generated but it sounds like it's an afternoon thing.

I believe that I figured out the issue. I had the camera taking a photo every 10 seconds and I think that it just wasn't able to handle it. It's a p4 8gb with a 256 gaming sd card, but that was a lot of pics. I think I may try to create a timelapse with the images, but I was able to grab some nice pics anyways.

The lights should be out again tonight and I set it to take an image every 40 seconds. Hopefully that turns out good.

Cheers

[EricClaeys]

Timelapse, startrails, and keograms are created at the end of nighttime which is defined by your Angle setting.

What do you mean by "just wasn't able to handle it"? Did something fail?

[Jasonshobbie]

I believe that the timelapse wasn't generated on that day because I had too many images that the Pi was trying to process. I had it taking the pics every 10 seconds. This is just my speculation as I haven't ran any codes. I was thinking of doing the workaround to generate the timelapse though. Since I've changed to every 46 seconds and adjusted for the startrails, all is well and is working perfectly.

[EricClaeys]

@Jasonshobbie, I'm not sure if "too many" images would keep a timelapse from being created, or it would simply take a lot longer.
Would you please run generateForDay.sh --timelapse --debug DATE, replacing DATE with the date when a timelapse wasn't created.
It should fail bug will hopefully provide an error message.
Thanks - Eric