Dimax number of recorded frames is dropping about libpco

[matze]

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.

[tfarago]

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:

dimax > camera.start_recording()

dimax > camera.recorded_frames
<Quantity(0, 'dimensionless')>

dimax > camera.recorded_frames
<Quantity(0, 'dimensionless')>

dimax > trigger.on()

dimax > trigger.off()

dimax > camera.recorded_frames
<Quantity(193, 'dimensionless')>

dimax > camera.recorded_frames
<Quantity(126, 'dimensionless')>

dimax > camera.recorded_frames
<Quantity(0, 'dimensionless')>

dimax > camera.stop_recording()

dimax > camera.recorded_frames
<Quantity(0, 'dimensionless')>

So now I neither know how many frames I recorded neither can I read out the full buffer with Concert if num_frames is None, i.e. I want to read out everything.

[tfarago]

OK I could just read out until I get an exception from camera, but that's a dirty workaround.

[tfarago]

I also noticed the value in recorded frames is one too many. E.g. if the camera tells you n you can actually read n - 1 images. Is that normal behavior for PCO?

[matze]

FYI: to stop dropping frames, camera.storage_mode must be set to RECORDER and not FIFO_BUFFER.

[tfarago]

Thanks, I will try.

[tfarago]

Yeah it works.