Roberta. This is kinda getting off topic of this list, but some things to keep in mind:
- wmode=transparent this definitely affects performance and should be avoided if at all possible. You can use wmode=opaque if you still need Flash to be a part of the z-indexing of the page (eg a HTML menu has to appear ove the op of the page). The only time you should use transparent is if you HAVE to have content showing through the background of the flash file. - use of timers etc to calculate the position does the API allow you to listen to progress events from the netstream class of the video? You really want an accurate way of calculating the video position. you should be able to also use a combination of : *player.getDuration()* * * and * * player.getCurrentTime() * * to work out the progress (or is this is what you are doing now with your timer?) Aran * * On Thu, Jan 14, 2010 at 5:09 AM, Roberta <[email protected]> wrote: > I think I'm starting to figure it out. On the embed, I've got > wmode=transparent, because it has to be set that way for the page I'm > working on. Between that and the video running, the frame rate being > affected, which is messing up how often the timer fires. I'm going to > try playing around with the quality when I publish it (maybe use > "autohigh" instead of "high"). I'm still not understanding why this > would be more of a problem with swfobject than the old-fashioned > embed, but as long as it's now working better, I'm happy. > > Thanks for responding! > Roberta > > > On Jan 13, 11:06 am, Philip Hutchison <[email protected]> wrote: > > SWFObject has nothing to do with the content of a SWF or its frame rate, > > except perhaps setting some paramaters when embedding or passing values > via > > FlashVars. Neither of these is used to change the frame rate. > > > > - philip > > > > > > > > On Wed, Jan 13, 2010 at 6:52 AM, Roberta <[email protected]> wrote: > > > Thanks for the quick response, Aran. Yes, I did read all the docs you > > > mentioned, and I've looked at the example. I agree with you that it > > > has something to do with how I've coded or, more likely, published > > > it. I don't think it has anything to do with the youtube API, > > > though, because youtube has nothing to do with calculating where to > > > put the ball on the slider - that's all in my code, which is in > > > Actionscript. The example doesn't have a progress bar, though, and > > > it's in javascript in the HTML, not Actionscript, so it doesn't > > > help. > > > > > The reason I asked the question in this forum was that I thought I saw > > > something in my googling adventures yesterday about swfobject and > > > default frame rate. When I change the frame rate in the actionscript > > > and the .fla, it changes the speed of the bar, and how far it > > > progresses before it thinks it's done. It's still wrong, just > > > differently wrong. I guess what I'm looking for is clarification on > > > swfobject and frame rate. > > > > > I'm starting to wonder if the reason I haven't found any actionscript > > > examples is because no one else has been able to do this either :-). > > > > > Thanks, > > > Roberta- Hide quoted text - > > > > - Show quoted text - > > -- > You received this message because you are subscribed to the Google Groups > "SWFObject" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<swfobject%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/swfobject?hl=en. > > > >--
You received this message because you are subscribed to the Google Groups "SWFObject" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/swfobject?hl=en.
