-
Notifications
You must be signed in to change notification settings - Fork 51
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
Gscam reports gst_uri_is_valid (uri)
error on startup, but video still works.
#1
Comments
Encountered the same problem, there is no solution? |
Unfortunately I haven't looked into it since it does not impact performance. Last I looked, it seemed like it might be a problem with the formatting of the pipeline string or a brief problem at initialization. |
I tried the jetson_csi_cam with the new xavier and e-consystems cuxvr130, but I also get the same error as mentioned above, and no rostopic is published. When running the gst-launch example: $ gst-launch-1.0 v4l2src device=/dev/video ! "video/x-raw, supplied from e-consystems, I can successfully view each of the 4 camera streams at /dev/video(0-3). when running: $ roslaunch jetson_csi_cam jetson_csi_cam.launch Any help would be much appreciated. |
I am running into this issue on a TX1 and from the logs it seems to be puking on a default calibration file.
I don't know where to find a default yaml file because I am trying to calibrate the camera right now :D |
I also got this error and didn't see any image topic. I solved it by replacing the definition of
It's basically |
Well, I cant really remember wether I found the reason for the error
message or not. However I got a setup working in the end using some other
gstreamer commands. I used jetson xavier, and 4 4k e-consystem cameras.
ons. 11. sep. 2019, 16:40 skrev Falko Schindler <[email protected]>:
… I also got this error and didn't see any image topic. I solved it by
replacing the definition of GSCAM_CONFIG in jetson_csi_cam.launch with
the following lines:
<env name="GSCAM_CONFIG" value="nvarguscamerasrc sensor-id=$(arg sensor_id) ! video/x-raw(memory:NVMM),
width=(int)$(arg width), height=(int)$(arg height), format=(string)I420, framerate=(fraction)$(arg fps)/1 !
nvvidconv flip-method=2 ! video/x-raw, format=(string)BGRx ! videoconvert" />
It's basically nvarguscamerasrc instead of nvcamerasrc and removing the
trailing video/x-raw, format=(string)BGR.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1?email_source=notifications&email_token=AK4MV57NCGWGZNJ5FXVIIBDQJD7NJA5CNFSM4DYCCBFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6OXCVQ#issuecomment-530411862>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AK4MV55HOWFPFSYIO5HTUJDQJD7NJANCNFSM4DYCCBFA>
.
|
I had success with the Jetson Nano and the Raspi Cam V2 using the following: |
|
You can Just make a standard yaml file for your camera. The yaml file is
essentially Just telling how the video stream is being scaled.
fre. 3. mai 2019, 03:16 skrev Seth King <[email protected]>:
… I am running into this issue on a TX1 and from the logs it seems to be
puking on a default calibration file.
[ INFO] [1556845282.545341291]: camera calibration URL: file:///root/.ros/camera_info/csi_cam_0.yaml
[ INFO] [1556845282.545543318]: Unable to open camera calibration file [/root/.ros/camera_info/csi_cam_0.yaml]
[ WARN] [1556845282.545596182]: Camera calibration file /root/.ros/camera_info/csi_cam_0.yaml not
found.
I don't know where to find a default yaml file because I am trying to
calibrate the camera right now :D
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AK4MV56YOKVHXUJGN5MHBTDPTOHANANCNFSM4DYCCBFA>
.
|
I am new to yaml language. it would be very helpul if you could just share your yaml file for camera |
I will just leave a example from our project on how we got it working with the e-consystems cameras. This code is based on the code from Peter Moran, and edited to work with our system.
As you see it asks for a camera calibration .ini file in which where the calibration parameters for the camera sits. Just make a ini file in one editor and paste the following( obviously you need to change so it fits your camera with regards to resolution, and the other parameters in the camera matrix) Ask me if you need explaination for the camera matrix Camera intrinsics[image] width height [default] camera matrix distortion rectification projection After you get the camera working, you can run a calibration routine and update the ini file to have a "calibrated" camera. |
For those working on ros melodic TX2, the correct command for the launch file is
|
@peter-moran env name="GSCAM_CONFIG" value="nvarguscamerasrc sensor-id=$(arg sensor_id) ! video/x-raw(memory:NVMM), width=(int)$(arg width), height=(int)$(arg height), format=(string)NV12, framerate=(fraction)$(arg fps)/1 ! nvvidconv flip-method=0 ! video/x-raw, format=(string)BGRx ! videoconvert" if you want add other functions you can read help file of gst-launch-1.0 |
No description provided. |
This worked well! Thank you so much. |
The
gscam
node reports a failure from GStreamer on startup for all launches. Specifically, if gives the following error.However, the lauch file remains fully functional and video still appears to work. It would be ideal to prevent this error even though everything seems functional.
The text was updated successfully, but these errors were encountered: