I think it is possible to use setParseState(); function within the skip loop to prevent the overflowing. But I'm not sure it this way the right way.
Yes, actually this is the right thing to do. You should call "setParseState()" just after you've finished parsing (or skipping) each complete NAL unit. If you do this, and a C++ exception occurs (because more input data needs to be read), then later on - when "parse()" gets called again to re-parse the data, the parsing will resume from this same point (and the input buffer won't fill up with unparsed data).
-- Ross Finlayson Live Networks, Inc. http://www.live555.com/ _______________________________________________ live-devel mailing list live-devel@lists.live555.com http://lists.live555.com/mailman/listinfo/live-devel
