Capture size doesn't match SDK vs.ASCOM

A place to report problems and bugs in SharpCap
Forum rules


If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs

Please also read about Troubleshooting USB Issues before posting.

*** Please do not post license keys - please report any problems with licensing to 'admin' by private message ***

Please include the following details in any bug report:

* Version of SharpCap
* Camera and other hardware being user
* Operating system version
* Contents of the SharpCap log after the problem has occurred.
[If SharpCap crashes, please send the bug report when prompted instead of including the log]
Post Reply
donboy
Posts: 256
Joined: Sat Mar 25, 2017 1:57 am

Capture size doesn't match SDK vs.ASCOM

#1

Post by donboy »

When trying to use my Darks and Flats taken with the SDK driver when using the ASCOM driver I receive an error stating that the two don't match.

On my ASI2600MC Pro using Bin2 the Darks and Flats both read 3120 x 2080, where the ASCOM reads 3124 x 2088 - So to use the ASCOM driver I would need to take a new set of calibration files. ASILiveStack also rejected the SDK taken calibration files.

Don
User avatar
admin
Site Admin
Posts: 13122
Joined: Sat Feb 11, 2017 3:52 pm
Location: Vale of the White Horse, UK
Contact:

Re: Capture size doesn't match SDK vs.ASCOM

#2

Post by admin »

Hi Don,

there are some rules for the ZWO cameras about what values for width and height are valid, and it may be that SharpCap interprets them slightly differently (perhaps over strictly) when compared to the ASCOM driver. I'm reluctant to change this as part using the ASCOM driver and part using the native driver is a pretty rare thing to do, whereas if I updated the rules for the native driver it would change the size of the camera in 2x2 and break existing flats/darks for those who exclusively use the native driver.

cheers,

Robin
Post Reply