-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sharpcap crashes when selecting the Lumix camera (S1) #4
Comments
i dont have the S1 so hard for me to reproduce. however:
I have not been using sharpcap really as it is better suited for video/liveview cameras. When I connect my lumix it is emulating a liveview by taking constant shots. do you experience the same behaviour? The only exception i have seen so far is if i take too short exposure once connected then the driver does not have the time to get the image on the PC and i have a "file not found" exception. |
Hello, I have a GX880 and am experiencing the same issue with Sharpcap - it connects, but bails out when it takes its first picture. I've tried Thumb mode and a few other settings, nothing helps. Idenfies as a GF10. Ascom diagnostics seems to connect ok Temporary folder exists and there's images in there. CheckDotNetExceptions ASCOM.Lumix.Camera ImageArray Get System.ArgumentNullException: Path cannot be null. |
did you find a solution? |
No, hence the post |
any update on this? |
i did a fresh test this am with sharpcap 4.0 64 bits and my lumix gh5s. it works rather well. either in " live view" or still mode. |
when I check the properties it says that there are no cameras. so it doesn't find it. |
so in that case here is the fool proof method:
|
not sure if I can connect to my home wifi. I have to check this with the camera wifi I know for sure the IP, in any case the diagnostics gives this when I connect Create Creating device Name Lumix Ascom Driver Connected Disconnecting from device |
I have a panasonic S1, when I select the ascom Lumix on sharpcap I have this error:
The text was updated successfully, but these errors were encountered: