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 through FMS and I get the same problem, make sure the flvs
are not corrupted ..etc
5. check the following example, and make sure after you create allow a frame
to pass so that the draw methods of the flvplayback component are done
drawing.
6. MAKE sure you're not assigning an undefined value or a bad link, it
breaks up the thing !! you'll have to use a catch/try if you're not sure or
if statement before you assign.
function createFLVPlayback()
{
this.my_FLVPlybk = FLVPlayback (this.attachMovie ("FLVPlayback",
"my_FLVPlybk", 500));
this.my_FLVPlybk.autoPlay=true;
this.play_btn._visible= !this.my_FLVPlybk.playing
this.pause_btn._visible=this.my_FLVPlybk.playing
this.my_FLVPlybk.activeVideoPlayerIndex = 1
this.my_FLVPlybk.visibleVideoPlayerIndex = 1
this.my_FLVPlybk.progressInterval = 001;
voloff_btn._visible = false;
play_btn._visible = false;
}
function switchToAnotherPlayer()
{
i=i==1? 2 : 1;
k=i==1? 2 : 1;
my_FLVPlybk.closeVideoPlayer(i);
my_FLVPlybk.ncMgr.close();
my_FLVPlybk.getVideoPlayer(my_FLVPlybk.visibleVideoPlayerIndex).ncMgr.close();
my_FLVPlybk.activeVideoPlayerIndex = k;
my_FLVPlybk.visibleVideoPlayerIndex = k;
}
On 12/16/06, Alon Zouaretz <[EMAIL PROTECTED]> wrote:
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]> wrote:
>
> 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?
> > _______________________________________________
> > [email protected]
> > 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
> >
>
> _______________________________________________
> [email protected]
> 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
>
_______________________________________________
[email protected]
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
_______________________________________________
[email protected]
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
