On Tue, Oct 6, 2009 at 12:55 AM, Sébastien Escudier <span dir="ltr"><sebastien-devel@celeos.eu></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Quoting Ross Finlayson <<a href="mailto:finlayson@live555.com">finlayson@live555.com</a>>:<br>
<br>
> >I don't seem to get the stack overflow anymore, but something tells<br>
> >me if this records for a while and all of these chunks are kept in<br>
> >memory, then it'll blow up pretty soon.<br>
><br>
> Yes, and unfortunately there's not a lot we can do about this,<br>
> because of the stupid brain-damaged way in which the ".mov" (and<br>
> ".mp4") file formats was designed.<br>
<br>
</div>what do you call "for a while" ?<br>
I don't know .mov files, but for .mp4 files, your file will become way too big<br>
before you run out of memory because of chunks and frames informations kept in<br>
memory.<br>
You should consider splitting your files after a few hours of recording.<br>
</blockquote></div><br>If you're really serious about writing MP4/MOV files, I would not use Live555 code for that (Live555 is "Source-code libraries for standards-based
RTP/RTCP/RTSP/SIP multimedia streaming"; it is not an MP4/MOV container library). Rather, I'd consider something like mp4v2, or ffmpeg's container code.<br>