[Live-devel] aac headers

Edward edward at v-ecom.com
Fri Jan 16 01:07:15 PST 2009


Hi,

openrtsp only output raw audio files that are not playable on any 
player. i used faad to create an aac file from the raw audio file. is it 
possible to add the headers directly from openrtsp? which part of the 
code do i edit so i can insert the faad library?

live-devel-request at ns.live555.com wrote:
> Send live-devel mailing list submissions to
> 	live-devel at lists.live555.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.live555.com/mailman/listinfo/live-devel
> or, via email, send a message with subject or body 'help' to
> 	live-devel-request at lists.live555.com
>
> You can reach the person managing the list at
> 	live-devel-owner at lists.live555.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of live-devel digest..."
>
>
> Today's Topics:
>
>    1. Re: Memory leaks (Ross Finlayson)
>    2. Re: Memory Leaks ! (Ross Finlayson)
>    3. Multiplexing RTP and RTCP (Gabriele De Luca)
>    4. Implementation of Live555 Streaming media in smart	phone
>       ( Miguel Carretero Rodr?guez )
>    5. Re: Implementation of Live555 Streaming media in smart	phone
>       (Erik Hovland)
>    6. What to do when fNumTruncatedBytes  > 0 (Matt Schuckmann)
>    7. streaming MPEG4 without VOSS & VOS markers (Stephen Berry)
>    8. RTSP clinet (Aditya Vikram)
>    9. changing frames' resolution during a stream (Filippo Rossi)
>   10. Re: changing frames' resolution during a stream (Ross Finlayson)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 8 Jan 2009 12:05:00 -0200
> From: Ross Finlayson <finlayson at live555.com>
> Subject: Re: [Live-devel] Memory leaks
> To: LIVE555 Streaming Media - development & use
> 	<live-devel at ns.live555.com>
> Message-ID: <f06240807c58bb629b8e6@[66.80.62.44]>
> Content-Type: text/plain; charset="us-ascii" ; format="flowed"
>
>   
>>               I am sending the file which describes regarding the 
>> memory leak in the code.
>>     
>
> I'm not convinced that any of these are real memory leaks; instead, 
> they seem to just be the "LIVE555 Media Server" doing its job.
>
> Note that the server works by dynamically allocating a 
> "ServerMediaSession" object (and appropriate "ServerMediaSubsession" 
> objects) for each file that it streams.   This object remains 
> allocated even when the stream stops (but will get reused the next 
> time that the same file is streamed).  In any case, the allocated 
> memory (for each file that gets streamed) is very small.
>
> There would be a "memory leak" only if the allocated memory keeps 
> increasing whenever the *same* file is streamed several times in 
> succession.  If you see that happening, let me know.
>   


More information about the live-devel mailing list