*** 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]
Additionally, the camera refuses to settle on an exposure time.
Not sure if this the contributing factor for the sensor analysis issue.
posting my debug log...
Info: 18:23:25.7267048 Thread:#1 SharpCap.Program.Main() :: Starting...
Info: 18:23:25.8048348 Thread:#1 SharpCap.Program.SetupNBUG() :: Setting up bug reporting.
Info: 18:23:25.8360793 Thread:#1 SharpCap.LogSystemInfo.Run() :: Starting thread to log system info
Info: 18:23:25.8360793 Thread:LogInfo Thread#9 SharpCap.LogSystemInfo.ThreadProc() :: SharpCap Version 3.2.6480.0
Info: 18:23:25.8360793 Thread:LogInfo Thread#9 SharpCap.LogSystemInfo.ThreadProc() :: GC Memory 119Mb
Info: 18:23:25.8360793 Thread:LogInfo Thread#9 SharpCap.LogSystemInfo.ThreadProc() :: Process Memory 169Mb
Info: 18:23:25.8360793 Thread:LogInfo Thread#9 SharpCap.LogSystemInfo.ThreadProc() :: Total Physical Memory 7549Mb
Info: 18:23:25.8360793 Thread:LogInfo Thread#9 SharpCap.LogSystemInfo.ThreadProc() :: Available Physical Memory 4233Mb
Info: 18:23:25.8673458 Thread:#1 SharpCap.Program.RunApp(Boolean showSplash) :: Setting up application
Info: 18:23:25.8673458 Thread:#1 SharpCap.Program.RunApp(Boolean showSplash) :: Initializing WPF
Debug: 18:23:25.8985839 Thread:#1 SharpCap.UI.SharpCapForm..ctor() :: Started
Info: 18:23:25.9454615 Thread:LogInfo Thread#9 SharpCap.LogSystemInfo.ThreadProc() :: Operating System : Microsoft Windows 10 Home
Info: 18:23:25.9454615 Thread:LogInfo Thread#9 SharpCap.LogSystemInfo.ThreadProc() :: Full OS Version 10.0.18363
Info: 18:23:25.9454615 Thread:LogInfo Thread#9 SharpCap.LogSystemInfo.ThreadProc() :: OS is 64 bit, SharpCap is 64 bit.
Info: 18:23:25.9610891 Thread:#1 SharpCap.ImageProcessing.AstapPlateSolverFactory.CheckInstalledImpl() :: Astap found at c:\Program Files\Astap\Astap.exe
Info: 18:23:25.9610891 Thread:#1 SharpCap.ImageProcessing.CombinedAstrometryPlateSolveFactory.CheckInstalledImpl() :: Plate solver detection : Manually configured Astrometry - Not configured
Info: 18:23:25.9610891 Thread:#1 SharpCap.ImageProcessing.CombinedAstrometryPlateSolveFactory.CheckInstalledImpl() :: Plate solver detection : AstroTortilla - Not found
Info: 18:23:25.9610891 Thread:#1 SharpCap.ImageProcessing.AstrometryNetPlateSolveFactory.CheckInstalledImpl() :: Found All Sky Plate Solver at C:\Users\Dilig\AppData\Local\Astrometry
Info: 18:23:25.9610891 Thread:#1 SharpCap.ImageProcessing.CombinedAstrometryPlateSolveFactory.CheckInstalledImpl() :: Plate solver detection : All Sky Plate Solver - Found at C:\Users\Dilig\AppData\Local\Astrometry
Info: 18:23:25.9610891 Thread:#1 SharpCap.ImageProcessing.CombinedAstrometryPlateSolveFactory.CheckInstalledImpl() :: Plate solver detection : Ansvr - Not found at C:\Users\Dilig\AppData\Local\cygwin_ansvr
Info: 18:23:25.9610891 Thread:#1 SharpCap.ImageProcessing.CombinedAstrometryPlateSolveFactory.CheckInstalledImpl() :: Plate solver detection : Cygwin/Astrometry based - Not found at C:\cygwin
Info: 18:23:25.9923470 Thread:#1 SharpCap.MultiCaptureProvider.AddProvider() :: Added device enumerator of type QHYDeviceEnumerator
Info: 18:23:25.9923470 Thread:#1 SharpCap.MultiCaptureProvider.AddProvider() :: Added device enumerator of type ASIDeviceEnumerator
Info: 18:23:25.9923470 Thread:#1 SharpCap.MultiCaptureProvider.AddProvider() :: Added device enumerator of type AltairDeviceEnumerator
Info: 18:23:25.9923470 Thread:#1 SharpCap.MultiCaptureProvider.AddProvider() :: Added device enumerator of type SVBonyDeviceEnumerator
Info: 18:23:25.9923470 Thread:#1 SharpCap.Base.InterfaceFactory`2.ScanDll(String filename) :: Probing for camera providers : C:\Program Files\SharpCap 3.2 (64 bit)\SharpCap.Cameras.Altair.dll
Info: 18:23:25.9923470 Thread:#1 SharpCap.Base.InterfaceFactory`2.ScanDll(String filename) :: Probing for camera providers : C:\Program Files\SharpCap 3.2 (64 bit)\SharpCap.Cameras.ASCOMCamera.dll
Info: 18:23:26.0079799 Thread:#1 SharpCap.Base.InterfaceFactory`2.ScanDll(String filename) :: Probing for camera providers : C:\Program Files\SharpCap 3.2 (64 bit)\SharpCap.Cameras.ASI.dll
Info: 18:23:26.0079799 Thread:#1 SharpCap.Base.InterfaceFactory`2.ScanDll(String filename) :: Probing for camera providers : C:\Program Files\SharpCap 3.2 (64 bit)\SharpCap.Cameras.Atik.dll
Info: 18:23:26.0079799 Thread:#1 SharpCap.Base.InterfaceFactory`2.ScanDll(String filename) :: Probing for camera providers : C:\Program Files\SharpCap 3.2 (64 bit)\SharpCap.Cameras.Celestron.dll
Info: 18:23:26.0079799 Thread:#1 SharpCap.Base.InterfaceFactory`2.ScanDll(String filename) :: Probing for camera providers : C:\Program Files\SharpCap 3.2 (64 bit)\SharpCap.Cameras.DS3.dll
Info: 18:23:26.0079799 Thread:#1 SharpCap.Base.InterfaceFactory`2.ScanDll(String filename) :: Probing for camera providers : C:\Program Files\SharpCap 3.2 (64 bit)\SharpCap.Cameras.Fake.dll
Info: 18:23:26.0079799 Thread:#1 SharpCap.Base.InterfaceFactory`2.ScanDll(String filename) :: Probing for camera providers : C:\Program Files\SharpCap 3.2 (64 bit)\SharpCap.Cameras.Moravian.dll
Info: 18:23:26.0079799 Thread:#1 SharpCap.Base.InterfaceFactory`2.ScanDll(String filename) :: Probing for camera providers : C:\Program Files\SharpCap 3.2 (64 bit)\SharpCap.Cameras.NewDirectShow.dll
Info: 18:23:26.0079799 Thread:#1 SharpCap.Base.InterfaceFactory`2.ScanDll(String filename) :: Probing for camera providers : C:\Program Files\SharpCap 3.2 (64 bit)\SharpCap.Cameras.QHY.dll
Info: 18:23:26.0079799 Thread:#1 SharpCap.Base.InterfaceFactory`2.ScanDll(String filename) :: Probing for camera providers : C:\Program Files\SharpCap 3.2 (64 bit)\SharpCap.Cameras.SVBony.dll
Info: 18:23:26.0079799 Thread:#1 SharpCap.MultiCaptureProvider.AddProvidersByReflection(String[] providerNames) :: Added device enumerator of type CelestronDeviceEnumerator
Info: 18:23:26.0079799 Thread:#1 SharpCap.MultiCaptureProvider.AddProvider() :: Added device enumerator of type MoravianDeviceEnumerator
Info: 18:23:26.0079799 Thread:#1 SharpCap.MultiCaptureProvider.AddProvider() :: Added device enumerator of type AtikDeviceEnumerator
Info: 18:23:26.0079799 Thread:#1 SharpCap.MultiCaptureProvider.AddProvider() :: Added device enumerator of type DS3DeviceEnumerator
Info: 18:23:26.0079799 Thread:#1 SharpCap.MultiCaptureProvider.AddProvider() :: Added device enumerator of type AscomDeviceEnumerator
Info: 18:23:26.0079799 Thread:#1 SharpCap.MultiCaptureProvider.AddProvider() :: Added device enumerator of type FolderMonitorDeviceEnumerator
Info: 18:23:26.0079799 Thread:#1 SharpCap.MultiCaptureProvider.AddProvider() :: Added device enumerator of type FakeDeviceEnumerator
Info: 18:23:26.0704759 Thread:#1 SharpCap.ProxyFinder`1.LoadProxiesForFactoryType(Type t) :: Loading Hardware Proxies from SharpCap.WheelProxy.ASCOM.WheelFactory
Info: 18:23:26.0861150 Thread:#1 SharpCap.ProxyFinder`1.LoadProxiesForFactoryType(Type t) :: Found device QHYCCD FilterWheel
Info: 18:23:26.0861150 Thread:#1 SharpCap.ProxyFinder`1.LoadProxiesForFactoryType(Type t) :: Found device QHYCCD FilterWheel2st
Info: 18:23:26.0861150 Thread:#1 SharpCap.ProxyFinder`1.LoadProxiesForFactoryType(Type t) :: Found device Filter Wheel Simulator [.Net]
Info: 18:23:26.0861150 Thread:#1 SharpCap.ProxyFinder`1.LoadProxiesForFactoryType(Type t) :: Found device Simulator
Info: 18:23:26.0861150 Thread:#1 SharpCap.ProxyFinder`1.LoadProxiesForFactoryType(Type t) :: Loading Hardware Proxies from SharpCap.WheelProxy.ZWO.WheelFactory
Info: 18:23:26.1017410 Thread:#1 SharpCap.ProxyFinder`1.LoadProxiesForFactoryType(Type t) :: Loading Hardware Proxies from SharpCap.WheelProxy.ZWO.ManualWheelFactory
Info: 18:23:26.1017410 Thread:#1 SharpCap.ProxyFinder`1.LoadProxiesForFactoryType(Type t) :: Found device Manual Filter Wheel
Info: 18:23:26.1173670 Thread:#1 SharpCap.ProxyFinder`1.LoadProxiesForFactoryType(Type t) :: Loading Hardware Proxies from SharpCap.MountProxy.ASCOM.MountFactory
Info: 18:23:26.1173670 Thread:#1 SharpCap.ProxyFinder`1.LoadProxiesForFactoryType(Type t) :: Found device Celestron Telescope Driver
Info: 18:23:26.1173670 Thread:#1 SharpCap.ProxyFinder`1.LoadProxiesForFactoryType(Type t) :: Found device CPWI
Info: 18:23:26.1173670 Thread:#1 SharpCap.ProxyFinder`1.LoadProxiesForFactoryType(Type t) :: Found device Device Hub Telescope
Info: 18:23:26.1173670 Thread:#1 SharpCap.ProxyFinder`1.LoadProxiesForFactoryType(Type t) :: Found device Telescope Simulator for .NET
Info: 18:23:26.1173670 Thread:#1 SharpCap.ProxyFinder`1.LoadProxiesForFactoryType(Type t) :: Found device Simulator
Info: 18:23:26.1486084 Thread:#1 SharpCap.UI.SharpCapForm..ctor() :: Application model created
Info: 18:23:26.3986199 Thread:#1 SharpCap.UI.SharpCapForm..ctor() :: Control Form created
Info: 18:23:26.4142424 Thread:#1 SharpCap.UI.SharpCapForm..ctor() :: View model initialized
Info: 18:23:26.4454948 Thread:#1 SharpCap.UI.SharpCapForm..ctor() :: Preview host created
Info: 18:23:26.4454948 Thread:#1 SharpCap.Base.Utilities.Logger.LogStackTrace(LogLevel level, String msg) :: Parent being changed on PreviewPanel
I am starting to think my recent problems, "All revolve around the Windows OS updating of drivers."
I am starting to suspect recent updates to my ASCOM or QHYCCD(native) drivers that where installed are 'THE' contributing factor.
I am not sure, if these updates where applied prior to my problems or after.
Since my solution to the problem was to purchase a brand new QHY268c camera. I have two now. I am ok with this.
Bit coins, bit coins, no skin off my teeth. But, upon reflection, the new camera ABSOLUTELY refuses to settle on an exposure time.
AQfter nearly 1.5 hours of trying to capture my first frame.PNG (19.25 KiB) Viewed 1004 times
Meaning, the issues I am experiencing maybe related to lazy Windows OS features, not wanting to discard old drivers.
Windows may very well be keeping these newer ASCOM and QHYCCD drivers through *.inf files even though the software was uninstalled.
So any roll back, "The most newer default drivers are persistent through these *.inf files and windows uninstalling software does not delete the newer drivers on uninstalls. So upon uninstall and re-install. The most newer drivers(which may the root cause of the problem, are blindly being re-installed in the roll back to earlier versions.)
Since Windows in checking for the latest drivers of software being installed, "The registry very well have been been wiped clean, but because the newer drivers may have not been deleted in the uninstall, whether related to ASCOM or QHYCDD(native). They may not have been removed in the uninstall, and being maintained through these *.inf files such that the roll back attempt to earlier versions of SharpCap and/or ASCOM/QHYCDD(native drivers) simply may be re-installing these latest drivers(which may be root cause of the problem).
Currently I am running ASCOM version 6.5.1.3234 and QHYCCD_WIN ALLInOne version 20.06.26.36. Both of these versions, I had updated prior to experienceing my earlier issues and/or having update them to solve my issues.
However, since rolling back to earlier versions(where I had functional software/drivers in place) .
Such that when I rolled backed the software to earlier versions of ASCOM and QHYCCD(native versions) where everything was working, "Did I really achieve this outcome? Am I still applying suspect drivers and/or the SDK *.dll's."
At this point, my only recourse is to roll back the Window's OS to factory settings prior to ASCOM and QHYCCD origin installs. And re-install these ASCOM and QHYCDD All-In ones drivers that where working just fine prior to my problems.
YUCK!!!!
So I am very much questioning whether I am truly running, "Earlier versions of these software packages/drivers when my camera was just running just fine."
If upon re-install to earlier versions of ASCOM and/or QHYCDD drivers(native) that SharpCap interacts with through the SDKs, "Some where along the line a suspect driver or *.dll may be still be re-installed the to latest (suspect) version and could be the root cause of my experienced issues.
Since updates/roll backs maybe still persistent through these *.inf files."
Such is the state of third party software dependencies. Just, saying, "It is not unheard of."
Sincerely,
MTK
P.S. What I am describing is not not unheard of in the world of Window drivers, meaning *.inf persistence is often the root cause of driver issues."
As a further note. Now having two cameras that may be functional valid.
I am going to send one of them off to a company eventually that states they can remove the debayer matrix with the result to a mono camera by removing the debayer matrix.
in answer to your dissapearing start button - I think that all that has happened is that the height of the Sensor Analysis are of the screen has become a bit too small somehow - that means that the start button is lost just off screen.
Hover your mouse over the dividing line between the sensor analysis area and the main display area above - you should be able to drag the division upwards to reveal the start button.
I would be very cautious about trying to remove the bayer matrix from a camera (even if someone else is doing it). This was OK on cheap partly broken consumer DSLR cameras, but is a big risk on a working high spec astro camera. Also remember that the process will also remove the microlenses, reducing the light sensitivity of the camera and I have seen many examples where the result is imperfect (not producing an even image).
Like the previous post...I too have no "Proceed" or "Start" button when I try to complete the Sensor Analysis procedure.
My version of SharpCap is 4.09556.0 May/2/23
Is this due to a "scaling issue" as my laptop recommended resolution is 3840 x 2160
In on of your previous posts you mention "Hover your mouse over the dividing line between the sensor analysis area and the main display area above - you should be able to drag the division upwards to reveal the start button".
I try this ... unfortunately, that doesn't resolve the issue.
do you happen to know what scaling you have set for your monitor? I think windows recommends 175% or maybe 200% on that sort of monitor usually.
Either way, it should scale correctly unless you have adjusted other settings in the 'Advanced Scaling Settings' in Windows. I have just tried on a 3840x2160 display set at 200% and I cannot make the analysis area shorter than it should be (ie I cannot change the height so that the 'Start' button vanishes).
If you download and watch the video above, it shows how the height can be increased if it does come out too short to show those buttons. Hover the mouse over the dividing line until the mouse cursor changes to up and down arrows, then press and hold left mouse button and drag upwards. Hopefully this should sort out the issue.
