Author Topic: Mixed images in segmented mode  (Read 4729 times)

pantxoD

  • Newbie
  • *
  • Posts: 4
    • View Profile
Mixed images in segmented mode
« on: January 26, 2022, 09:04:34 AM »
Hi,

We use a Chronos 1.4 (0.6 firmware) to shoot typically 50 blocks (segments) of 400 images at close to max frame rate (995fps). FWIW each segment is started at about 5 seconds interval, using an external TTL trigger on the BNC input of trigg1.

I would expect the exported images to be frame_000001.tiff->frame_000400.tiff for the first block, then 401->800 for the second block and so on. But instead the first block only has 398 images (frame_000001.tiff->frame_000398.tiff) while the second and the others (except the last) have the expected 400 images (399->798, 799...). Finally, the last block contains 403 images, the last 3 of which seem to belong to the beginning of the first block.

Is this a known issue and if so is there a workaround?

Since my explanation may be confusing, don't hesitate to ask for details.

Nikon1

  • Hero Member
  • *****
  • Posts: 983
    • View Profile
Re: Mixed images in segmented mode
« Reply #1 on: January 26, 2022, 09:40:43 AM »
There kind of is, but i am not sure if the Problem itself causing that is well enough known to be able to fix that. The Framerate counter behaves weirdly and inconsistent sometimes, and saving small numbers of frames has had Glitches as long as i know.
 .
 I am not aware of a Known workaround, if you actually need an exact amount number of frames for each Segment, other than to just save a bunch more than you need and delete / ignore the ones that are not needed later (thats what i did, just make sure, i have enough. if i need 25 Frames, save ~40 just to be sure).
 .
 Existing Discussions (which i am aware of) about this Topic and Related issues:
 .
 https://forum.krontech.ca/index.php?topic=659.0
 https://forum.krontech.ca/index.php?topic=565.msg3892#msg3892

pantxoD

  • Newbie
  • *
  • Posts: 4
    • View Profile
Re: Mixed images in segmented mode
« Reply #2 on: January 27, 2022, 02:36:09 AM »
Thanks, now I know this is a known issue  :P.