GStreamer-devel

H264 RTP

Classic

List

Threaded

5 messages Options

Chuck Crisler

H264 RTP

I am working with plugin code that is supposed to be transmitting H264 video
via RTP. It uses the element rtph264pay. This code works in an earlier
version but fails in my 'new and improved' version. I have upgraded to
gstreamer 0.10.22 (not sure about the earlier version), good plugin 0.10.14
from 0.10.10 and base 0.10.22 from 0.10.21. A packet sniff shows that the
RTP is simply all wrong, even the RTP version, which is the first RTP byte.
Is there something that I should be doing to get the RTP header properly
generated, or should that 'just happen'?

TIA!
Chuck

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

Tim-Philipp Müller-2

Re: H264 RTP

On Thu, 2011-04-14 at 18:21 -0400, Chuck Crisler wrote:

> I am working with plugin code that is supposed to be transmitting H264 video
> via RTP. It uses the element rtph264pay. This code works in an earlier
> version but fails in my 'new and improved' version. I have upgraded to
> gstreamer 0.10.22 (not sure about the earlier version), good plugin 0.10.14
> from 0.10.10 and base 0.10.22 from 0.10.21. A packet sniff shows that the
> RTP is simply all wrong, even the RTP version, which is the first RTP byte.
> Is there something that I should be doing to get the RTP header properly
> generated, or should that 'just happen'?

Just to double-check: you're having a problem with rtph264pay which you
upgraded from an almost 3-year old version to a more than 2-year old
version?

Have you tried something slightly more recent, like the latest releases
for example?

Cheers
-Tim

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

Chuck Crisler

Re: H264 RTP

It is an embedded system and we don't quite have that freedom. :-(

----- Original Message -----
From: "Tim-Philipp Müller" <[hidden email]>
To: <[hidden email]>
Sent: Thursday, April 14, 2011 6:37 PM
Subject: Re: H264 RTP

> On Thu, 2011-04-14 at 18:21 -0400, Chuck Crisler wrote:
>
>> I am working with plugin code that is supposed to be transmitting H264
>> video
>> via RTP. It uses the element rtph264pay. This code works in an earlier
>> version but fails in my 'new and improved' version. I have upgraded to
>> gstreamer 0.10.22 (not sure about the earlier version), good plugin
>> 0.10.14
>> from 0.10.10 and base 0.10.22 from 0.10.21. A packet sniff shows that the
>> RTP is simply all wrong, even the RTP version, which is the first RTP
>> byte.
>> Is there something that I should be doing to get the RTP header properly
>> generated, or should that 'just happen'?
>
> Just to double-check: you're having a problem with rtph264pay which you
> upgraded from an almost 3-year old version to a more than 2-year old
> version?
>
> Have you tried something slightly more recent, like the latest releases
> for example?
>
> Cheers
> -Tim
>
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>

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

Chuck Crisler

Re: H264 RTP

OK, the RTP header values are set in the call to gst_basertppayload_push()
to push the buffer to the next element. The function uses the passed in
GstBaseRTPPayload * object. That object might be part of the derived object
that implements a GstStaticPadTemplate with some data. However, things like
the RTP version aren't set there.

Chuck
----- Original Message -----
From: "Chuck Crisler" <[hidden email]>
To: "Discussion of the development of and with GStreamer"
<[hidden email]>
Sent: Thursday, April 14, 2011 6:40 PM
Subject: Re: H264 RTP

It is an embedded system and we don't quite have that freedom. :-(

----- Original Message -----
From: "Tim-Philipp Müller" <[hidden email]>
To: <[hidden email]>
Sent: Thursday, April 14, 2011 6:37 PM
Subject: Re: H264 RTP

Chuck Crisler

Re: H264 RTP

I am confused by something in here. Data moves through a pipeline by
elements allocating buffers and pushing them through pads. If you have a
plugin element that works with a piece of hardware (say an H264 encoder), it
will generate buffers that it knows about. But the next element (the
rtph264pay element) receives a gstbasertppayload buffer directly in the
handle buffer function. Who allocates that input buffer and initializes the
fields?

Thank you.
----- Original Message -----
From: "Chuck Crisler" <[hidden email]>
To: "Discussion of the development of and with GStreamer"
<[hidden email]>
Sent: Thursday, April 14, 2011 6:57 PM
Subject: Re: H264 RTP

OK, the RTP header values are set in the call to gst_basertppayload_push()
to push the buffer to the next element. The function uses the passed in
GstBaseRTPPayload * object. That object might be part of the derived object
that implements a GstStaticPadTemplate with some data. However, things like
the RTP version aren't set there.

Chuck
----- Original Message -----
From: "Chuck Crisler" <[hidden email]>
To: "Discussion of the development of and with GStreamer"
<[hidden email]>
Sent: Thursday, April 14, 2011 6:40 PM
Subject: Re: H264 RTP

It is an embedded system and we don't quite have that freedom. :-(

----- Original Message -----
From: "Tim-Philipp Müller" <[hidden email]>
To: <[hidden email]>
Sent: Thursday, April 14, 2011 6:37 PM
Subject: Re: H264 RTP

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

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

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