Gstreamer Pipeline sometimes doesn't work and sometimes does.

[rhythm87]

In following gstreamer pipeline, I'm receiving h264 encoded rtp packtes at
port 8000, and the using a tee displaying the stream and forwarding the same
packets to another port 6000.

gst-launch-1.0 udpsrc port=8000 caps="application/x-rtp,
media=(string)video, encoding-name=(string)H264" ! tee name=t ! queue !
rtph264depay ! decodebin ! videoconvert ! autovideosink t. ! queue ! udpsink
host=0.0.0.0 port=6000

The stream at port 8000 is continuous and works fine with this pipeline:
gst-launch-1.0 udpsrc port=8000 caps="application/x-rtp,
media=(string)video, encoding-name=(string)H264" ! rtph264depay ! decodebin
! videoconvert ! autovideosink

But, the first pipeline sometimes work and mostly not.
I can't figure out what could be wrong. Is it something I'm missing at
udpsrc , like clock configuration , which sometimes get synced or something,
making the pipeline work. If that is the case, please suggest how to get
around with this.

Regards,
Rhythm



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Dimitrios Katsaros]

You can check the rtp caps on the broadcast pipeline if you are using gst-launch with the -v flag. That should give you the rtp info you are looking for. Also try to print out the fialing pipeline debug info by using --gst-debug. you can start with --gst-debug=*:3 to get some info if there is any available and then further explore the problematic element.

Also, what do you mean that the pipeline does't work? Is it producing broken results or none at all? If you are getting no results, does starting up the consumer pipe before the producer, does it work normally? An important detail with h264 streams is that you need a key frame to start streaming so make sure that the encoder is producing key-frames on reasonable intervals.

On Fri, Mar 16, 2018 at 6:21 PM, rhythm87 <[hidden email]> wrote:

In following gstreamer pipeline, I'm receiving h264 encoded rtp packtes at
port 8000, and the using a tee displaying the stream and forwarding the same
packets to another port 6000.

gst-launch-1.0 udpsrc port=8000 caps="application/x-rtp,
media=(string)video, encoding-name=(string)H264" ! tee name=t ! queue !
rtph264depay ! decodebin ! videoconvert ! autovideosink t. ! queue ! udpsink
host=0.0.0.0 port=6000

The stream at port 8000 is continuous and works fine with this pipeline:
gst-launch-1.0 udpsrc port=8000 caps="application/x-rtp,
media=(string)video, encoding-name=(string)H264" ! rtph264depay ! decodebin
! videoconvert ! autovideosink

But, the first pipeline sometimes work and mostly not.
I can't figure out what could be wrong. Is it something I'm missing at
udpsrc , like clock configuration , which sometimes get synced or something,
making the pipeline work. If that is the case, please suggest how to get
around with this.

Regards,
Rhythm



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[rhythm87]

The pipeline produces no results at all. No frames received and no log when
-v is used.
And yes, as you said if consumer pipeline is started before the producer
pipeline, it works always. Is it unusual or what?

Can you explain why it is happening?

Regards,
Rhythm



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Nicolas Dufresne-5]

Le lundi 19 mars 2018 à 02:03 -0700, rhythm87 a écrit :
> The pipeline produces no results at all. No frames received and no
> log when
> -v is used.
> And yes, as you said if consumer pipeline is started before the
> producer
> pipeline, it works always. Is it unusual or what?
>
> Can you explain why it is happening?

Sure, what difficulties are you facing ?

>
> Regards,
> Rhythm
>
>
>
> --
> Sent from: http://gstreamer-devel.966125.n4.nabble.com/
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[Nicolas Dufresne-5]

Le lundi 19 mars 2018 à 02:03 -0700, rhythm87 a écrit :
> The pipeline produces no results at all. No frames received and no
> log when
> -v is used.
> And yes, as you said if consumer pipeline is started before the
> producer
> pipeline, it works always. Is it unusual or what?

Logs are enabled with environment GST_DEBUG="<cat>:<N>,...,<M>" where N
is the log level, the larger the more traces, and M is the default log
level for all categories.

Nicolas

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel

[rhythm87]

Okay, I'll check it. But do you have any idea why is it happening?
Because, otherwise both the pipelines work perfectly with same src. It only
happens when I use tee to join them?

And also the special case I mentioned above. If consumer pipeline is running
prior to producer, then there is no error or unusual behaviour.

Regards,
Rhythm



--
Sent from: http://gstreamer-devel.966125.n4.nabble.com/
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel