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
I'm currently working on a project that involves capturing video from an RViz instance in ROS2 Galactic. I have two potential approaches in mind, and I'm seeking guidance on which one to pursue or if there are alternative methods:
Connecting to RViz: Is there a recommended way to develop a ROS2 node to connect to a specific RViz instance and capture its video feed?
Accessing RViz's "File -> Save Image" Function: after connecting to a specific RViz, is it possible to access RViz's "File -> Save Image" functionality programmatically to capture images and then compile them into a video?
Creating a Custom Plugin: Should I create a custom RViz plugin to facilitate video capture directly within RViz?
I'd greatly appreciate any insights or recommendations regarding the best approach to achieve this video capture functionality within ROS2 Galactic. Thank you!
The text was updated successfully, but these errors were encountered:
I'm currently working on a project that involves capturing video from an RViz instance in ROS2 Galactic. I have two potential approaches in mind, and I'm seeking guidance on which one to pursue or if there are alternative methods:
Connecting to RViz: Is there a recommended way to develop a ROS2 node to connect to a specific RViz instance and capture its video feed?
Accessing RViz's "File -> Save Image" Function: after connecting to a specific RViz, is it possible to access RViz's "File -> Save Image" functionality programmatically to capture images and then compile them into a video?
Creating a Custom Plugin: Should I create a custom RViz plugin to facilitate video capture directly within RViz?
I'd greatly appreciate any insights or recommendations regarding the best approach to achieve this video capture functionality within ROS2 Galactic. Thank you!
The text was updated successfully, but these errors were encountered: