Hi,
1. Switch between indexes if you have alot of sequential movies to play
2. use doLater if you're building on top of mx.core.uicomponent or a
setInterval() with 100 milliseconds and a clear Interval to kill it again
3. Make sure you get the latest FLVPlayback component update
4. I am streaming
hey, I had the same problem and manage to get around it with adding a
0.1sdelay to the function that load the video, so its not being called
once the
component [or the movieclip that holds it] is attached but once its already
on the stage.
hth
a
On 12/15/06, Josh Santangelo <[EMAIL PROTECTED]>
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
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 v
4 matches
Mail list logo
