-
Notifications
You must be signed in to change notification settings - Fork 14
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
ERROR: from element /GstPipeline:pipeline0/GstRealsenseSrc:realsensesrc0: RealSense error calling rs2_pipeline_start_with_config (pipe:0x20aa540, config:0x208f9e0) #14
Comments
Which model camera do you have? Looks like something is wrong with the configuration passed to the Realsense code. The build/install output looks fine. Try setting the properties when using gst-launch, for example: Thank you for being patient working through these issues! |
Hello, I am using intel realsense T265. is this a tested model? I will be switching to D435i when it arrives. I tried the command you suggested and got the following error:
Thank you for creating this and helping me solve the issues! |
We have not tested with the T265. It looks like the T series outputs different stream types than the D series. It shouldn't be too difficult to update the code for T series, but maybe a bit hard to test. It's just a matter of enabling the streams, setting the CAPs as appropriate, and supporting the streams with the mux/demux code. |
Got it. Thanks for the update. So I'll probably test it when my D435i arrives. Thank you very much. |
I have a similar problem with my D415, maybe you can help me too? )) There are some my logs: gst-launch-1.0 -v -m realsensesrc stream-type=2 align=0 imu_on=false ! videoconvert ! autovideosink |
@chezh The D415 does not have an IMU, correct? If that's the case the fix should be straightforward. |
@TimConnelly I'm not sure that it is about IMU. I tried to set IMU off and had the same result. I noticed that list of plugin formats (RS_to_Gst_Video_Format()) does not match with my D415 output format list. Could it be a reason? P.S. Now tried on D435, got the same result |
@chezh What platform are you on? We've tested mostly on Ubuntu 18.04. What formats does the D415 put out that aren't listed in the format conversion function? It seems there were some breaking changes from librealsense at some point. Can you tell me the version of librealsense you have installed? ( Try this branch and let me know if it helps. https://github.com/WKDSMRT/realsense-gstreamer/tree/bugfix-pipeline-start-error |
@TimConnelly this is exactly what i needed! Thanks for help) |
Hi, I have the same issue, I am using Raspberry Pi with Raspbian, the realsense model is T265 detailed output: Got message #47 from element "realsensesrc0" (error): GstMessageError, gerror=(GError)NULL, debug=(string)"../src/gstrealsensesrc.cpp(589):\ gst_realsense_src_start\ ():\ /GstPipeline:pipeline0/GstRealsenseSrc:realsensesrc0"; I tried to re-install the bug-fix branch, but it didn't help me( |
Hi, I do also have the same issue. I am using a Lattepanda with Realsense D435 without IMU on Ubuntu 20. I need to use the Bugfix-Pipeline-Start-Error branch. When I try: gst-launch-1.0 realsensesrc stream-type=0 align=0 imu_on=false ! videoconvert ! autovideosink The Output is: Setting pipeline to PAUSED ... Any ideas? |
I got this error when executing the command:
gst-launch-1.0 -v -m realsensesrc ! videoconvert ! autovideosink
I should also mentioned that when executing
sudo ninja -C build install
, the output is the following and I suspect it didnt build successfully :The gst-inspect command output seems correct tho.
The full error message can be found here:
The text was updated successfully, but these errors were encountered: