SharpCap Forums

Hi all,
I wanted to share a project I've been work'n on for a couple of day or two. After coming across SETnC software ( Eclipse photography software, but only works with Canon DSLRs ), I wished for a similar way of sequencing Eclipse images on actual astronomy cameras.

So, I created...

SharpCap Eclipse Sequence Generator

Now With Voice Prompts throughout the Eclipse!!!

A few notes:

• Requires SharpCap Pro version 4.1.11922 or newer!
• The generator is hosted on GitHub, and source code is available at linuxkidd/SharpCap-Eclipse-Sequencer.
• The generator is 100% HTML, CSS and Javascript and runs completely in the browser - no server side execution occurs.
• I generated the Sequencer output based on the documentation, but I could have misread something, or there may be bugs which I've not hit.

Screenshot:


Please feel free to provide any suggestions, problems found, constructive feedback, etc.


Change Log

• Changed the time entry to allow copy/paste, in 24 hour HH:MM:SS format.
• Save and Restore the camera settings after sequence execution.
• Added the 'ARRANGE FILES IN ONE FOLDER' instruction.
• Update the target name throughout the execution:
  PartialPreEclipse, BailysBeadsPreEclipse, FullEclilpse, BailysBeadsPostEclipse, PartialPostEclipse
• I added URL encoding of the parameters so it's a bit easier to come back and re-work your collection plans.
  NOTE: This only remembers / re-populates all the top stuff ( above the collection plans ). Times, Camera parameters, Intervals and output File Format.
• Also, the URL used to generate the sequence, including the hashed parameters is written as a comment at the top of the generated sequence.
• Based on the pre-release version available here, I have updated the generator to use the new `PAD DURATION` instruction.
• Added a 5 frame delay between collection plan steps.
• Added an option to trigger the collection plan iterations at an even percentage of partial phase. More details in this update post.
• Added the additional "Partial Eclipse Count" values as discussed in post #94
• Added additional "Baily's Beads Interval" values.
• Added a 'Tips' section at the top.
• Added ability to set resolution per step in collection plan.
• Changed to 'LATER THAN' vs 'AFTER' for 'LOOP UNTIL' ( per this post )
• Set maximum of 2 seconds delay between 'Collection Plan' steps
• Fixed 'Put on filters' alert timing to be -after- Baily's Beads
• Added C{1..4} tags to the time entry fields.
• Add user specifiable inter-loop delay to Baily's and Totality Collection ( see the header for their respective collection plan )
• Add parameters and pseudo-code to the top of the plan for easier understanding of what to expect during execution.
• Change to using the Browser's "local storage" for tracking all plan and parameter changes - Future loading of the page will restore your previous config so you can easily pick up where you left off.
• Added the PowerShell companion script, originally submitted by Scott Sousa, please see the 'Instructions' tab on the Sequence Generator for how to use it.

Thanks!
linuxkidd

Hi linuxkidd,

great idea - nice that you have taken the time to do this and to share it.

From the SharpCap side, I'm not sure periodics are the way to do this, since they can only run at any point where the sequencer changes from one step to the next (or between frames of still frame steps). That means that I think not much would run in the current arrangement, since the periodics would not be activated during the 'wait until localtime' steps. Of course, you could make those waits a 'LOOP UNTIL AFTER LOCALTIME' step with a 'DELAY 1' inside, which should then allow the periodic to activate. I did check and periodic functions *are* protected against interrupting each other, so that at least is OK.

The simple alternative of a 'LOOP UNTIL AFTER...' with the capture inside and a delay may be easier/more robust. Even then, be careful because timings may change unexpectedly - for instance capturing and saving 100 frames may take longer as the SSD/HD fills up.

If you haven't looked already, it's probably worth checking out this CN thread on the topic of sequencing the eclipse - lots of good discussions and ideas : https://www.cloudynights.com/topic/9099 ... l=sharpcap

From the web UI point of view, it would be great to be able to paste the timings into the Eclipse Times boxes, rather than having to enter the HH, MM and SS separately.

cheers,

Robin

Hi Robin,
Thanks so much for your feedback. In my testing today, I did run into the Periodic event not firing and figured I was missing something. I had hoped the periodic would run in the background on a predictable timing ( trying to keep from using a delay and getting unpredictable results ). I certainly agree that the save timing could also add a level of uncertainty... I may add a warning about that to the UI.

I'll definitely check out the CloudyNights thread... I hope to get things figured out shortly.

Also, great idea re: pasting the time into a field instead of entering manually in hh mm ss format. I'll get that added.

Thanks again!
linuxkidd

Hi Robin,
Would it be possible to add a new 'loop' variant...
This would make precise timing collections much more predictable for the eclipse.

Thanks!
linuxkidd

First, linuxkidd thank you for sharing your generator, WOW WOW WOW WOW thank you!

I can hardly wait for you and Robin to get it smoothed out and ready for action. I will be thanking you again after the eclipse I am sure!!!

Hi,

new sequencer commands aren't usually too hard to add (practically no risk of breaking any existing stuff - I like that kind of change).

Another option would be to add a new block that pads timings if necessary... Naming is possibly the hardest part, but something like
Basically the block would run the sub-steps and then wait at the end up to the specified time (if the sub-steps took less time). That could then be put into any of the existing loops.

Really struggling with the name though!

cheers,

Robin

Maybe the keyword of CONSUME makes sense?
Thanks,
LK

I thought about it a bit and went for
This will most likely be in next week's update, as I am still focused on bug fixes only this week.

cheers,

Robin

Sounds great to me!

Thanks for all your work on SharpCap, Robin!

LK

I've edited the first post to include the change log...

Thanks,
LK