[Live-devel] x264 Video Stream Stops

[Constantin Savtchenko]

Hey Ross,

  Thank you for the quick response.

  Yes I meant h264, but I think I put it together with the x264 encoder in
my mind while I wrote the email... It has been a long day.

  The stream is coming from a gstreamer server, written by a colleague.  As
of right now it is not publicly accessible.  I was hoping to get some
advice or suggestions, as opposed to the answer on a silver platter.  Some
thoughts and questions I had:
   1)  Does my second email have any significance.  What is Live555 writing
to the socket now and then in the form of 60 bytes.  Note that this is
after the RTP connection has been negotiated through RTSP.  Is this a
KeepAlive type mechanism?  After examining the code, and doing some light
reading, it seems a KeepAlive might be needed as the communication between
the server and my testRTSPclient is over UDP.  This brings me to my second
thought.
   2)  Do I need a KeepAlive mechanism?  Do I implement it with RTSP
client's SendGetParameter call with a NULL body?  Or does Live555 do this
for us.  (I dug through the source code but I couldn't find where that 60
bytes is sent, could you actually direct me to the class?)
   3)  If you were to speculate, and assume that the server is working
correctly encoding h264 packets to RTP, what are the consistent 60 bytes
reads? (As a sidenote, I am unsure the server is correct, I will sit down
tomorrow with my colleague to review.)

  I hope this wasn't too much at once.  I appreciate all the work you've
done with the library.

Regards,
Constantin

On Tue, May 1, 2012 at 9:04 PM, Ross Finlayson <finlayson at live555.com>wrote:

>    I will be using Live555 to read in an RTSP xh264 Video stream.
>>
>
> What is "xh264"?  Or did you just mean to say "h264"?
>
>
>  I started with the testRTSPClient.  It runs well for 1-10 seconds
>> (variably), then stops.  The program is still running, but it's not getting
>> any new frames.
>>
>
> Where is this H.264 RTSP stream coming from?  I.e., what hardware/software
> is generating it?
>
> Is the stream accessible via a public "rtsp://" URL?  If so, let us know,
> and we'll take a look at it, to try to figure out what's wrong with it.
>  (But if the stream is not publically accessible, then it's hard to say
> what might be wrong...)
>
> Ross Finlayson
> Live Networks, Inc.
> http://www.live555.com/
>
>
> _______________________________________________
> live-devel mailing list
> live-devel at lists.live555.com
> http://lists.live555.com/mailman/listinfo/live-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.live555.com/pipermail/live-devel/attachments/20120501/8023a84c/attachment-0001.html>