> On Dec 11, 2019, at 11:54 AM, Jeff Shanab wrote:
>
> In RTSPClient, Would it be better to have the cast from char* to u_int8_t*
> inside the write function, so those operations systems that expect send to
> have a char * will not need re-casting?
Yes, perhaps - though this is not a big de
In RTSPClient, Would it be better to have the cast from char* to u_int8_t*
inside the write function, so those operations systems that expect send to
have a char * will not need re-casting?
(If not an alternate solution like typedef SOCKET and DATATYPE in a common
platform header or compiler define
Thanks. I have just released a new version (2019.12.10) that includes this
patch.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-deve
Hi Ross,
I am currently using a new video recorder.
When I send it a RTSP START command with a range (like "Range: npt=0.000-"), it
returns me a response with the following format : "Range:
npt=0:0:28.0-0:5:28.0" or "Range: npt=0-0:5:0.0".
This Normal Play Time format is well defined in the RFC
