Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

duplicate frame numbers in rosbag #2214

Closed
marcovs opened this issue Aug 8, 2018 · 5 comments
Closed

duplicate frame numbers in rosbag #2214

marcovs opened this issue Aug 8, 2018 · 5 comments
Assignees
Labels

Comments

@marcovs
Copy link

marcovs commented Aug 8, 2018

Required Info
Camera Model D415
Firmware Version 05.09.09.02
Operating System & Version MacOS
Kernel Version (Linux Only)
Platform Mac
SDK Version 2.11.0
Language C++
Segment AR

From the output of the rosbag viewer, I noticed that sometimes consecutive frames are recorded with the same frame number. The timestamp and the frame contents are different, but the frame number is the same. The issue does not bother me, but I thought to flag it just in case it was not documented.

@dorodnic
Copy link
Contributor

dorodnic commented Aug 8, 2018

Hi @marcovs
Same frame number with different timestamp is not a valid behavior IMHO, we will try to reproduce and fix.
Any specific steps you can share for obtaining such rosbag?

@dorodnic dorodnic added the bug label Aug 8, 2018
@marcovs
Copy link
Author

marcovs commented Aug 9, 2018

Did not doing anything different than usual, captured the rosbag with only rgb and depth streams, no infrared at 30fps with a resolution of 1280x720. I am wondering whether the fact that I am connecting the realsense through a usb hub to the macbook pro is what is causing the issue

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
hi @marcovs,

i see you are using libRealsense v2.11.0, which is kind of old now, would like to know if this can be reproduced with last release?
and how you record the bag file? via realsense viewer?
thanks.

@dorodnic
Copy link
Contributor

Should be resolved in v2.16.1

@RealSense-Customer-Engineering
Copy link
Collaborator

[Realsense Customer Engineering Team Comment]
Hi @marcovs,

How about the test result based on v2.16.1?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants