On the sender side, the output buffer is encapsulated wihtin the OutPacketBuffer class (see MediaSink.cpp). In its constructor, a buffer is allocated (called fBuf). It is *that* buffer that gets passed to the input source. Ex: MultiFramedRTPsink class passes the pointer to the fBuf buffer (by calling the curPtr() method of OutPacketBuffer class) to the source (through the getNextFrame method of the source). This pointer is called 'fTo' wihtin the context of the source. The same goes for the 'fMaxSize': it is the size of the OutPacketBuffer passed from the sink to the source in the 'getNextFrame'.
IMPORTANT NOTE: the maximum size of the output buffer is hardcoded to be 60KBytes. You need to change this value if your output is larger than this (see OutPacketBuffer:maxSize in MediaSink.cpp ). Would it make sense to allow the user to change this maximum value dynamically? In my application I had to increase the hardcoded 60KBytes and recompile the live555Media library. The same goes for the receiver side buffer. Mojtaba Hosseini -----Original Message----- From: [EMAIL PROTECTED] on behalf of Luc Roels Sent: Fri 6/22/2007 3:33 AM To: Live555 group Subject: [Live-devel] (no subject) -----Original Message----- From: [EMAIL PROTECTED] on behalf of Luc Roels Sent: Fri 6/22/2007 3:33 AM To: Live555 group Subject: [Live-devel] (no subject) In the FAQ, I read that to implement live streaming you have to created your own FramedSource subclass to encapsulate your input source. In essence in the deliverframe you have to copy your frame data to the fTO. What I don't understand is where the frame memory ( pointed to by the fTO pointer ) is allocated and where the fMaxSize is set? Can you shed some light on this? _________________________________________________________________ Ontdek Windows Live Hotmail, het ultieme online mailprogramma! http://get.live.com/mail/overview
<<winmail.dat>>
_______________________________________________ live-devel mailing list [email protected] http://lists.live555.com/mailman/listinfo/live-devel
