The attached bug files are unique. They are not duplicates. The relate to the inability of sensor analysis to be carried out on this camera in Beta Sharpcap 4.0 even though the camera was in still mode
The other group bug reports is the inability of flats to be captured and averaged.
Dan Kahraman
Bug Reports Mallincam DS26c camera
Forum rules
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
Please also read about Troubleshooting USB Issues before posting.
*** 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]
If you have a problem or question, please check the FAQ to see if it already has an answer : https://www.sharpcap.co.uk/sharpcap-faqs
Please also read about Troubleshooting USB Issues before posting.
*** 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]
Bug Reports Mallincam DS26c camera
- Attachments
-
- InvalidOperationException at System.Linq.Enumerable.First_TSource_(IEnumerable_TSource_ source)_#11902.error.zip
- (15.54 KiB) Downloaded 55 times
-
admin
- Site Admin
- Posts: 13339
- Joined: Sat Feb 11, 2017 3:52 pm
- Location: Vale of the White Horse, UK
- Contact:
Re: Bug Reports Mallincam DS26c camera
Hi Dan,
in order:
#1 Camera seems to be not responding during flat capture, no frames saved, application closed during flat capture.
#2 3.2 bug report - problem with dark captures - no frames captured
#3 Very much like #1 - flat capture, no frames saved
#4 3.2 again, very much like #2
#5 Sensor analysis in this one - looks like it had not progressed far and then you deselected and reselected it, possibly causing the error. Lots of 'Single Frame Capture failed' messages in the log which is worrying- camera not responding properly?
#6 Very much like #5, single frame capture failed messages
#7 Very much like #5 - camera analysis being stopped and started again from the menu.
I think overall the picture is that the camera is sometimes not responding properly to SharpCap and that things tend to go even more wrong after that has happened - the reports are useful as they point me to several parts of the code that need to be made more robust against a badly behaved camera, but even if I do that you will just get a message along the lines of 'Your camera stopped working' instead of a crash.
The real fix would be to work out why the camera is being unreliable, but while I can add more logging to track any error in more detail, I think there is something unreliable in the ASCOM driver itself. If you have any configuration for USB speed, try turning that down (see this post for more hints : viewtopic.php?f=18&t=349&p=1556#p1556)
Robin
in order:
#1 Camera seems to be not responding during flat capture, no frames saved, application closed during flat capture.
#2 3.2 bug report - problem with dark captures - no frames captured
#3 Very much like #1 - flat capture, no frames saved
#4 3.2 again, very much like #2
#5 Sensor analysis in this one - looks like it had not progressed far and then you deselected and reselected it, possibly causing the error. Lots of 'Single Frame Capture failed' messages in the log which is worrying- camera not responding properly?
#6 Very much like #5, single frame capture failed messages
#7 Very much like #5 - camera analysis being stopped and started again from the menu.
I think overall the picture is that the camera is sometimes not responding properly to SharpCap and that things tend to go even more wrong after that has happened - the reports are useful as they point me to several parts of the code that need to be made more robust against a badly behaved camera, but even if I do that you will just get a message along the lines of 'Your camera stopped working' instead of a crash.
The real fix would be to work out why the camera is being unreliable, but while I can add more logging to track any error in more detail, I think there is something unreliable in the ASCOM driver itself. If you have any configuration for USB speed, try turning that down (see this post for more hints : viewtopic.php?f=18&t=349&p=1556#p1556)
Robin