Generate error when the rtp payload data is not mulaw audio

[Rohan0993]

Hi all,

I have made this pipeline which is sending RTP packets to a local port

*gst-launch-1.0 filesrc location=/path/to/TestSrc.wav ! wavparse !
audioconvert ! audio/x-raw,channels=1,rate=44100 ! rtpL16pay  ! udpsink
host=192.168.xxx.xxx port=5000*

The file (TestSrc.wav) is Linear16 PCM encode @44100 Hz sampling rate.

my receiver pipeline is:

*gst-launch-1.0 udpsrc port=5000 ! "application/x-rtp,media=(string)audio,
clock-rate=(int)8000, encoding-name=(string)PCMU, channels=(int)1,
payload=(int)96" ! rtppcmudepay ! filesink
location=/path/to/Testoutput.ulaw*

This receiver pipeline is assuming that the input RTP packets have the data
as mu-law encoded PCM @ 8000Hz.

NOW
I don't want to edit any of the pipelines to change their functionality. I
mean I want the sender to send linear 16 encoded data via RTP and I want the
listener to expect mu-law encoded data in RTP.

I just want to produce an error message(s) that the received data is not
PCM-MU. It will be great if I can find out whether encoding is wrong or the
sampling rate is wrong or both are wrong.

*How can I do that?*




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

[Sebastian Dröge-3]

On Mon, 2019-04-08 at 01:43 -0500, Rohan0993 wrote:
>
> I just want to produce an error message(s) that the received data is
> not PCM-MU. It will be great if I can find out whether encoding is
> wrong or the sampling rate is wrong or both are wrong.
>
> *How can I do that?*

You can't as this information is not included in the RTP packets
themselves. For statically assigned payload types (< 96) you could
detect a wrong format based on that, but for dynamic payload types (and
mismatching sampling rate) there's nothing you can really do.

--
Sebastian Dröge, Centricular Ltd · https://www.centricular.com


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

[Rohan0993]

Sebastian Dröge-3 wrote
> For statically assigned payload types (< 96) you could
> detect a wrong format based on that

Thanks for the reply,

how can I do that? I have tried changing the payload type to 0 (for Mulaw)
at my receiving pipeline. But it didn't work The pipelines simply worked and
depayloaded garbage data in the filesink file.



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

[Sebastian Dröge-3]

On Tue, 2019-04-09 at 04:07 -0500, Rohan0993 wrote:
> Sebastian Dröge-3 wrote
> > For statically assigned payload types (< 96) you could
> > detect a wrong format based on that
>
> Thanks for the reply,
>
> how can I do that? I have tried changing the payload type to 0 (for Mulaw)
> at my receiving pipeline. But it didn't work The pipelines simply worked and
> depayloaded garbage data in the filesink file.

You need to add code somewhere that checks for the payload type field.
The depayloaders don't care about it.

You could for example add something in a pad probe before the
depayloader.

--
Sebastian Dröge, Centricular Ltd · https://www.centricular.com


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

[Rohan0993]

Sebastian Dröge-3 wrote
> add something in a pad probe before the depayloader.

Can you share an example I didn't understand how?

Rohan



--
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 mardi 09 avril 2019 à 12:25 +0300, Sebastian Dröge a écrit :

> On Tue, 2019-04-09 at 04:07 -0500, Rohan0993 wrote:
> > Sebastian Dröge-3 wrote
> > > For statically assigned payload types (< 96) you could
> > > detect a wrong format based on that
> >
> > Thanks for the reply,
> >
> > how can I do that? I have tried changing the payload type to 0 (for Mulaw)
> > at my receiving pipeline. But it didn't work The pipelines simply worked and
> > depayloaded garbage data in the filesink file.
>
> You need to add code somewhere that checks for the payload type field.
> The depayloaders don't care about it.

We could add a check in the base class to check that the PT in the
packet matches the provided caps if it's not already the case. That
will only improve strictness for static PT of course, might raise
issues in your template too (which would be nice).

>
> You could for example add something in a pad probe before the
> depayloader.
>
> _______________________________________________
> 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