We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am trying these simple test commands
gst-launch-1.0 videotestsrc ! video/x-raw,width=352,height=288,framerate=15/1 ! videoconvert ! x264enc ! rtph264pay name=pay0 pt=96
gst-launch-1.0 videotestsrc ! video/x-raw,width=352,height=288,framerate=15/1 ! videoconvert ! avenc_mpeg4 ! rtpmp4vpay name=pay0 pt=96
Both should play the stream over rtsp protocol, but I am getting this error :
rtsp
mendel@queen-dog:~$ gst-launch-1.0 videotestsrc ! video/x-raw,width=352,height=288,framerate=15/1 ! videoconvert ! x264enc ! rtph264pay name=pay0 pt=96 Setting pipeline to PAUSED ... Pipeline is PREROLLED ... Setting pipeline to PLAYING ... New clock: GstSystemClock Redistribute latency... ERROR: from element /GstPipeline:pipeline0/GstVideoTestSrc:videotestsrc0: Internal data stream error. Additional debug info: gstbasesrc.c(3055): gst_base_src_loop (): /GstPipeline:pipeline0/GstVideoTestSrc:videotestsrc0: streaming stopped, reason not-linked (-1) Execution ended after 0:00:00.269623910 Setting pipeline to PAUSED ... Setting pipeline to READY ... Setting pipeline to NULL ... Freeing pipeline ...
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I am trying these simple test commands
gst-launch-1.0 videotestsrc ! video/x-raw,width=352,height=288,framerate=15/1 ! videoconvert ! x264enc ! rtph264pay name=pay0 pt=96
gst-launch-1.0 videotestsrc ! video/x-raw,width=352,height=288,framerate=15/1 ! videoconvert ! avenc_mpeg4 ! rtpmp4vpay name=pay0 pt=96
Both should play the stream over
rtsp
protocol, but I am getting this error :The text was updated successfully, but these errors were encountered: