Here is an answer:
This behavior is expected; there is nothing to correct. The accuracy and frequency of time updates depends upon the 
implementation of the io-media graphs used to process the media, and on the accuracy and frequency of updates delivered 
by the underlying drivers and hardware. Graphs should attempt to deliver a timing resolution of 100 milliseconds or 
better, but this resolution is not always available.

The MME delivers the MME_EVENT_TIME event to the client application only when it receives a time update from the device 
or driver (through io-media). Thus, if, for example, the MME's notification interval to the client application is set to
 100 milliseconds, but a driver delivers time position updates to the MME only every 300 milliseconds, the client 
application will only receive time updates every 300 milliseconds and may see jitter in the time reporting.