-
Notifications
You must be signed in to change notification settings - Fork 2
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
Dimax number of recorded frames is dropping #4
Comments
Is it consistent if you stop recording? I could imagine, that the reported number is anything but a good indicator for the currently number of recorded frames. In any case, there isn't much magic going on, when reading that number. |
Then it is consistent, you are right. However, the value which you get after you stop recording is still less then what was really recorded. For example I acquired in sequence record mode and waited until the camera buffer was filled. Then it stopped recording itself, but gave 0 recorded frames. to illustrate this in a simpler manner when I stop the camera:
So now I neither know how many frames I recorded neither can I read out the full buffer with Concert if |
OK I could just read out until I get an exception from camera, but that's a dirty workaround. |
I also noticed the value in recorded frames is one too many. E.g. if the camera tells you |
FYI: to stop dropping frames, |
Thanks, I will try. |
Yeah it works. |
When auto trigger mode and external acquire mode the camera can be allowed or disallowed from recording frames by low-level TTL signal on acq. enable input. When I try to use it the number of recorded frames is dropping (see the Concert screenshot):
The text was updated successfully, but these errors were encountered: