<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
You can't falsify the MOOV atom because it contains file offsets to the individual data blocks, and you wont know what those offsets are until the data is written. If you need to stream realtime then MP4 is not a good format.<br><br>I didn't realize you were only streaming audio though. In that case you don't really need a container at all. You can stream raw AAC frames as long as they have an ADTS header attached. You only need a container if you need to interleave audio and video data, or if you need timestamps for seeking. If you're just streaming in real time then sending raw frames should work fine.<br><br>Dan<br><br><div>> Date: Wed, 5 Oct 2011 23:05:16 +0000<br>> From: atlithorn@gmail.com<br>> To: libav-user@ffmpeg.org<br>> Subject: Re: [Libav-user] newb mp4 question<br>> <br>> Thanks Dan, when we stream live we often falsify the content-length to<br>> something like 2gb, users are never going to hit that limit with<br>> normal usage so it's "good enough". The underlying http client will<br>> often cut off at that point which is fine, people will forgive<br>> restarting a stream after 2gb of listening.<br>> <br>> Could I use QTFastStart and provide similarily false information to<br>> the container so it could at least start streaming?<br>> <br>> While I have you on the line ;) what transport stream should I<br>> otherwise be looking at. I don't have a lot of options to choose<br>> from....<br>> <br>> Atli.<br>> <br>> On 5 October 2011 22:38, Dan Haddix <dan6992@hotmail.com> wrote:<br>> > MP4 files contain something called a MOOV atom, which contains vital<br>> > information about the file that is needed for playback. The MOOV atom is not<br>> > written until you call av_write_trailer. And even then it's written to the<br>> > very end of the file which makes it so you can't stream the file. There is<br>> > another chunk of code in FFmpeg called QTFastStart which moves the MOOV atom<br>> > to the start of the file, which in turn makes it possible to stream the<br>> > file, but you still need a finished file before you can call it. So it's<br>> > really only meant for streaming complete files from a server to a player.<br>> ><br>> > If you need to remux and stream in realtime then you'd be better off using<br>> > another format. Transport streams are the best for streaming. They have no<br>> > header or footer and can be picked up at any point in the stream without<br>> > issue. This is why broadcasters use TS for digital TV signals.<br>> ><br>> > Dan<br>> ><br>> >> Date: Wed, 5 Oct 2011 22:18:24 +0000<br>> >> From: atlithorn@gmail.com<br>> >> To: libav-user@ffmpeg.org<br>> >> Subject: [Libav-user] newb mp4 question<br>> >><br>> >> Hi, I'm trying to remux an flv muxed aac stream using the mp4 muxer.<br>> >> (movenc.c). It works fine so long as I call av_write_trailer.<br>> >><br>> >> Problem is I also need to remux live (long running) streams, how would<br>> >> I go about that. Currently a skeleton of my code looks like this<br>> >><br>> >> init_input<br>> >> init_output<br>> >><br>> >> do{<br>> >> av_init_packet(&ipacket)<br>> >> av_read_frame(iFormatCtx, &ipacket);<br>> >> if(packet.stream_index == audioStrem){<br>> >> av_init_packet(&opacket);<br>> >><br>> >> copy stuff around, code borrowed from ffmpeg.c<br>> >><br>> >> av_write_frame(oFormatCtx, &opacket);<br>> >> av_free_packet(&opacket);<br>> >> }<br>> >> av_free_packet(&ipacket);<br>> >><br>> >> }while(stuff is incoming);<br>> >><br>> >> av_write_trailer(oFormatCtx);<br>> >><br>> >><br>> >> I was hoping I could buffer av_write_frame calls and write out to a<br>> >> client but the client can't understand the file without the trailer it<br>> >> seems. I'm new to this stuff so I was hoping someone could point me in<br>> >> the right direction.<br>> >><br>> >> Before you ask, I am streaming to the Android MediaPlayer so my format<br>> >> options are a little limited.<br>> >><br>> >> Thanks,<br>> >> Atli.<br>> >> _______________________________________________<br>> >> Libav-user mailing list<br>> >> Libav-user@ffmpeg.org<br>> >> http://ffmpeg.org/mailman/listinfo/libav-user<br>> ><br>> > _______________________________________________<br>> > Libav-user mailing list<br>> > Libav-user@ffmpeg.org<br>> > http://ffmpeg.org/mailman/listinfo/libav-user<br>> ><br>> ><br>> _______________________________________________<br>> Libav-user mailing list<br>> Libav-user@ffmpeg.org<br>> http://ffmpeg.org/mailman/listinfo/libav-user<br></div> </div></body>
</html>