rtsp h264 problem

[Sergio Basurco]

Hi again,

It seems the issue comes from somewhere else. I'm reopening this on a 
different thread as it seems unrelated to PT or  the initial post.

Thanks!

El 06-Mar-15 a las 10:03 AM, Sergio Basurco escribió:
> Hi Marc,
>
> Sorry I took so long to reply, here's the output with debug=9 on rtspsrc.
>
> $ gst-launch-1.0.exe --gst-debug-level=rtspsrc:9 rtspsrc 
> location="rtsp://192.168.1.189/rtsp_tunnel?h26x=4&line=1&inst=2" 
> latency=1000 ! rtph264depay ! avdec_h264 ! autovideosink
>
> Setting pipeline to PAUSED ...
> Pipeline is live and does not need PREROLL ...
> Progress: (open) Opening Stream
> Progress: (connect) Connecting to 
> rtsp://192.168.1.189/rtsp_tunnel?h26x=4&line=1
> &inst=2
> Progress: (open) Retrieving server options
> Progress: (open) Retrieving media info
> Progress: (request) SETUP stream 0
> Progress: (open) Opened Stream
> Setting pipeline to PLAYING ...
> New clock: GstSystemClock
> Progress: (request) Sending PLAY request
> Progress: (request) Sending PLAY request
> Progress: (request) Sent PLAY request
> ERROR: from element 
> /GstPipeline:pipeline0/GstRTSPSrc:rtspsrc0/GstUDPSrc:udpsrc1
> : Could not read from resource.
> Additional debug info:
> gstudpsrc.c(548): gst_udpsrc_create (): 
> /GstPipeline:pipeline0/GstRTSPSrc:rtspsr
> c0/GstUDPSrc:udpsrc1:
> get available bytes failed
> Execution ended after 0:00:00.003091305
> Setting pipeline to PAUSED ...
> Setting pipeline to READY ...
> Setting pipeline to NULL ...
> Freeing pipeline ...
>
>
> Cheers!
>
>
> El 26-Feb-15 a las 9:26 AM, Marc Leeman escribió:
>> First of all, I don't think you need to use the short header: the
>> short-header is typically used for cameras that are based on some crappy
>> software stack that does not understand complete RTSP negociation.
>>
>> Secondly, can you post the output of the command line with the debug=1
>> set on the rtspsrc elemeent. That will get some clarity as to what the
>> camera is claiming to send.
>>
>>
>>
>> On Wed Feb 25 2015 at 5:41:10 PM Sergio Basurco
>> <sergio.b at coherentsynchro.com <mailto:sergio.b at coherentsynchro.com>> 
>> wrote:
>>
>>     Hello there,
>>
>>     I'm still unable to make 1.4.4 work with Bosch cameras due to the PT
>>     value. How can I check that encoding-name matches?
>>
>>     Best!
>>
>>     El 18-Feb-15 a las 11:42 AM, Sergio Basurco escribió:
>>      > Hi Tim,
>>      >
>>      > I'm on 1.4.4. What does it mean for the encoding-name to match?
>>     Here's
>>      > the pipeline:
>>      >
>>      > rtspsrc location=rtsp://{...} short-header=TRUE ! rtph264depay !
>>      > avdec_h264 ! autovideosink
>>      >
>>      > Best,
>>      >
>>      > El 18-Feb-15 a las 11:39 AM, Tim Müller escribió:
>>      >> On Wed, 2015-02-18 at 01:58 -0800, sergio_cs wrote:
>>      >>
>>      >> Hi Sergio,
>>      >>
>>      >>> I know this is an old post but it's the exact same issue. Is it
>>      >>> possible to
>>      >>> remove the PT in the rtph264depay element usign gst-launch?
>>      >>>
>>      >>> Or do I have to modify it from source?
>>      >>
>>      >> What version are you using? I think this got fixed a while 
>> back, and
>>      >> current versions (1.4 / git master) will accept any pt as long
>>     as the
>>      >> encoding-name matches?
>>      >>
>>      >> Cheers
>>      >>   -Tim
>>      >>
>>      >
>>
>>     --
>>     Sergio Basurco,
>>     Coherent Synchro
>>     _________________________________________________
>>     gstreamer-devel mailing list
>>     gstreamer-devel at lists.__freedesktop.org
>>     <mailto:gstreamer-devel at lists.freedesktop.org>
>> http://lists.freedesktop.org/__mailman/listinfo/gstreamer-__devel
>> <http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel>
>>
>>
>>
>> _______________________________________________
>> gstreamer-devel mailing list
>> gstreamer-devel at lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>>
>

-- 
Sergio Basurco,
Coherent Synchro