search

WKDSMRT / realsense-gstreamer

GStreamer source plugin for the Intel RealSense line of cameras
GNU Lesser General Public License v3.0
30 stars 13 forks source link

RealSense error calling rs2_get_frame_metadata (frame:0x55bb489ba208, frame_metadata:Actual Exposure) #19

Open sandeshk1 opened 3 years ago

sandeshk1 commented 3 years ago

RealSense Camera Model: D435i

$ gst-launch-1.0 realsensesrc ! videoconvert ! autovideosink Setting pipeline to PAUSED ... Pipeline is live and does not need PREROLL ... Setting pipeline to PLAYING ... New clock: GstSystemClock ERROR: from element /GstPipeline:pipeline0/GstRealsenseSrc:realsensesrc0: RealSense error calling rs2_get_frame_metadata (frame:0x55a4117a2cf8, frame_metadata:Actual Exposure) Additional debug info: ../src/gstrealsensesrc.cpp(348): gst_realsense_src_create (): /GstPipeline:pipeline0/GstRealsenseSrc:realsensesrc0 Execution ended after 0:00:00.003126435 Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... Freeing pipeline ...

TimConnelly commented 3 years ago

Hi, can you try this branch? https://github.com/WKDSMRT/realsense-gstreamer/tree/bugfix-pipeline-start-error

Getting the actual exposure is set to 0 on that branch to avoid the error. I'll see if I can find a fix.

sandeshk1 commented 3 years ago

Hi,

Thanks for the quick reply.

I am facing the same error in the bugfix-pipeline-state-error branch as well.

Is there any way I can unblock from this issue.

sandeshk1 commented 3 years ago

Hi, sry there was an error while pulling the bugfix branch. I see that you have commented the part where actual exposure is read from realsense camera to unblock this issue. So bugfix branch is unblocking this issue.

Can you please try to provide a fix for this

TimConnelly commented 3 years ago

Yes. I'll look into it. Do you need the exposure value for your application?

sandeshk1 commented 3 years ago

Thanks for looking into it. It would be great to have a property to set the exposure value for the real sense camera .

TimConnelly commented 3 years ago

@sandeshk1 Can you pull and try the bugfix-pipeline-start-error branch? Getting the exposure is working for me now. If it works for you then I'll move on to looking at adding an exposure property.

sandeshk1 commented 3 years ago

I am still getting the same error in the https://github.com/WKDSMRT/realsense-gstreamer/tree/bugfix-pipeline-start-error branch

TimConnelly commented 3 years ago

Can you check which version of librealsense2 you're using with apt list | grep realsense? The error stopped occurring on my end when I installed the latest version of librealsense2 (2.41.0).

librealsense2-dev/focal,now 2.41.0-0~realsense0.3963 amd64 [installed]

PCH10507323 commented 3 years ago

Hi, follow the previous commits, I build the source with this branch

Hi, can you try this branch? https://github.com/WKDSMRT/realsense-gstreamer/tree/bugfix-pipeline-start-error

Getting the actual exposure is set to 0 on that branch to avoid the error. I'll see if I can find a fix.

Also, I installed libgstreamer-plugins-base1.0-dev and my librealsense2 version is 2.41.0 But I still have this error

RealSense error calling rs2_get_frame_metadata (frame:0x55a4117a2cf8, frame_metadata:Actual Exposure)

Is there any part I miss to setup? Thanks

sandeshk1 commented 3 years ago

@TimConnelly I had installed realsense v2.41.0 from source(https://github.com/IntelRealSense/librealsense) and still faced the exposure issue.

I had to comment the line where exposure metadata is being read to get it working

TimConnelly commented 3 years ago

@sandeshk1 I'm no longer able to reproduce the error on my end. Can you send the output of gst-inspect-1.0 realsensesrc and the pipeline error.

Also, which specific OS, including version, are you developing on?

TimConnelly commented 3 years ago

@sandeshk1 Are you still experiencing this problem?

I was able to replicate the error on my old system that had version 2.39.0 of librealsense. I upgraded to version 2.41.0 (following the instructions here) and the error resolved.

When you installed from source, which options did you give to Cmake? From the comment on this realsense issue the FORCE_RSUSB_BACKEND option can affect performance.

mcaniot commented 2 years ago

I have the same issue using realsense version 2.50. I already tried the bug-fixed branch without any success.