Page 1 of 1

Bin2 image size

Posted: Sun Aug 20, 2023 3:54 pm
by Higany
Hello,

I am using SC also to create flat and dark frames (because I think the averaging function is very handy), which I can universally use during post processing, even for light taken with another software.
I am using a ZWO ASI178MM camera in bin2 mode, and with SC4 between two versions (I don't know which, I noticed it in May) the bin2 image size changed from 1544x1040 px to 1548x1010px. Any other program, like APT also creates 1544x1040px size images in bin2 mode. With this change, I can't use SC4 calibration frames anymore with images taken with another software. My workaround is to use an old SC3 instance on the computer. The bin1 image size in all versions and software is 3096*2080 (yes, it's half is 1548*1040). When I try to set up a ROI, I can select 1548*1040 as a target, but it says, the closest valid is 1544*1080. But then why it saves the frames in 1548*1040? I can't set the target to 1544*1040px.
Is it a bug or a feature?
Is it possible to get the desired frame size somehow?

Thank you,

PS: The log is created with a version 4.0.9538.0 but it's the same in the latest 4.0.9562.0 too.

Re: Bin2 image size

Posted: Mon Aug 21, 2023 1:08 pm
by admin
Hi,

there are some quite complex rules about what sizes are allowable for ZWO cameras, and SharpCap tries to follow them exactly. In this particular case, the 1548x1080 size is valid for USB3 cameras providing that hardware binning is not turned on. However, turning on the hardware binning option changes the rules somewhat and in that case 1548x1080 is not valid and SharpCap will (I think) go to 1544x1080 as the nearest valid size.

I wonder if the other applications either have hardware binning on by default or are applying the hardware binning rules in all cases?

Anyway, hopefully turning on that option if you have it will give you the size you want.

cheers,

Robin

Re: Bin2 image size

Posted: Sun Sep 03, 2023 6:47 pm
by Higany
Dear Robin,

thank you for the hint. In the 64bit 4.0.9562.0 version it worked!
(In 4.0.9538 it gave me an error.)