-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Data 'looping' issue when simultaneously displaying RGB/Depth & Accel/Gyro Data Stream from recorded .bag files #6773
Comments
Hi @NickSadjoli Your description has characteristics similar to a previous Python D435i case, where the program was fine if enabling two of any combination of stream types (e.g depth / imu or rgb / depth), but timed out if all three stream types were enabled. The RealSense user in that case developed a solution in the end (a script at the bottom of the discussion) that still timed out when the camera first turned on but otherwise worked. |
Thank you very much for the reference to the issue, his code has indeed seem to have solved my issue as well. I'll be tidying up the code that worked for me, and provide them in an updated reply for this thread before closing the issue. Thanks again for the help @MartyG-RealSense ! |
Awesome news - thanks so much for the update and the solution sharing. :) |
Alright, as promised here is the code that has finally worked for me:
I'm especially highlighting the 2 different pipelines that need to be prepared to allow such streaming to happen. As not setting this up firsthand would lead to the 'Looping' issue that you see in the beginning of this thread:
This code now is able to stream and display the data from all channels (RGB/Depth images and IMU Accel/Gyro data) at the same time, as can be seen from this short video/GIF in this link. Hope this is useful for everyone with similar problem in the future! EDIT: Removed unnecessary piece of code block, as well as providing example link showing code successfully working now |
Issue Description
Hi, I'm currently trying to capture data using the RealSense camera to allow training/development of a Point-Cloud classifier for a Robotics platform in a university research. Hence, I'm studying how to extract and process data from the .bag files that are recorded using the RealSense Viewer tool.
The problem however - as summarized in the title - is that tuning the pipelines's config to capture and display both Image/Depth & IMU motion data (accel and gyro) stream at once seems to cause my custom tool to instead 'loop' within the first 5 seconds of the recording, which I've confirmed does not happen if I switch the config to display Image/Depth only. Here are the links for the short clips showcasing the normal playback (image/depth streams only) vs. the 'looping' playback that occurs once I try to display the recorded IMU data.
I've not yet tried to see whether a similar effect happens if I toggle IMU data stream only, however I'll try and update the results tomorrow.
In addition I'd like to note that on my machine attempting the same from a live camera stream, displaying of all data streams at once is possible only for a few seconds before the accel and gyro stream 'freezes' and doesn't update anymore. Could this issue be related somehow? I forgot to record this live streaming example, however I'll provide a similar video clip showcasing this issue once I've gotten back to the PC tomorrow.
For reference, here's the code loop that I'm currently using for both scenarios:
where this code block in particular:
is currently how I switch between toggling for all streams, vs only depth/color streams.
If additional information would be required, I'll gladly try and acquire them from the PC and upate this thread tomorrow.
EDIT: Accidentally sent comment too early before finishing the full message
The text was updated successfully, but these errors were encountered: