[gst-devel] udpsink issues

[Raseel Bhagat]

On Tue, Aug 24, 2010 at 4:39 AM, Tiago Katcipis <katcipis at inf.ufsc.br>wrote:

>
>
> On Mon, Aug 23, 2010 at 6:36 PM, Greg Wunder <gwunder at eoir.com> wrote:
>
>>  I've tested my end application with other sending apps ok.
>> I also do not see any data in Wireshark when testing.
>> If I send "ping" commands from the same machine, Wireshark sees these, but
>> the data in udpsink doesn't seem to be pushed out at all...
>>
>
> that is pretty odd... which version of gstreamer are you running and in
> which system? (udpsink can have some problems on windows, depending on the
> version of gstreamer that you are using)
>
> have you tried a identity before your udpsink just to be sure that data is
> flowing trough your pipe? (i must admit that given the simplicity of the
> pipe i don't know why it wouldn't go to play... but anything is possible
> :-)).
>
> you can try debugging with a --gst-debug=udpsink:5 or --gst-debug=5 to see
> if anything odd appears on the debug.
>
>
> http://www.gstreamer.net/data/doc/gstreamer/head/manual/html/section-checklist-debug.html
>
>
I agree, you should try after enabling debugging.
Usually setting the environment variable GST_DEBUG=*:3 suffices for me, cuz
5 gives way too much info for a first level debugging.

I had faced a similar issue some time ago.
In my case, I could see the following error/warning : "message size too
long" in the debug logs. As a result it was not able to send it on udp.
However,  my encoder had a fault and as soon as I fixed it, I could wrap the
correct RTP payload after encoding it and was able to send the packets out
correctly.

--
Raseel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20100824/905b5a92/attachment.htm>