> Ok. I tried your test program. I tried with scale of 1 and 2. If the
> client sends "Range: npt=30.000-60.000" the server plays starting at 30
> seconds into the clip (clip timing information - not wall time) and plays for
> 30 seconds wall time (which for scale 2 will be 60 seconds of clip
Ok. I tried your test program. I tried with scale of 1 and 2. If the client
sends "Range: npt=30.000-60.000" the server plays starting at 30 seconds into
the clip (clip timing information - not wall time) and plays for 30 seconds
wall time (which for scale 2 will be 60 seconds of clip time).
> Thanks. I don't think I made myself clear though. When I fast forward with
> a range it doesn't stop at the requested end time (but it does stop a little
> while after it). When I fast forward with a range it seems to get confused
> and play to much.
I don't follow this (perhaps one of th
Thanks. I don't think I made myself clear though. When I fast forward with a
range it doesn't stop at the requested end time (but it does stop a little
while after it). When I fast forward with a range it seems to get confused and
play to much.
From: Ross Finlayson
Sent: Monday, July 23,
The server code interprets "now-60" (which, as you noted, the client shouldn't
really be sending anyway, because it's not a live event) the same as "0-60".
If you want to play starting from a specific time, then you'll need to include
that time as the start time in the client's "Range:" header.
Thanks for the help. Also, when I play with a range of "now-60" and a scale of
greater than 1 (fast forward) it will play way past 60 seconds although it does
stop eventually. Any idea why? Thanks.
From: Ross Finlayson
Sent: Friday, July 13, 2012 6:39 PM
To: LIVE555 Streaming Media - develo
> I don't want to distribute my source
And you don't have to. Because the "LIVE555 Streaming Media" code is LGPL, and
not GPL, you don't need to distribute your application's source code, only the
LIVE555 code. (If, as is preferred, you do not modify the LIVE555 code at all,
you can do this
> Can u just tell me how to receive concurrent multiple streams using your
> "test on demand rtsp server" code.
As stated clearly in the FAQ (that you were asked to read before posting to
this mailing list :-), LIVE555-based applications are single-threaded, using an
event loop, rather than mu
I'm trying to decode some H.264 and AAC. It seems like live555 would be
ideal for this task, but I'm getting mixed advice about LGPL under iOS
for paid AppStore Apps.
I get the impression many developers are just including live555
regardless in their paid apps, which puts me at a huge disadva
Hello Sir
i made an application in which i receive the streaming data from
different streamers on my server where i have placed your "test on
demand rtsp server" code.
At my server side i am creating an globally rtsp server and every time
whenever the new streamer start streaming it send a message
Hi,
I'm tryimg to make simple HTTP-based control of RTSP clients, i.e. I
want to be able to start/stop one or more RTSP clients by sending
appropriate HTTP request.
I would like to implement this by using live555 code as much as
possible, especially since there's already test RTSP server
im
11 matches
Mail list logo
