d the camera hardware boots up "something" to provide an
RTSP server on the network, with only a limited browser interface or none. If
anyone knows of some standard that would allow such a system to be modified, I
would look into it. I haven't had much luck searching for
parse the client_port in the
SETUP response and use that if the ports are different than requested?
Thank you for your attention and any insights,
Derrick N. Guerrero
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
>
> I've found out that when you run a few different instances of RTSP clients
>> in separate threads CSeq number is not increased by one with each
>> consecutive request.
>> It's because CSeq number is a static variable in RTSPClient.
>>
>
> This is a perfect illustration of why you are not suppos
I'm trying to implement trick-mode support server and client side. My
original attempt for UI notification of playback time was to use the pts
provided by ffmpeg for the position within the media, and on the client side
take this pts out of the total duration to update my media slider. After
any t
p the
chunks periodically.
I don't seem to get the stack overflow anymore, but something tells me if
this records for a while and all of these chunks are kept in memory, then
it'll blow up pretty soon.
Thanks.
Derrick N. Guerrero
Index: QuickT
