-
Notifications
You must be signed in to change notification settings - Fork 177
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
no image published with gscam #60
Comments
Did you ever get this resolved? |
nope. I finally skipped gscam and I am using now a ROS image topic to RTSP streaming service which works amazingly well: |
I was kinda experiencing the same issue. I was getting one image published, and then nothing. One day of debugging later and it turns out I need this PR to make it work... (It's a real shame nobody maintains this project) |
GSCAM2 has a very active maintainer, ended up just switching to ROS2 |
I've just faced with the similar problem that gscam publish nothing. I investigated it a bit and look likes that gscam doesn't support dynamically created pads. gscam parses the part of the pipeline passed as environment variable: pipeline_ = gst_parse_launch(gsconfig_.c_str(), &error); and if some pads are dynamic, it couldn't be lined, but gscam continue working, but nothing is published. In my case the problem was in the |
I am trying to set up gscam on my Jetson TX2 with Jetpack 4.2.2 under Ubuntu 18.04. Streaming with gstreamer works perfectly well, but with gscam I receive no image feed. No errors are issued. I do have gscam installed in the following way:
Running the following pipeline with gstreamer works well:
gst-launch-1.0 v4l2src device=/dev/video0 ! video/x-raw, width=3840, height=1080 ! videocrop top=0 left=0 right=1920 bottom=0 ! tee name=t ! queue ! videoconvert ! omxh264enc ! video/x-h264, stream-format=byte-stream ! h264parse ! rtph264pay config-interval=1 ! udpsink host=10.0.1.111 port=5600 t. ! queue ! videoconvert
However when I try the same with gscam no image is published and the process hangs (control C doesent work, I need to kill it)
I traced the messages with GST_DEBUG=4, no errors are occuring, here is the tail of the log:
The text was updated successfully, but these errors were encountered: