SharpCap Forums

Hi, a bit harder than it might sound, since the internal format for the 'processed' light heading into the live stack is not the same as the normal processed light being saved. There is also the fact that the processing is irreversible, so if someone ended up with that option left on unintentionally...

Hi, let me investigate that - I thought that it should ignore the setting if the box is unticked, and I can see the code that looks like it will do that. I can also see the code that should do a single stage move not a two stage move if the backlash values are both set to zero, so something odd is g...

Hi Don, if you send me a screenshot or a saved frame then I can check if anything is going wrong. Auto adjust also records info in the log about what choices it has made and why. However, if you have bad vignetting or dust spots then you can end up in a situation where the brightest parts of the ima...

Hi, ah, the angles being opposite does indicate that the mount is moving in opposite directions (roughly), but not 'opposite enough' for the calibration code... Ideally the angles would be 180 degrees apart (say -90 and +90, or -80 and +100). If you look at the 'Scatter' graph tab, you will see that...

Hi, ah, OK. No, the memory limit changes are unlikely to affect the display update rate - if you are just watching the image on screen, SharpCap can work with about 3 or 4 frames worth of memory. Having more memory available is really only used significantly when capturing. If you turn on the option...

Hi,

OK, will try for 1/16 of similar.

cheers,

Robin

Hi Jim, how were you capturing? In a small number of places where you capture without having a setting to actively choose the output format, SharpCap may default to the 'Preferred still format' from the settings. I'm trying to catch and fix these as I find them. There are also a few places where sav...

Hi, OK, so if the FPS indicator at the bottom left is staying at about 40fps then the camera is still working as it should sending frames to SharpCap, so it sounds like SharpCap is being bogged down and ending up lagging on the frame display. What could be happening is that SharpCap has a display fr...

Hi, yes, that looks like the right log - I can see the use of live stacking and the individual captures happening in it. Unfortauntely the live stack doesn't record a great deal in the main log unless something goes badly wrong, so the main log will not reveal much here. One more thing did occur to ...

Hi, thanks for the additional logs - I have the problem worked out now - the line of code to start the focuser moving in response to the sequencer was duplicated, so it starts the focuser off moving to position 5000, then requests it again. The focuser fails the second request because it is already ...