*** 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]
are these frame rates happening at full resolution on the camera, or when you are using ROI. In either case they are odd, since the values exceed those compatible with the exposure times (ie maximum 125fps at 8ms). If it is at full resolution then it is *doubly* odd as the data transfer rate to the PC should exclude those rates from happening. Unfortunately the log doesn't really record anything very helpful in this sort of situation.
Assuming that the frame rates you are seeing are happening with the camera at a small ROI then the logical conclusion would be that the camera is actually using an exposure a bit below (~30%) the specified value. That actually seems likely, since the percentage change from the expected frame rate is about the same in each case.
Hi Robin, I'm using a ROI - noticed the issue when I was capturing a recording of Jupiter last night.
I think the issue can be closed though, I was wondering if Firecapture had the same issue and apparently it does so this is something caused by the Touptek dll/driver and not by SharpCap. If you have some contacts at Touptek then please don't hesitate to get in touch with them to discuss. Otherwise, I'll drop them an email explaining the issue. Thanks for your feedback.
I'll pass this on to ToupTek - from all accounts it sounds like the calculation that converts exposure time into the camera commands needed isn't quite right for this model in the SDK.
actually it looks like there is a newer SDK version on the ToupTek download site than the once currently in SharpCap - I will try updating to that in the next SharpCap update to see if that helps.
