I've had similar problems and struggled for weeks to solve them. I
found that in general, FLVPlayback is much more reliable with RTMP
streams than HTTP.
Another thing to mess with is the visiblePlayerIndex and
activePlayerIndex properties. Instead of playing one file right after
the other in the same player, switch between a couple of player
indexes. I think this approach works a bit better.
-josh
On Dec 13, 2006, at 10:36a, grimmwerks wrote:
I've got an instance of the FLVPlayback in an app that is getting sent
a path; it's contentPath was just being resent the new path.
It's not working 100%, as every so often it decides it doesn't want to
load that requested video.
What's a better way of using one FLVPlayback object that reloads video
requested? Birthing a new instance each and every time?
_______________________________________________
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
_______________________________________________
Flashcoders@chattyfig.figleaf.com
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
