[Live-devel] fNumFramesUsedSoFar and MutiFramedRTPSink
Ross Finlayson
finlayson at live555.com
Wed May 10 01:08:09 PDT 2006
At 12:52 AM 5/10/2006, you wrote:
> > Unfortunately I'm still not seeing any problem with
> > this. "sendNext()" calls "buildAndSendFrame()", which in turn resets
> > "fNumFramesUsedSoFar" to zero.
>True, but then later if a frame is got (in afterGettingFrame),
>fNumFramesUsedSoFar is incremented. It is then sent but
>"fNumFramesUsedSoFar" keeps its value until sendNext() is called
>again. So if ourHandleCLosure is called (before the new call to
>sendNext()), "fNumFramesUsedSoFar" equals 1.
OK, I see now. The problem in this case is that "ourHandleClosure()"
will cause an extra, 'dummy' packet to be sent.
>I added "fNumFramesUsedSoFar=0" just after sending the packet and my
>problem was fixed.
OK, I'll also include this in the next software release.
Ross Finlayson
Live Networks, Inc. (LIVE555.COM)
<http://www.live555.com/>
More information about the live-devel
mailing list