[Live-devel] Continous Streaming of m4e files

Cristaldi Ambra Ambra.Cristaldi at elsagdatamat.com
Fri Sep 14 01:57:48 PDT 2007


Hello.

 

We're trying to use Live555 code in order to implement a H24 network
video recorder (NVR). Apparently, the Live555 stuff performs quite well
both in recording m4e files, and in restreaming the recorded files, but
we're in deep troubles trying to customize a detail in the mechanism of
restreaming when switching from one file to the next: simply, we can't
find where in the code this is implemented. I know we're admitting some
sort of incompetence, but it's been several days of code hunting, and we
got nothing.

 

So, let's first explain why we're having this peculiar problem, and why
the playlist mechanism already implemented in Live555 doesn't suit our
needs. The H24 continuous recording is based on a circular queue of
files that are recorded and cyclically deleted at the end of the queue
to keep a roughly constant space on hard disk. Upon this, let's say,
circular playlist, you may ask the NVR to start streaming from a given
time in the past on, and in H24 mode as well. This means that the DVR
will stream, perhaps, files that still have to be created at the time
you issue the play command. Even the m4e pathnames are not fully
determined in advance.

 

So, the basic idea is the following: find out where Live555 is becoming
aware of the end of a m4e file and, through a callback routine that
wouldn't impact on the Live555 project source code, insert a new m4e
file to the current playlist, maybe deleting also the last file just
streamed. In this way the streaming process may continue indefinitely
(if requested to) adding one file at a time whose pathname may be
calculated at runtime depending on the particular naming policy of the
NVR. Also, we hope that in this way we should be able to stream files
upon the very same RTSP/RTP session with no noticeable delay when the
file switch occurs, exactly as if we were streaming a single endless
file.

 

We don't know whether this situation may be general enough to interest a
wider audience, but we're stuck, as I said, in the effort of trying to
find out where the callback routine should be invoked. Could you provide
us some direction? Thanks in advance.

 

 

 

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.live555.com/pipermail/live-devel/attachments/20070914/9b801fb8/attachment.html 


More information about the live-devel mailing list