Timelapse are always 16 seconds long.

[MLethbridge76]

I recently reset my allsky install as somehow my first one become corrupted. The first one was working perfectly.
I also upgraded my camera to the ASI676, but now, the timelapse is always 16 seconds long, no matter what settings I change.
I used to have the exposure length set to Auto, but in an effort to have a longer timelapse, I changed the exposure to manual, set it to 10 seconds with a 1 second delay between each exposure. This should make the video a few minutes, but it always stays at 16 seconds.
Also, not sure if this is related, but the star trails always returns just a single image with no star trails created.

Any help would be appreciated. Please note, I'm not overly skilled with linux, everything was done by following tutorials.

[EricClaeys]

Did you upgrade to v2024.12.06? If not, I suggest doing so. It may not fix the problem but will make troubleshooting easier.

The length of a timelapse is simply the number of images (regardless of their exposure length) times the FPS (Frames Per Second) you set. You can change the number of images by adjusting the Delay.
You can also get a longer video by decreasing the FPS, but if it's too low the image will be jerky.

The Troubleshooting -> Timelapse documentation page has a section for timelapse that are too short. Please check it out. We need to know how many frames are in the video as well as how many images there are. Run a manual creation to check for error messages:

generateForDay.sh  --timelapse 20241221

The startrails issue is totally unrelated. There is a documentation page describing how to adjust the setting for it.

[MLethbridge76]

Hi Eric,
Thanks for the response, I am on v2024.12.06, I upgraded to that about a week ago.
I've been looking into the documentation you pointed me to, and it is definitely helping. I've dropped the FPS to 15 and that has made a difference, and the resulting video is still pretty smooth for my eyes.
I am testing a few of the nighttime exposure settings, and one of them is a bit confusing, as it seems to be 2 things at once... Max Auto-Exposure: "The maximum exposure in milliseconds when using Auto-Exposure. When Auto-Exposure is on, this value will be used as the delay between frames. Ignored if Auto-Exposure is off."

So if I am reading this correctly, does this mean if I have AutoExposure on, and this setting at 1000 ms, the AutoExposure will only be 1 second, and then the next pic will start 1 second later?
If I set it to 60000 the AutoExposure will be 1 minute and then there will be a delay of 1 minute between finishing that pic and taking the next one?

What if I want AutoExposure on and a delay of 1 second?

Perhaps I am just misunderstanding.

[EricClaeys]

@MLethbridge76, I'm glad you're making progress, and that you read the documentation!

I created Issue #4110 to fix the documentation. You are not misunderstanding since the documentation isn't clear. I will explain in the Issue. Please use it for any further comments on "Max Auto-Exposure".
Continue to use this Discussion for your original timelapse problem.
Thanks for finding the documentation bug.

[MLethbridge76]

Thanks so much for all your help with this Eric! Truly appreciated!