Getting frame index in filecapture

[AgolovaUCL]

Hi, I'm capturing a video using Filecapture and I'd like to get as an output its current frame id (as I'm playing it). I don't see that as an output option. How could I get that? Many thanks!

[bruno-f-cruz]

Here are two options:

1- Use a ElementIndex after the FileCapture. This will "IndexStamp" each event from the FileCapture node. I should note that these are related to the order in which the frames arrive. If you are taking control over the playback of the video (e.g. using the default editor to "seek" frames, or pausing/playing the video) this strategy will fail
2- If you need control over the frame, you can use the StartPosition property of the FileCapture. This sets the frame number at subscription time so you will know what frame number the video is at at subscription and you can count from there. If you need multiple "skips", you can have N observable sequences for the same video.

Hope it helps!

[AgolovaUCL]

I used the first option and it worked. Thank you!

…

________________________________ From: Bruno Cruz ***@***.***> Sent: 16 September 2025 15:27 To: bonsai-rx/bonsai ***@***.***> Cc: Golova, Sophia ***@***.***>; Author ***@***.***> Subject: Re: [bonsai-rx/bonsai] Getting frame index in filecapture (Discussion #2427) ⚠ Caution: External sender Here are two options: 1- Use a ElementIndex after the FileCapture. This will "IndexStamp" each event from the FileCapture node. I should note that these are related to the order in which the frames arrive. If you are taking control over the playback of the video (e.g. using the default editor to "seek" frames, or pausing/playing the video) this strategy will fail 2- If you need control over the frame, you can use the StartPosition property of the FileCapture. This sets the frame number at subscription time so you will know what frame number the video is at at subscription and you can count from there. If you need multiple "skips", you can have N observable sequences for the same video. Hope it helps! — Reply to this email directly, view it on GitHub<#2427 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A5XPZKVEE2Q7PG4MR6BR75L3TAT5RAVCNFSM6AAAAACGULKSXOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTINBRG44DGNQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>