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
When we are trying to render a second video, we are creating a new system object and also just the be safe, we are also calling request_reset() but the reset is only called after the first frame is created (during feed_frame)
The issue is that data::frame::next_id_ was not reset to 0 before de creation of the first frame in create_monocular_frame
we are manually resetting it, but I would suggest maybe adding something to reset the value during the system constructor?
Thank you
Tim
The text was updated successfully, but these errors were encountered:
Essentially, data::frame::next_id_ designed to be static seems to obscure handling of initialization and destruction. I'll see if I can move it to system::next_id_. Thanks for the report.
we can reset next_frame_id_ to 0 by destroying system.
In addition, reset() will not set next_frame_id_ to 0 after this change. I removed this feature because I thought it was unnecessary and confusing, but if you need it, please let me know.
When we are trying to render a second video, we are creating a new system object and also just the be safe, we are also calling
request_reset()
but the reset is only called after the first frame is created (duringfeed_frame
)The issue is that
data::frame::next_id_
was not reset to 0 before de creation of the first frame increate_monocular_frame
we are manually resetting it, but I would suggest maybe adding something to reset the value during the system constructor?
Thank you
Tim
The text was updated successfully, but these errors were encountered: