×

INDI Library v2.0.6 is Released (02 Feb 2024)

Bi-monthly release with minor bug fixes and improvements

scheduler; frame captures not updated

  • Posts: 969
  • Thank you received: 94
Hi everyone
Tonight's build: The number of captures remains at zero:

Have I missed a setting in the capture module perhaps?
TIA and clear skies,
Steve
Log:: www.indilib.org/media/kunena/attachments/4679/log_23-48-25.txt
Last edit: 5 years 7 months ago by alacant.
5 years 7 months ago #28331
Attachments:

Please Log in or Create an account to join the conversation.

We're aware of these issues and Eric (aka TallFullyMan) is working on a solution for KStars 2.9.8
The following user(s) said Thank You: alacant
5 years 7 months ago #28356

Please Log in or Create an account to join the conversation.

  • Posts: 1029
  • Thank you received: 301
Yes, until the capture module is fixed entirely, I'll make no attempt at fixing this one. The image update goes to the first tab, but is not reflected in the scheduler tab. And it's not as straightforward as it may seem.

In the past I would have called the issue cosmetic because the scheduler wasn't supposed to offer much feedback and it was only a job edition tool :) Now I'm not really looking at the first tab anymore...

-Eric
5 years 7 months ago #28393

Please Log in or Create an account to join the conversation.

  • Posts: 969
  • Thank you received: 94
JTOL: The number of frames captured is readily available in 2 other easily consulted places. Just leave it out of the scheduler?
5 years 7 months ago #28394

Please Log in or Create an account to join the conversation.

  • Posts: 1029
  • Thank you received: 301
The number of current and required frames has to be considered by the Scheduler in order to estimate each job duration in the schedule. Thus it has its place in that table for clarity on calculations. It's important for the end-user to have a clear feedback on why things happen.

-Eric
5 years 7 months ago #28395

Please Log in or Create an account to join the conversation.

Time to create page: 0.261 seconds