TDA4VM: VISS output dequeue intervals are too short?

Tool/software:

This thread is derived from the following thread:
https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1521521/tda4vm-is-it-possible-to-access-viss-output-image-memory-without-openvx-node/

Hi Gokul,

I actually tried memory access method using map and printed a log after the map.

The log prints timestamp in ms, frame ID, and memory address after mapping.

Then I noticed something strange. Sometimes the time until the next frame ID is very short. Why is this? If the camera is at 30fps, there should be an interval of about 34ms.

[timestamp] [id]              memory address
...
[175880] [10] viss_image[0] = 0x9B71F000
[175985] [11] viss_image[0] = 0xA4012000
[175986] [12] viss_image[0] = 0x9AAF7000
[176019] [13] viss_image[0] = 0x99ECF000
[176049] [14] viss_image[0] = 0x9B71F000
[176084] [15] viss_image[0] = 0xA4012000
[176128] [16] viss_image[0] = 0x99ECF000
[176165] [17] viss_image[0] = 0x9AAF7000
[176199] [18] viss_image[0] = 0x9B71F000
[176236] [19] viss_image[0] = 0xA4012000
[176298] [20] viss_image[0] = 0x99ECF000
[176298] [21] viss_image[0] = 0x9AAF7000
[176330] [22] viss_image[0] = 0x9B71F000
...

ex) Only 1 ms between frames 11 and 12.

Regards,
Daigo