It doesn't seem like there's a way to dynamically resize buffers without losing data because in the afterGettingFunc if fNumTruncatedBytes > 0 you've already lost the data. The only post I've really seen talk about this is here: http://lists.live555.com/pipermail/live-devel/2009-January/010083.html
It sounded like they came to the same conclusion. So with that in mind I created a patch that I'm hoping may get incorporated in a future release. Or at least some incarnation of it. See the attached file for details. The downside to doing it this way is that you're potentially allocating multiple times per frame, but I would imagine the code to reallocate should be allocating larger than what was requested anyway and its better than nothing. I made the new parameters for getNextFrame have default values of NULL, but perhaps the better approach for compatibility would be to add a getNextFrame2 that has these extra parameters.
DynamicBuffer.patch
Description: Binary data
_______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel