TDA4VEN-Q1: capture buffer timestamp

WenBo Ding

Part Number: TDA4VEN-Q1

Tool/software:

Hi,

In sdk10.0, when I check the timestamps of all capture buffers when they are dequeued or enqueued, there are a total of four buffers, among which only one buffer has a timestamp, while the timestamps of the other three buffers are all 0. This issue does not exist on sdk9.2. Could you tell me what causes this?

Regards,

Wenbo

5 months ago

0 Gokul S 5 months ago

TI__Genius 13420 points

Hi Wenbo,

Can you describe how your are checking the timestamps of the capture buffers ? are you printing the value from the target kernel or the fvid2_driver ?

Regards,
Gokul

0 WenBo Ding 5 months ago in reply to Gokul S

Prodigy 80 points

Hi Gokul,

I added printing in the app_multi_cam demo to view the timestamp.As shown below.

vxGetObjectArrayTimeStamp is a custom function, implementation is as follows:

The printing effect is as follows,The printing effect of sdk9.2 and sdk10.0 is the same, with only one buffer having a timestamp.

The problem I mentioned first is that I got it wrong. The phenomena of the two sdk versions are the same.

Regards,

Wenbo

0 Gokul S 5 months ago in reply to WenBo Ding

TI__Genius 13420 points

Hi Wenbo,

This is normal as only the reference you dequeued will have the timestamp, the framework sets the timestamp to 0 before calling the process_callback function of capture node. When the timestamps are 0 which means the buffers are being processed and not yet updated with the new frame. Once the buffer is updated with the data the timestamp is updated to the obj_array reference.

Regards,
Gokul

0 WenBo Ding 5 months ago in reply to Gokul S

Prodigy 80 points

Hi Gokul,

Thank you. I understand now.

Regards,

Wenbo

Processors

Processors forum

TDA4VEN-Q1: capture buffer timestamp