-
Notifications
You must be signed in to change notification settings - Fork 34
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
Not able to launch pipeline_node #56
Comments
Your logs look normal right up until the error. |
Intel(R) Xeon(R) E-2278GE CPU And I kept only audio_test as part of simple_bins, and removed rest others including webrtc_example_bin section |
That does narrow it down a lot. Does the audio_test pipeline work on its own through gst-launch?
|
I tested with one of the working pipeline |
Hi,
Not able to launch the gst pipeline node with launch file, could you please share some example for the same.
~/workspaces/gstreamer_ws$ ros2 launch gst_bridge example.launch.py
[INFO] [launch]: All log files can be found below /home/avlabs/.ros/log/2023-03-24-05-21-48-934184-nuvo-one-234474
[INFO] [launch]: Default logging verbosity is set to INFO
[INFO] [pipeline_node-1]: process started with pid [234475]
[pipeline_node-1] [DEBUG] [1679615509.086904536] [rcl]: Initializing node 'pipeline_node' in namespace ''
[pipeline_node-1] [DEBUG] [1679615509.086944619] [rcl]: Using domain ID of '0'
[ERROR] [pipeline_node-1]: process has died [pid 234475, exit code -11, cmd '/home/avlabs/workspaces/gstreamer_ws/install/gst_pipeline/lib/gst_pipeline/pipeline_node --ros-args --log-level debug --ros-args -r __node:=gst_pipeline_node --params-file /home/avlabs/workspaces/gstreamer_ws/install/gst_bridge/share/gst_bridge/config/example.config.yaml'].
Thanks in Advance
The text was updated successfully, but these errors were encountered: