Hi,
this is still not completely clear to me (but then very few things are....).
What I do realize (approximately) is that the flow of the MEDIA_PLAYFILE_STOP
message would probably be as follows:
- MprFromFile would finish playing (either because there is no more data or it
was told to stop) so it will send an internal message to:
-> MpCallFlowGraph who would notify:
-> CpPhoneMediaInterface which should hold on to the IMediaEventListener
interface ptr passed to createConnection, this would call the onFileStop
function in:
-> SipConnection which would post the MEDIA_PLAYFILE_STOP message to:
-> CpCallManager which would pass it on (the rest is probably irrelevant for
this discussion).
What I don't get is what would be the correct way for MpCallFlowGraph to notify
CpPhoneMediaInterface. The latter has a pointer to the former, but I cannot
find a simple way for MpCallFlowGraph to notify it's parent (assuming that the
relationship is like that).
Also, I would really like the MEDIA_PLAYFILE_STOP message to indicate how much
was actually played (I know that MprFromFile stores it in the mFileBufferIndex
member variable, seems to be a matter of passing it as a parameter with all the
messages). This addition would make room for functionality like pausing and
then restarting, or playing a buffer, pausing, and then recording from that
position.
Keith: is the new notification messaging system used anywhere besides in the
MprFromFile class? I.e. is anyone using that functionality in MprFromFile?
Regards,
Daníel
> Date: Fri, 18 May 2007 10:35:29 +0200> From: [EMAIL PROTECTED]> To:
> [email protected]> Subject: Re: [sipxtapi-dev]
> MEDIA_PLAYFILE_START, MEDIA_PLAYFILE_STOP, MEDIA_PLAYBUFFER_START and
> MEDIA_PLAYB> > -----BEGIN PGP SIGNED MESSAGE-----> Hash: SHA1> > > There is
> one message you can use. Right now it's internal, and meant> > > just for the
> flowgraph (so it can do some cleanup of it's own)...> > > FLOWGRAPH_STOP_PLAY
> - which is sent in the doProcessFrame loop of> > > MprFromFile (
> MprFromFile.cpp:617). I'd recommend against extending> > > this particular
> message out to the CallLib..> > I was thinking he could use the
> IMediaEventListener interface that is> passed into
> CpPhoneMediaInterface::createConnection to fire events into> CallLib. If you
> look at its methods you will see it was intended to be> used for this
> purpose.> > CpPhoneMediaInterface::createConnection is called for example
> from line> 825 from SipConnection where we pass this cast to
> IMediaEventListener as> SipConnection implements it.> > Jaro> -----BEGIN PGP
> SIGNATURE-----> Version: GnuPG v1.4.7 (MingW32)> Comment: Using GnuPG with
> Mozilla - http://enigmail.mozdev.org> >
> iD8DBQFGTWVRTzSnIPmBbH8RArTUAJ0TY8kQ9sANtD+CKSeODl0cybR5QQCfVeHM>
> 4vTCnQS/NHUdL32b2n387mQ=> =UNjI> -----END PGP SIGNATURE----->
> _______________________________________________> sipxtapi-dev mailing list>
> [email protected]> List Archive:
> http://list.sipfoundry.org/archive/sipxtapi-dev/
_________________________________________________________________
Explore the seven wonders of the world
http://search.msn.com/results.aspx?q=7+wonders+world&mkt=en-US&form=QBRE
_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
