Fails to Initialize Camera in ZWO ASI120MM
Posted: Wed Apr 16, 2025 5:02 am
Hi all,
I've been encountering a persistent and rather puzzling issue with SharpCap (64-bit, v4.1.10158) on my Windows 11 machine while attempting to initialize my ZWO ASI120MM camera. I’m posting here in hopes someone with deeper insight into SharpCap’s camera initialization pipeline or USB handling might be able to assist or point me toward further debugging options.
Symptoms:
Upon clicking "Cameras > ZWO ASI120MM" in the dropdown, SharpCap either:
Completely freezes for 15–20 seconds before throwing a "Camera Failed to Start" error.
Or crashes to desktop without an error window (event viewer shows an application hang in SharpCap.exe).
This behavior is intermittent but leans toward failure 90% of the time. The same camera works flawlessly with ASICap and FireCapture on the same system.
Is there a known issue with ASI120MM on SharpCap in recent builds?
Any advanced logs I can enable (verbose mode?) to trace the failure point?
Would using the DirectShow interface instead of native SDK bypass the issue as a test?
I've been encountering a persistent and rather puzzling issue with SharpCap (64-bit, v4.1.10158) on my Windows 11 machine while attempting to initialize my ZWO ASI120MM camera. I’m posting here in hopes someone with deeper insight into SharpCap’s camera initialization pipeline or USB handling might be able to assist or point me toward further debugging options.
Symptoms:
Upon clicking "Cameras > ZWO ASI120MM" in the dropdown, SharpCap either:
Completely freezes for 15–20 seconds before throwing a "Camera Failed to Start" error.
Or crashes to desktop without an error window (event viewer shows an application hang in SharpCap.exe).
This behavior is intermittent but leans toward failure 90% of the time. The same camera works flawlessly with ASICap and FireCapture on the same system.
Is there a known issue with ASI120MM on SharpCap in recent builds?
Any advanced logs I can enable (verbose mode?) to trace the failure point?
Would using the DirectShow interface instead of native SDK bypass the issue as a test?