Hello, On 3/22/07, Daniel Petrie <[EMAIL PROTECTED]> wrote: > We already have a heartbeat for the media task, it probably would not > be difficult to send the heartbeat (i.e. OsMsg) to multiple consumers > (e.g. the MpOutputDeviceManager). As I mentioned, under Windows current heartbeat timer send messages from speaker thread at the same time when next frame of data is pushed to audio device. If we remove speaker thread, we lose heartbeat timer. If we want to port this heartbeat timer to new framework, it's a good time to abstract it too. Current implementation take heartbeat ticks from one source and send it to all flowgraphs. With this approach we're falling to clock skew problems all the time. If flowgraph use one audio device, it should take clock from this device, or have good logic for clock skew detection and correction.
-- Regards, Alexander Chemeris. SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000 _______________________________________________ sipxtapi-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
