-
Notifications
You must be signed in to change notification settings - Fork 17
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
Equivalent pipeline gst-launch-1.0 #22
Comments
Hello, I am doing something similar as to what you wish to do. I could not get this program to completely work on my system but I was able to use the @joshdoe vision plugin. I can currently send two video streams with almost zero latency over UDP. The pipeline I am currently running for one camera is :
On the receiver PC, I am running this pipeline:
I hope this information helps! I am sure these pipelines will work on this program. This pipeline might work with the "parse" argument in the demopylongstreamer sample. Cheers, |
Hi, |
Firsly, congratulations for your work! :-)
I'm working on a Basler camera and I'm studiyng your code in order to better understand gstreamer. In particularly, I'm interested to understand what's the equivalent pipeline in order to send a video streaming from my Basler camera...
E.g. If the demopylongstreamer ask me to launch the following command on the terminal of the receiver PC:
gst-launch-1.0 udpsrc port=5000 ! application/x-rtp,encoding-name=H264,payload=96 ! rtph264depay ! avdec_h264 ! autovideosink sync=false async=false -e
If I wanted to experiment the equivalent command in order to launch a sender on the terminal:
gst-launch-1.0 appsrc ! videoconvert ! x264enc speed-preset=1 ! video/x-h264,stream-format=byte-stream ! rtph264pay ! udpsink host=127.0.0.1 port=5000 sync=false async=false
There's appsrc, because I'm writing a simple sender with C++ and OpenCV.
Is that comand correct? Because I tried it, but it doesn't work and the gstreamer documentation is gaunt... :-(
Thank your in advance for your response! :-)
The text was updated successfully, but these errors were encountered: