# ZedX Timestamps

**URL:** <https://community.stereolabs.com/t/zedx-timestamps/8924>\
**Category:** Software\
**Created:** [May 27, 2025, 5:58pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924 "2025-05-27T17:58:28Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![robots](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/r/48db29/32.png) [@robots](https://community.stereolabs.com/u/robots)\
**Post date:** [May 27, 2025, 5:58pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/1 "2025-05-27T17:58:28Z")

</div>

What does `camera.get_timestamp(sl.TIME_REFERENCE.IMAGE)` represent on the ZedX cameras using a quad link capture card? I want to know, with the highest precision possible, when the end of the camera exposure occurred to properly calculate transforms and mask areas of the scene.

I’ve read [Sensors Time Synchronization - Stereolabs](https://www.stereolabs.com/docs/sensors/time-synchronization) and all the pages/posts on camera latency, but am still confused. Reading  
[ZED Link Quad GPIO Triggering - Stereolabs](https://www.stereolabs.com/docs/get-started-with-zed-link/zed-link-quad-triggering) “The output trigger signals are two square wave, with their rising edge synchronized with the end of the exposure phase of the CMOS sensors.” gives me optimism that the capture time can precisely be known. However, I’m unsure if that is exposed in the API or whether I need to create a setup involving the GPIO pins to know the exposure end time within a few milliseconds.

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [May 28, 2025, 1:50pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/2 "2025-05-28T13:50:22Z")

</div>

> [@robots](#):
>
> What does `camera.get_timestamp(sl.TIME_REFERENCE.IMAGE)` represent on the ZedX cameras using a quad link capture card?

It’s the system time when the full sample has been received by the GMSL2 deserializer.

> [@robots](#):
>
> I’ve read [Sensors Time Synchronization - Stereolabs](https://www.stereolabs.com/docs/sensors/time-synchronization) and all the pages/posts on camera latency, but am still confused. Reading  
> [ZED Link Quad GPIO Triggering - Stereolabs](https://www.stereolabs.com/docs/get-started-with-zed-link/zed-link-quad-triggering) “The output trigger signals are two square wave, with their rising edge synchronized with the end of the exposure phase of the CMOS sensors.” gives me optimism that the capture time can precisely be known. However, I’m unsure if that is exposed in the API or whether I need to create a setup involving the GPIO pins to know the exposure end time within a few milliseconds.

You can use this information to know the exact instant when the frame is ready.  
The SDK cannot be aware of this information because there’s no link between the deserializer GPIO and the SDK.

---

<div class="post-metadata">

**Author:** ![robots](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/r/48db29/32.png) [@robots](https://community.stereolabs.com/u/robots)\
**Post date:** [May 28, 2025, 3:03pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/3 "2025-05-28T15:03:31Z")

</div>

Good to know. Can you verify my understanding?

1. 

> It’s the system time when the full sample has been received by the GMSL2 deserializer.

Will this timestamp will be 1-2 frames after the exposure ended? Based on  
[GMSL ZED x vs regular zed and usb cable --- latency - #2 by Myzhar](https://community.stereolabs.com/t/gmsl-zed-x-vs-regular-zed-and-usb-cable-latency/2681/2) . Also does the latency really scale inversely with framerate?  
2.

> The SDK cannot be aware of this information because there’s no link between the deserializer GPIO and the SDK.

Has there been any consideration around integrating this into the SDK? The setup I’m imagining is connecting the capture card GPIO pins to the Jetson’s GPIO pins. Would that allow for syncronizing the timestamps with the true exposure time? Is there any way to transmit this over the CSI port? Any information you can provide here is useful both in the context of potential future SDK features and just general knowledge as I may try to build this setup myself.

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [May 29, 2025, 9:07am UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/4 "2025-05-29T09:07:40Z")

</div>

[quote=“robots, post:3, topic:8924”]  
Will this timestamp will be 1-2 frames after the exposure ended? Based on  
[GMSL ZED x vs regular zed and usb cable — latency - #2 by Myzhar](https://community.stereolabs.com/t/gmsl-zed-x-vs-regular-zed-and-usb-cable-latency/2681/2) .[/quote]  
Yes, this is correct

> [@robots](#):
>
> Also does the latency really scale inversely with framerate?

What do you mean?

> [@robots](#):
>
> Has there been any consideration around integrating this into the SDK? The setup I’m imagining is connecting the capture card GPIO pins to the Jetson’s GPIO pins. Would that allow for syncronizing the timestamps with the true exposure time? Is there any way to transmit this over the CSI port? Any information you can provide here is useful both in the context of potential future SDK features and just general knowledge as I may try to build this setup myself.

This is under investigation. I’m not sure it’s possible to send GPIO pin status over GMSL2 without introducing latency which will make this mechanism unuseful.

---

<div class="post-metadata">

**Author:** ![robots](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/r/48db29/32.png) [@robots](https://community.stereolabs.com/u/robots)\
**Post date:** [May 29, 2025, 1:52pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/5 "2025-05-29T13:52:52Z")

</div>

> [@robots](#):
>
> Also does the latency really scale inversely with framerate?

At 60FPS 1-2 frames of latency is 16-32ms of latency. At 30FPS 1-2 frames becomes 32-64ms of latency. It’s suspicious to me that a lower frame rate would result in a higher absolute latency.

> This is under investigation. I’m not sure it’s possible to send GPIO pin status over GMSL2 without introducing latency which will make this mechanism unuseful.

I may be misunderstanding component names, but my goal isn’t to send anything over GMSL2. I want to connect the capture card pins to the Jetson’s GPIO pins. I would then poll on the Jetson for the voltage changes to get a more accurate timestamp. I’d pairwise match the nth frame capture to the timestamp of the nth voltage change.

 ![image](https://community.stereolabs.com/uploads/default/original/2X/9/9218ece5db1e11c6fe164a8bea95c5b3025a8199.png)

 ![image](https://community.stereolabs.com/uploads/default/original/2X/4/47a9a7ac1c106fef709a32aeb7bbcf527700cb04.jpeg)

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [May 30, 2025, 9:31am UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/6 "2025-05-30T09:31:45Z")

</div>

> [@robots](#):
>
> At 60FPS 1-2 frames of latency is 16-32ms of latency. At 30FPS 1-2 frames becomes 32-64ms of latency. It’s suspicious to me that a lower frame rate would result in a higher absolute latency.

This is instead expected because the latency is caused by buffering.

> [@robots](#):
>
> I may be misunderstanding component names, but my goal isn’t to send anything over GMSL2. I want to connect the capture card pins to the Jetson’s GPIO pins. I would then poll on the Jetson for the voltage changes to get a more accurate timestamp. I’d pairwise match the nth frame capture to the timestamp of the nth voltage change.

This is something that you can apply. Unfortunately, this is a feature so “custom” that it cannot be integrated into the ZED SDK, at least now.

---

<div class="post-metadata">

**Author:** ![Parv-Maheshwari](https://community.stereolabs.com/user_avatar/community.stereolabs.com/parv-maheshwari/32/5756_2.png) [@Parv-Maheshwari](https://community.stereolabs.com/u/Parv-Maheshwari)\
**Post date:** [February 19, 2026, 4:44pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/7 "2026-02-19T16:44:53Z")

</div>

I have couple of questions regarding this

- Will the timestmap itself be delayed 1-2 frames on the image , or will the image be delivered -12 frames later but the timestamp is correct
- Regading the 1-2 frame latency due to buffering - if its only buffreing then wehere does the stochasticity orginate from - int he sense that why is not not 1 frame
- Overall given a timestamp of a image - is there anyway to back calculate the exact time the exposure ended for that image

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [February 19, 2026, 5:00pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/8 "2026-02-19T17:00:53Z")

</div>

> [@Parv-Maheshwari](#):
>
> Will the timestmap itself be delayed 1-2 frames on the image , or will the image be delivered -12 frames later but the timestamp is correct

The timestamp is assigned as soon as the image is available in the memory, to the only bias is caused by the data transfer time.

> [@Parv-Maheshwari](#):
>
> Regading the 1-2 frame latency due to buffering - if its only buffreing then wehere does the stochasticity orginate from - int he sense that why is not not 1 frame

This details cannot be undisclosed. I can only say that it’s not eliminable.

> [@Parv-Maheshwari](#):
>
> Overall given a timestamp of a image - is there anyway to back calculate the exact time the exposure ended for that image

You can only do this statistically.

---

<div class="post-metadata">

**Author:** ![Parv-Maheshwari](https://community.stereolabs.com/user_avatar/community.stereolabs.com/parv-maheshwari/32/5756_2.png) [@Parv-Maheshwari](https://community.stereolabs.com/u/Parv-Maheshwari)\
**Post date:** [February 19, 2026, 6:19pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/9 "2026-02-19T18:19:53Z")

</div>

> [@Myzhar](#):
>
> The timestamp is assigned as soon as the image is available in the memory, to the only bias is caused by the data transfer time.

Is the data transfer time same as the 1-2 frame latency ?

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [February 20, 2026, 10:00am UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/10 "2026-02-20T10:00:34Z")

</div>

> [@Parv-Maheshwari](#):
>
> Is the data transfer time same as the 1-2 frame latency ?

No, this is very fast.

---

<div class="post-metadata">

**Author:** ![Parv-Maheshwari](https://community.stereolabs.com/user_avatar/community.stereolabs.com/parv-maheshwari/32/5756_2.png) [@Parv-Maheshwari](https://community.stereolabs.com/u/Parv-Maheshwari)\
**Post date:** [February 23, 2026, 2:25am UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/11 "2026-02-23T02:25:50Z")

</div>

> [@Myzhar](#):
>
> No, this is very fast.

Okay, in that case can you please clarify which of the following is the case with respcet to zed sdk

- the image is timestampped at the moment it is captured (exposure time ends) but it is only avaible after 1-2 frmaes to be grabbed - essentially the timestamp is correct with repest to the image, and the overall frame (image + timestamp) is 1-2 frames stale/delayed
- The image is timestamped after it is available in the memory. The image is avaible in memory only after the 1-2 frames. In that case the image timestamp is ahead of the actual time of capture of the image by 1-2 frames
- Something else - If yes, please clarify how th efollwonig are realted to each other - a) end of exposure time (true image capture time) b) timestamp on the image c) when the frame is available to be grabbed

---

<div class="post-metadata">

**Author:** ![Parv-Maheshwari](https://community.stereolabs.com/user_avatar/community.stereolabs.com/parv-maheshwari/32/5756_2.png) [@Parv-Maheshwari](https://community.stereolabs.com/u/Parv-Maheshwari)\
**Post date:** [February 25, 2026, 7:05pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/12 "2026-02-25T19:05:23Z")

</div>

@Myzhar can you please help with this.

---

<div class="post-metadata">

**Author:** ![andrwr\_rev](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/a/e0b2c6/32.png) [@andrwr\_rev](https://community.stereolabs.com/u/andrwr_rev)\
**Post date:** [March 5, 2026, 11:25pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/13 "2026-03-05T23:25:19Z")

</div>

I second a lot of the questions that have been asked in this thread, and would like to revive it. Reading this, it is not clear to me exactly what the timestamps corresponding to `TIME_REFERENCE::IMAGE` mean.

From @Myzhar ‘s first comments it sounds like timestamps will lag the true “shutter closing time” by 1-2 frames. E.g. for a system running at 15 FPS, there will be a lag of about 66 to 133 ms (which is quite high IMO). In another comment, he writes that

> The timestamp is assigned as soon as the image is available in the memory, to the only bias is caused by the data transfer time

which is apparently “very fast”. This section seems contradictory to me. Let’s say we have a GMSL system operating at 15 FPS. We have two events. Event A: the shutter closes. Event B: the image corresponding to event A is timestamped. What amount of “wall clock” time will pass between A and B? (I think this is a reformulation of @Parv-Maheshwari ‘s last question).

Secondly, I would like to revisit @robots idea of using the TRIG\_OUT to match images to the “true capture” time. Did you ever implement this?

> I’d pairwise match the nth frame capture to the timestamp of the nth voltage change.

I assume this would be implemented by using the `grab()`call to increment a _frame counter_, which would then be matched against a _pulse counter_–\>_timestamp_ map (generated via ISR). This would assume that the number of frames can indeed be accurately tracked through the SDK. @Myzhar how would this interact with dropped frames? Is `getFrameDroppedCount()`an exact measure?

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [March 6, 2026, 7:05pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/14 "2026-03-06T19:05:56Z")

</div>

> [@Parv-Maheshwari](#):
>
> the image is timestampped at the moment it is captured (exposure time ends) but it is only avaible after 1-2 frmaes to be grabbed - essentially the timestamp is correct with repest to the image, and the overall frame (image + timestamp) is 1-2 frames stale/delayed

This is correct.

> [@andrwr\_rev](#):
>
> @Myzhar how would this interact with dropped frames? Is `getFrameDroppedCount()`an exact measure?

Yes, it is. A frame is dropped if the time distance between two consecutive frames is bigger than one frame period.

---

<div class="post-metadata">

**Author:** ![andrwr\_rev](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/a/e0b2c6/32.png) [@andrwr\_rev](https://community.stereolabs.com/u/andrwr_rev)\
**Post date:** [March 23, 2026, 11:34am UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/15 "2026-03-23T11:34:00Z")

</div>

Reposting what I wrote in an email to support @Myzhar .

My hardware platform is this: ZED X One GS, Carrier Mini, Orin NX 8GB, running at FHD resolution and 15 FPS. I need answers specific to this configuration.  
I have a navigation application where I need to match images against the pulses produced by the SYNC\_OUT port on the Carrier Mini.

The SDK API docs state that:

> When requesting the TIME\_REFERENCE::IMAGE ([https://www.stereolabs.com/docs/api/group\_\_Video\_\_group.html#ga9401e0c9b9fec46d2eb300ffd2fc72c9](https://www.stereolabs.com/docs/api/group __Video__ group.html#ga9401e0c9b9fec46d2eb300ffd2fc72c9)) timestamp, the UNIX nanosecond timestamp of the latest grabbed ([https://www.stereolabs.com/docs/api/classsl\_1\_1Camera.html#afa3678a18dd574e162977e97d7cbf67b](https://www.stereolabs.com/docs/api/classsl_1_1Camera.html#afa3678a18dd574e162977e97d7cbf67b)) image will be returned.  
> This value corresponds to the time at which the entire image was available in the PC memory. As such, it ignores the communication time that corresponds to 1 or 2 frame-time based on the fps (ex: 16.6ms to 33ms at 60fps).

I am confused by this and want to make sure I am not misinterpreting. Does the image timestamp correspond to the exposure time, or to the time at which the image is received at the deserializer?

Also, under the assumption that the timestamp corresponds to the deserializer reception:

- what determines whether the timestamp delay is one or two frames?
- Does it depend on resolution? Frame rate? Something else?
- Is it deterministic, in the sense that one set of settings will always produce a 1 frame delay, whereas another will always produce a 2 frame delay?
- Is the delay always either 1 OR 2 frames, or can it be anything in between?

Also regarding the “data transfer time” @Myzhar , what does this represent? The time from exposure to reception at the deserializer, or something else?

In our mail thread you also mentioned something about differences in how the ZED SDK works between USB and GMSL2 setups, can you elaborate?

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [April 2, 2026, 10:03am UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/16 "2026-04-02T10:03:41Z")

</div>

> [@andrwr\_rev](#):
>
> I am confused by this and want to make sure I am not misinterpreting. Does the image timestamp correspond to the exposure time, or to the time at which the image is received at the deserializer?

The image timestamps correspond to the time the image is received at the host, which is also (~us) the time the exposure ends.

> [@andrwr\_rev](#):
>
> Also, under the assumption that the timestamp corresponds to the deserializer reception:
> 
> - what determines whether the timestamp delay is one or two frames?
> - Does it depend on resolution? Frame rate? Something else?
> - Is it deterministic, in the sense that one set of settings will always produce a 1 frame delay, whereas another will always produce a 2 frame delay?
> - Is the delay always either 1 OR 2 frames, or can it be anything in between?

The delay is theoretically only 1 frame, but we are currently working on an issue to solve with SVGA and HD1080 resolution, where, randomly, the delay becomes 2 frames.

> [@andrwr\_rev](#):
>
> Also regarding the “data transfer time” @Myzhar , what does this represent? The time from exposure to reception at the deserializer, or something else?

The 1-frame delay is due to buffering from the ISP stack on the Jetson host.

> [@andrwr\_rev](#):
>
> In our mail thread you also mentioned something about differences in how the ZED SDK works between USB and GMSL2 setups, can you elaborate?

The USB3 cameras’ “delay” is caused by buffering internal to the USB3 controller driver.  
The GMSL2 cameras’ “delay” is caused by buffering internal to the ISP stack running on the Jetson.

---

<div class="post-metadata">

**Author:** ![andrwr\_rev](https://community.stereolabs.com/letter_avatar_proxy/v4/letter/a/e0b2c6/32.png) [@andrwr\_rev](https://community.stereolabs.com/u/andrwr_rev)\
**Post date:** [April 2, 2026, 3:43pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/17 "2026-04-02T15:43:09Z")

</div>

> The image timestamps correspond to the time the image is received at the host, which is also (~us) the time the exposure ends.

This is very good news to me and good to know, thanks.

> The delay is theoretically only 1 frame, but we are currently working on an issue to solve with SVGA and HD1080 resolution, where, randomly, the delay becomes 2 frames.

Does this mean that I can run HD1200 resolution on the ZED X One GS, and expect a consistent delay of one frame?

---

<div class="post-metadata">

**Author:** ![Myzhar](https://community.stereolabs.com/user_avatar/community.stereolabs.com/myzhar/32/11_2.png) [@Myzhar](https://community.stereolabs.com/u/Myzhar)\
**Post date:** [April 3, 2026, 10:11am UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/18 "2026-04-03T10:11:44Z")

</div>

> [@andrwr\_rev](#):
>
> Does this mean that I can run HD1200 resolution on the ZED X One GS, and expect a consistent delay of one frame?

This is the expected behavior.

---

<div class="post-metadata">

**Author:** ![Parv-Maheshwari](https://community.stereolabs.com/user_avatar/community.stereolabs.com/parv-maheshwari/32/5756_2.png) [@Parv-Maheshwari](https://community.stereolabs.com/u/Parv-Maheshwari)\
**Post date:** [August 3, 2026, 2:06am UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/19 "2026-08-03T02:06:00Z")

</div>

## ZED X SVO timestamps — end of exposure or host receive time?

Hi, following up on this thread with concrete measurements from a ZED X in **hardware-triggered slave mode at 30 Hz**.

### Setup

- ZED X (SN 40735594), slave mode, triggered by Teensy 4.1 (PTP-synced, 30 Hz)
- Recorded to SVO2 using [zed-ros2-wrapper](https://github.com/stereolabs/zed-ros2-wrapper) (SDK 5.2, Jetson AGX Orin)
- Trigger timestamps recorded via Jetson HTE (hardware timestamping engine)

### How we read the SVO timestamps

```python
import pyzed.sl as sl

cam = sl.Camera()
init = sl.InitParameters()
init.set_from_svo_file("zed.svo2")
init.svo_real_time_mode = False
init.depth_mode = sl.DEPTH_MODE.NONE
cam.open(init)

timestamps_ns = []
while True:
    err = cam.grab(sl.RuntimeParameters())
    if err == sl.ERROR_CODE.END_OF_SVOFILE_REACHED:
        break
    if err == sl.ERROR_CODE.SUCCESS:
        ts = cam.get_timestamp(sl.TIME_REFERENCE.IMAGE)
        timestamps_ns.append(ts.get_nanoseconds())
cam.close()

```

### Alignment to trigger

We embed a 13-bit sync pattern in the trigger signal (selectively dropping pulses) at the start and end of each recording. This lets us unambiguously match trigger pulses to camera frames without relying on clock synchronization. Results:

- 2 sync sequences detected, both at 100% confidence
- Zero dropped frames (3918 valid frames)
- Tick spans match exactly between trigger and ZED

### Result

After accounting for a small clock drift between the timestamping clocks (HTE vs SYSTEM\_CLOCK), the **constant offset between the SVO timestamp and the trigger edge is 31.76 ms** (~0.95 frame periods), with 340 us jitter.

This is very close to exactly **one frame period** (33.33 ms). This is consistent with the timestamp being assigned when the frame is **available on the host** (after GMSL transfer + ISP), not at **end of exposure** (which should align with the trigger rising edge to within ~15 us per the [slave mode docs](https://community.stereolabs.com/t/understanding-slave-mode-on-the-quad-capture-card/10777)).

### Question

Does `camera.get_timestamp(sl.TIME_REFERENCE.IMAGE)` return:

1. **End of exposure time** — i.e. when the sensor finished integrating, synchronized to the trigger edge, or
2. **Host receive time** — i.e. when the frame arrived on the Jetson after GMSL transfer and ISP processing (~1 frame later)?

Our measurement of 31.76 ms offset (nearly one frame period) suggests it is (2). If so, is there a way to get the actual exposure timestamp from the SVO, or should we subtract one frame period to approximate it?

### Reproduction

Files (SVO, trigger timestamps, extraction scripts, plots): [Google Drive](https://drive.google.com/open?id=1GjwI0fnLs5hrMFTrQfgzf68WNKRfkTjI)

---

<div class="post-metadata">

**Author:** ![Parv-Maheshwari](https://community.stereolabs.com/user_avatar/community.stereolabs.com/parv-maheshwari/32/5756_2.png) [@Parv-Maheshwari](https://community.stereolabs.com/u/Parv-Maheshwari)\
**Post date:** [November 6, 2026, 11:14pm UTC](https://community.stereolabs.com/t/zedx-timestamps/8924/20 "2026-11-06T23:14:13Z")

</div>

@Myzhar, could you please clarify my last post? We are working on time-syncing ZEDX with other cameras and modalities, and knowing both - the end of each camera’s exposure and the delay between a trigger/drop and the corresponding frame/drop is pivotal, since we use frame triggering/dropping across cameras to align them temporally. Thank you.

Also, I have a theory - Please tell me if this is correct or not

The image capture lags the trigger by 1 pulse. As you said before, the [trigger pulse rising edge syncs with the end of exposure for the image capture](https://community.stereolabs.com/t/understanding-slave-mode-on-the-quad-capture-card/10777/5). Let’s say we set the camera to receive a pulse at 30 Hz. For the first pulse we send, it cannot estimate when to start the exposure such that the end is synced. This means that the camera/SDK, based on the first pulse, estimates when the next pulse will arrive and then starts the exposure so that the end of the exposure syncs with the second pulse.

Let’s say we send a pulse of 1111010010011, then the camera images are \_111101001001 → basically delayed by 1 frame relative to the trigger. Is this correct ? If yes, then this explains why I was seeing a frame delay between the trigger and the corresponding image/drop, which means the delay is not coming from a wrong timestamp (i.e., ZEDX images contain the correct end-of-exposure time and not the timestamp post-frame buffering due to the ISP stack on the Jetson host)

[Next page](https://community.stereolabs.com/t/zedx-timestamps/8924.md?page=2)
