Lantency in ltmmPlay_Notify_StateChanged notification

I have a requirement to play file segments "seemlessly", that is, "file1.avi" is playing and then transit to "file2.avi" as though they were one file. I have everthing set up (two player instances wiih files loaded and ready).

What I wanted to do was use the SetWindowNotify() with ltmmPlay_Notify_StateChanged notification to tell me when "file1.avi" reached the end (state goes from "Running" => "Paused or Stopped".) and then start "file2.avi" playing. The problem is I seem to get a 1 to 2 second delay between the time "file1.avi" stops and the notification is received by the SetWindowNotify message handler. I see no other way to get notification of EOF from a "Running" file.

I experimented with the PlayWnd.cpp DriectShow example, and the corresponding event interface handler gets the EC_COMPLETE within milliseconds (which would allow starting the next file playing without a noticable delay). But if I have to use DirectShow directly that sorta sorta kills the deal, hmmm?

Anyway, it would be a great hep if anyone has any ideas about why the delay in notification and how to eliminate it.

You could use the ltmmPlay_Notify_TrackingPositionChanged
notification value to know where exactly playback has reached, and when it reaches the end, continue playing back the next video.