- edited description
Strange overlay when capturing with QHY294C using ASCOM drivers with "Remove Overscan Area" disabled (default)
NINA: nightly 1.10 # 58
ASCOM driver: 0.1.51.42
QHY SDK: 20.2.3.0
Now that QHY added the "Remove Overscan Area" option in their ASCOM driver and that by default it is disabled, there is an overlay on the capture frames (see attachments).
When opening ASCOM driver settings and ticking the option, the problem is fixed.
- It seems that NINA tries to remove overscan area forcefully, but does not do it correctly.
- I did not check, but will verify, I hope the frame is “overcropped” (cropped when not needed) when overscan is deactivated in the ASCOM driver.
Comments (8)
-
reporter -
reporter In that situation, I think NINA should stop trying to crop overscan and leave control to user with the ASCOM driver settings
-
reporter Checked resolution when disabling overscan in ASCOM and the fit is 4164x2796 which is the correct resolution.
-
repo owner Is this only about the ASCOM driver?
There we don’t have any special logic for overscan, as this is info is not available through the ascom interface. We just take what data we get out of the ascom driver.Is there a reason not using the native QHY implementation?
-
reporter I would prefer using the native driver indeed, but unfortunately, it does not work with bin2. For more details, here the issue I posted recently:
https://bitbucket.org/Isbeorn/nina/issues/440/image-download-fails-when-capturing-aI will test ASCOM with other software to confirm if it’s a general driver problem.
-
reporter Oh crap.. it’s on ASCOM driver side I think. I have the same problem under SharpCap…
-
reporter Opened a ticket at QHY
-
repo owner - changed status to closed
ok - i will close this issue for now. Will take a look into the binning issue.
- Log in to comment