> Just wondering if this bug is a priority or if it may be a while.
FYI, I have just installed a new version (2012.08.17) of the "LIVE555 Streaming
Media" code that - I hope - fixes this bug. If the "Range:" header contains an
end time, then (when serving a Transport Stream file) the server wi
> Just wondering if this bug is a priority or if it may be a while.
The fact that I consider it a bug automatically makes it a priority, but I
can't (and won't) give an ETA (and asking about this will only delay it more :-)
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
Just wondering if this bug is a priority or if it may be a while.
From: Ross Finlayson
Sent: Monday, July 23, 2012 6:20 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Range Header
Ok. I tried your test program. I tried with scale of 1 and 2. If
> 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
clip time).
Shouldn't the server only stream 30 seconds according to the PTS/DTS and ignore
the wall clock time for range not equal to 1?
Thanks.
From: Ross Finlayson
Sent: Monday, July 23, 2012 1:17 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Rang
> 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
y, July 23, 2012 12:43 PM
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Range Header
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
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.
ming Media - development & use
Subject: Re: [Live-devel] Range Header
Thanks for the note. I have now installed a new version (2012.07.14) of the
"LIVE555 Streaming Media" code that updates the RTSP server implementation to
properly handle "Range:" headers like "Range: npt
Thanks for the note. I have now installed a new version (2012.07.14) of the
"LIVE555 Streaming Media" code that updates the RTSP server implementation to
properly handle "Range:" headers like "Range: npt=-60".
(The prebuilt binary versions of the "LIVE555 Media Server" have not yet been
update
Lets say I am 30 seconds into the clip I am watching. If I say play "Range:
npt=-60" it will return "Range: npt=0-" and play from the start. When I use
"Range: npt=now-60" it doesn't return a Range header but continues from where
it left off and stops at 60 seconds into the commercial IF the s
11 matches
Mail list logo
