Re: Embedded Windows Media Player 11 odd behavior

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Arjan:

As I wrote in my previous post, the WMP play states are not guaranteed
to occur in any particular order - they may fire in different orders
depending on the version of WMP you have and the type media you are
playing. This could explain the different behaviors you are seeing
between operating systems.

Your code is based on catching the "stopped" state when the
PlayStateChange event is fired. Try firing next() under "case 8: //
wmppsMediaEnded" instead - this is the state that indicates that the
media has played through until completion. I don't believe this event
is ever called when you call Player.Controls.Stop(), however, so you
will have to address that somehow too.

I also think you can dump all of the code in the OpenStateChange
handler. As long as you keep the 'autoStart' param value="true", the
player will play the file automatically each time the URL is updated.

--Tim

.