SharpCap Forums

Hi,

there will be a new update later today that I hope will fix the issue related to the order of loading the 'hardware binning' setting. I'm hoping that this will then resolve the problems you are seeing - please let me know if you still encounter problems.

cheers,

Robin

Robin
Thank you for your prompt response with the latest version update.
Unfortunately, I tried using the INI file from 11/23, but got the same results.
Camera control was possible without any problems without using the INI file.
Please let me know if there's anything I can try.
Y.I.

* Version of SharpCap ： SharpCap v4.1.13343.0 (X64, 64 bit)
* Camera and other hardware being user : ZWO ASI6200MM pro , ZWO FEM
* Operating system version　: Windows 11 Pro 24H2
* Contents of the SharpCap log after the problem has occurred. : Log_2025-05-28T12_09_45-4976.log

Hi,

that's a shame - I thought we might have found and fixed this one It's still getting stuck in the same place - that is trying to stop an exposure in progress when closing the camera in order to load the new settings.

Can you try re-creating the profiles from scratch - i.e. without loading one of the existing profiles, set the controls as you want for that profile, then save a new version of it. Then repeat that for the second profile so that you have two brand new profiles created in the latest version of SharpCap. You can then test if switching between those causes the crash, or if the problem is restricted to profiles saved in an older version of SharpCap.

thanks,

Robin

Robin

I tried loading the ini file generated by v4.1.13343.0, but the result was the same.
It's inconvenient that I can't use the ini file, but direct operation in the control panel works without any problems.
So I'll use it like this for a while.
There seems to be a problem loading the ini file, so I'll try various things.

Thank you.

Y.I.

Hi,

Ok, at this point I was hoping that we could try one of the options for verbose logging of control value changes, but I have just checked and there is an issue where the controls we are most interested in (binning, resolution, etc) are not being logged properly. I will fix that logging issue for next week and then we can try that approach to see if it gets us anything.

thanks,

Robin

Thanks Robin for your response.

I created and saved the following profile in V3.

v3 Check field bin1 9576x6388 (ZWO ASI6200MM Pro).ini
v3 Check field bin4 9568x6384 (ZWO ASI6200MM Pro).ini
V3 exp 10s BIN1 9576x6388 (ZWO ASI6200MM Pro).ini
V3 exp 10s BIN4 9568x6384 (ZWO ASI6200MM Pro).ini

I tried loading these two profiles several times in V4.1, but the camera stopped working.
There doesn't seem to be any connection between the 2-byte character profile and BIN.

Y.I.

Hi,

what we will do is try again with the new version that I will upload next week - that will have the corrected logging for control changes. I will also make a pair of capture profile files that only change binning and resolution (which I am sure are the key issues here), so that we can test with the absolute minimum of uncertainty about what is going on.

cheers,

Robin

Best regards.

When I change Frip None Pan:0 Tilt:0 to Both using the Camera Control Panel,
it changes to Pan:2 Tilt:1.
It's the same with V3.2 V4.1.
Is this normal?
Does it have anything to do with this error?

Pan:2 9576-9568=8 BIN4 =2
Tilt:1 6388-6384=4 BIN4 =1

Y.I.

Hi,

I think that *should* be fine...

What's happening is that because the exact maximum resolution isn't legal in bin4 with hardware binning on, there is a small range of pan/tilt available to adjust. When you use the 'flip' option, SharpCap internally reverses the ordering of the pan/tilt settings so that dragging the ROI box around still works as expected - the non-zero values you are seeing are the inverted values at the top end of the small available pan/tilt range.

I do generally advise against using the 'Flip' options from camera manufacturers. Those flip the orientation of the image before it gets to SharpCap, and because of that you need to make sure that any dark/flat frames that you use are captured with the same 'flip' settings. SharpCap has it's own 'Flip (after dark/flat)' setting that lets you adjust the orientation of the image without having to worry about needing different dark/flat frames for each orientation, since the flip operation is performed in SharpCap *after* the dark/flat correction.

cheers,

Robin

Robin

I haven't tried loading an ini file for a while.
I was using the camera controls directly, but I sometimes make mistakes, such as forgetting settings.
Even after upgrading, I still get errors.
I switch for each exposure, so it's inconvenient if I can't use the profile.
There's no problem with V3.2, so I could switch from V4.1 just for exposure,
but I can't use the other functions, so I'm in trouble.
I'd appreciate your consideration.

Y.I.