The first beta build of SharpCap 2.10 is now available on the Beta Downloads Page. Once again 2.10 is a very big release and there are a lot of new features and an awful lot of bug fixes and improvements.
On the hardware front, the big changes in 2.10 are the addition of support for Point Grey cameras and a revamp of how SharpCap handles Webcam and Frame Grabber input to bring those sources closer to the level of the dedicated astro cameras in terms of the functionality SharpCap can offer.
A big thank you to Astrograph for providing a sample Point Grey camera to work and develop with. Having a sample camera to develop against is pretty much the starting point for getting any new brand of cameras supported in SharpCap – without one it’s almost impossible to get things working in a reasonable amount of time. Currently SharpCap supports FlyCapture based cameras (not Spinnaker Cameras) and it should be fine with GigE, USB and Firewire models. As always, bug reports are welcome with as much detail as possible as it’s likely that different camera models might need a few more tweaks to the code throughout the beta process.
The change to the processing of Webcam/Frame Grabber video is the other major change in SharpCap 2.10. Right from the first versions of SharpCap up until version 2.9, SharpCap has let DirectShow (the Microsoft Video components) take charge of showing webcam images on the screen and saving them to AVI file. As SharpCap has added more and more features for Astro cameras, Webcam users have been a bit left behind, since adding those features for them was either impossible or would have meant writing the code twice – once for Astro cams and once for Webcams. Now in SharpCap 2.10, SharpCap takes full control of displaying and saving the images from Webcams – DirectShow is only used for grabbing the image data in the first place. This means that features that couldn’t previously be supported for webcams are now available – these include
- Dark frame subtraction and flat frame correction
- Saving in SER or FITS format
- Display adjustments of Gamma, Contrast and Brightness that affect the screen only
There is one drawback – if you have a camera that captures in a compressed format (primarily MJPG, possibly I420, YUV, YUY2 etc), then the new approach will lead to bigger capture files as the output files are always saved as RGB (three bytes per pixel). In this age of cheap SSD storage and even cheaper hard disk storage, it’s unlikely that the increase in file size is going to cause a problem, but if it does you can switch back to the old way of doing things in the settings dialog.
SharpCap 2.10 contains new versions of the camera SDKs from the major Astro camera vendors (Altair, QHY, ZWO) which fix bugs, add support for new models and add new features. If you have a new model camera from any of these vendors you may well find that it will work better with SharpCap 2.10 than it does with SharpCap 2.9
SharpCap 2.10 adds direct support for ZWO EFW filter wheels without needing to have ASCOM installed. There is also now an option on each type of supplementary hardware (Focuser, Filter Wheel, Mount) to allow the hardware to be temporarily disconnected then reconnected while the camera is running.
Flat frame correction is a brand new feature in SharpCap 2.10 – it allows flat fields to be captured in the same way that previous versions of SharpCap assisted in capturing dark frames and then the flat field can be applied to correct each image captured, correcting both the image viewed on screen and the data saved to file.
SharpCap uses the special high speed CPU instructions that are usually for games and multimedia to allow flat frame correction to be carried out at very high speed. With a modern high power processor you should be able to apply flat frame correction to the video stream from a USB3 camera (like a ZWO ASI174MC) at full speed.
SharpCap 2.10 adds the ability to create and apply high bit depth (16 bit) dark frames when using 8 bit cameras (or 8 bit modes). This is important when using live stacking with low gain (low noise) as otherwise the repeated use of an 8 bit dark frame negates the improvement in signal that would be expected as the number of stacked frames increases and the SNR of the stack increases.
Thanks to Matt from Astro Video Systems for suggestions that lead to the introduction of this features.
This version of SharpCap adds a filter option for for frame brightness which can be used to reject frames that are dimmer than the average – this should allow detection of incoming or patchy clouds. Additinally there is a new tab showing history graphs of the rotation and offset of each frame in the stack to allow a better understanding of how well the mount is tracking.
Lots of other improvements have been made to live stacking to improve both performance and user experience, including
- Ability to soften the black point of the histogram stretch to give better image tones around the black point
- More options to tweak the parameters used for star detection
- Improvements to file naming so that the total stack duration is included in the file name
Finally, SharpCap no longer re-detects stars in the stack so far every time a new frame is added, meaning that the time taken to stack each frame is approximately halved!
SharpCap 2.10 adds focus assistance if you are using an ASCOM focuser. This appears in the ‘Graph’ tab of any of the focus measurements if you have a focuser connected. Rather than having to adjust the focuser through several positions one at a time to find the best position you can use the ‘Scan Out’ and ‘Scan In’ buttons to perform a series of measurements of the focus score. Once a scan has been performed and has a maximum (or minimum) score in it, you can use the ‘Goto Best Positon’ or ‘Goto Best Score’ buttons to put the focuser back to either the position where the best score was measured or to seek the best score value.
The ‘Goto Best’ buttons both take the focuser back to the beginninng of the scan so that the best score is approached in the same direction to avoid backlash problems.
You can use the ‘Options’ button to adjust the size and number of steps used when scanning.
SharpCap now supports plate solving using AstroTortilla if you already have it installed on your computer. You’ll need to have AstroTortilla itself installed (including the Star Index files).
You can kick off plate solving using the locate button (GPS Symbol) in the mount control (you have to have selected an ASCOM mount to access the plate solving). When you press the locate button, the current frame will be plate solved with AstroTortilla, the mount will be synced to the solution and then will perform a re-GOTO to the position it was originally supposed to be pointing to.
SharpCap scripting is improved by the inclusion of a full python standard library so that it’s no longer necessary to use the .NET API for basic tasks like file I/O in scripting. It’s now possible to run an RPC server like Pyro inside SharpCap to allow SharpCap to be controlled by other applications. Unfortunately due to limitations in Pyro it’s not possible to directly exposre the SharpCap object model, but it’s possible to write Python objects to wrap the SharpCap object model and expose those objects.
Finally, SharpCap 2.10 adds the – long requested – ability to manage capture profiles, which includes the ability to delete unwanted profiles and to set/clear the default profile for each camera.
Beta builds can be downloaded here.