Can you please add some details, like he version of SMP (if you are not using the latest, you can try that one) and the kind of stream you are using.
I'm seeing the same problem. Using Flash Media server 4.5 and an HTTP/HDS stream with two bitrates available. I'm using the latest SMP 1.6 Release version from here: http://sourceforge.net/projects/smp.adobe/files/
The video plays through fine but when it gets to the end the Buffering animation starts playing even though the video is completed. This only happens if I use the HTTP streaming. If I use RTMP streaming or link directly to the mp4 file, the player resets to the beginning and shows the play button.
Any luck on finding an answer to this issue?
My issues are exactly similar to pcmccullnps. no answers yet.
I apologize for not replying earlier.
I acknowledge that there is an issue. I will surely get back with some answers.
Thank you for your patience.
This was a player issue in OSMF 1.6 which has been fixed in 2.0.
Kindly update your players using the latest source given here: http://sourceforge.net/projects/osmf.adobe/files/
If you want to test, the new player is hosted here: http://osmf.org/dev/2.0gm/StrobeMediaPlayback.html
I have downloaded the 2.0 source from your link and inside OSMF > player > StrobeMediaPlayback > html-template there is no StrobeMediaPlayback.swf like the setup code is suggesting. Am I missing something? Did it not get packaged in? I see a StrobeMediaPlayback.js but no swf.
Can I use the swf from the 1.6.328 folder or is that too old?
I have flash builder 4.5, but it will not compile the 2.0 source code. What can I do?
There's not really any doc on it but demos here: http://osmf.org/dev/2.0gm/
This thread's ok too
Not sure if the 'complete' event actually works, but we had a hack using durationChange and currentTimeChange events and it works.
Trap for beginners - looks like the bridge created callback gets called by the player every tick -
So if you're doing stuff in there (like addEventListener) you'll gradually consume more and more cpu until everything craps out.
We solved by just putting everything in an "if" checking we hadn't already done that.