Some issues

derpit

Hi,

I'm using the latest (1.4) linux version of ASICAP with my ASI1600MM Pro.

There's two things I'd like to report, that hopefully can be taken care of in future versions:

Sometimes (as far as I can tell, when the exposure time is above 2s) changing the gain setting of the camera is ignored. I have to reduce exposure to 1s, change gain, then go back to long exposure

When klicking on the 'photo' icon to start saving frames as files, the software immediately stores the current/last frame in memory as first file. That is, if I change a setting and want to start taking data with that setting, I first have to wait until the software has finished a full exposure with those settings, else the first file will be a wrong one.

IMHO, when hitting the button the software should flush the cache and start a recording the moment I press the button, and then save that exposure as the first file

And maybe a feature request (unless I overlooked something): It would be nice to have a config setting for bit depth that is saved to the init settings. Not only once I had to restart capture because I forgot to switch to 16bit RAW....

Apart from that I really do like the software :)

hurely

Hi, DerPit

Thank you very much for your feedback.

1.About issue of long exposure, we tried many times, it didn't came out. Can you tell us more information, such as OS version, ROI, bit depth. We will keep trying.

2.About "immediately stores the current/last frame in memory as first file", That was designed on purpose. We will add a option setting in ASICAP to slove this problem about immediately or after long exposure.

3.For Now, ASICAP don't have a config setting about bit depth, ROI and bin, We will add these settings in future releases.

Please feel free to contact me if you have any questions about the problem of usage, my e-mail: lei.zhang@zwoptical.com

Thanks again.

derpit

Hello Hurley,

my excuses, I had not checked the thread in a while.

I am using ASICAP on Linux (openSUSE Tumbleweed, kernel 4.17.12). I've always been running 16bit mode only, but will try to see if it also happens with 8bit. But it had been very consistent also during my last imaging sessions. If exposure time is higher than one second, changes to the gain are ignored. This is with the maximum FOV. I'll also see if it is different if I only use a subfield.

Thanks. A config option would be perfect. The reason I ask: I often (mostly when changing filters) do a focus check at high gain and fast cadence. If I then switch back to storing data with long (minutes) exposure time I either need to wait, or remember to discard the first stored image. Neither is nice.

I'm looking forward to testing new versions. :)

hurely

Hi, DerPit

Thank you for your replay.

We will keep testing problems you said.

If there is any result, we will let you know.

derpit

Hi Hurley,

I just verified that it also happens in 8bit mode, as well as for reading out only subfields.

And I forgot to mention that I am indeed running the camera via an USB3 connection at 80% speed and/or auto.

Plus, if that is important, my desktop environment is KDE/Plasma5.

But I noticed that the value does change if I move the gain slider in the moment the exposure is finished and read out. Either the check for value change is not catching it properly during exposure, or there's some interference with the exposure countdown in the main window (the number showing remaining seconds to expose in the upper left of the image display)?

hurely

Hi, DerPit

Thanks for your feedback again.

There are too many Linux distributions, We spend a lot time to test, You may wait a while for result.

Hope you understand.

Lei