The bulk of the index could be written to a temp file as the video
portion of the file is filled and then attached to the end of the AVI /
QT file along with any of the other index information that may be
required to wrap the raw index. I know, more to manage and potential
problems with partial completion but I think the memory problem is
solved by this strategy.
On 10-12-14 8:13 PM, Ross Finlayson wrote:
One thing that should be taken into account. The memory allocated by
AVIFileIndex for index grows as video is being received and recorded,
because index section should be added to the very end of AVI file,
just before closure. Although size of index data is very small
comparing to video data, it still could potentionally exhaust all
available memory after the very long recording (many hours).
Yes, it turns out that we have the same issue for
"QuickTimeFileSink". Unfortunately there isn'e anything we can do
about this; these file formats are not well-designed for the purpose
of recording incoming streams.
--
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-devel
_______________________________________________
live-devel mailing list
live-devel@lists.live555.com
http://lists.live555.com/mailman/listinfo/live-devel
