You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using arv_stream_pop_buffer a subsequent call to arv_buffer_get_timestamp returns a valid timestamp. But when using arv_stream_timeout_pop_buffer a subsequent call to arv_buffer_get_timestamp returns 0. Is this expected behavior or is it somehow device-specific?
Expected behavior
I expected a valid timestamp to be returned. Workaround is to use arv_buffer_get_system_timestamp if needed but would prefer to the buffer timestamp.
Camera description:
Manufacturer: Lucid Vision Labs
Model: Atlas10 ATX470S/M
Interface: GigE
Platform description:
Aravis version: 0.8.29
OS: macOS 14.3.1
Hardware: MacBook Pro M1
Additional context
N/A
The text was updated successfully, but these errors were encountered:
There is no reason the content of a buffer would be different using either function. They are one liner that either call g_async_queue_pop() or g_async_timeout_queue_pop().
Describe the bug
When using
arv_stream_pop_buffer
a subsequent call toarv_buffer_get_timestamp
returns a valid timestamp. But when usingarv_stream_timeout_pop_buffer
a subsequent call toarv_buffer_get_timestamp
returns0
. Is this expected behavior or is it somehow device-specific?To Reproduce
vs.
Expected behavior
I expected a valid timestamp to be returned. Workaround is to use
arv_buffer_get_system_timestamp
if needed but would prefer to the buffer timestamp.Camera description:
Platform description:
Additional context
N/A
The text was updated successfully, but these errors were encountered: