[Live-devel] How to recover from parsing exceptionaldatasituation!
Mike Yan
mikey at tlcwatch.com
Mon Jun 14 18:35:19 PDT 2004
Sorry for not make the statements clear. I mean the time span to recover. I
did not know how much frame skipped, but I count how long the parser get
recover from bad parse. One thing I noticed that the period of recovering is
uncertain. Sometimes it's fast, sometimes it's slow.
-----Original Message-----
From: live-devel-bounces at ns.live.com [mailto:live-devel-bounces at ns.live.com]
On Behalf Of Ross Finlayson
Sent: Monday, June 14, 2004 4:27 PM
To: LIVE.COM Streaming Media - development & use
Subject: RE: [Live-devel] How to recover from parsing
exceptionaldatasituation!
>I have tested the new code of live media. The new one does not get robust
>result as you said. New version code takes even longer to recover than old
>version's each time when it get bad data.
What exactly do you mean by "takes even longer to recover"? Are you
referring to (i) how much input data gets skipped before the parser
recovers, or (ii) how much CPU time the parser takes (when it's trying to
recover)? If you're referring to (i), then this shouldn't happen - the new
code should skip over no more data than the old code did. However, if
you're referring to (ii), then yes, then new code will take more CPU time -
when the parser is recovering - than the old code. (I can probably reduce
this, though.)
Ross Finlayson
LIVE.COM
<http://www.live.com/>
_______________________________________________
live-devel mailing list
live-devel at lists.live.com
http://lists.live.com/mailman/listinfo/live-devel
More information about the live-devel
mailing list