The YT chrome etc is added over the top of the <video> element, so it
should look almost identical to the user whichever way you're using it.
To the outer document (your page) it just appears as an iframe and
javascript - so if whether it's flash or <video> shouldn't make any
difference to how your page itself is rendered.
Basically, everything except for the javascript API and the iframe
itself is a black box for us to work with.
I assume that whatever is going on in the iframe itself is similar to
what is going on in the flash player - e.g. there is server-generated
code to serve some kind of unique key, which is being used to stop us
from accessing the raw video stream in any manner which is not
TOS-compliant.
It is a shame we can't access the <video> element ourselves (e.g. for
using it as the source of a WebGL texture), but I understand how that
could prevent monetization of YouTube for Google.
Tim
On Thu, 2011-12-29 at 02:01 -0800, zdravko wrote:
> Thanks Tim, but this still does not answer my question, so my mind is
> still stuck in the gutter ;)
>
> I do get that part about how the iframe api presents both formats in a
> common way as far as javascript coding is concerned. However, what I
> am most curious about is whether the youtube api player appears to
> html5 to be a native video - the same way that other "html5 video
> formats" would appear to it ? Because if it did then instead of the
> yt api , we would do whatever others would do when hosting non youtube
> videos. ?!?
>
> Thanks again.
>
> On Dec 28, 10:12 pm, Tim Wintle <timwin...@gmail.com> wrote:
> > On Wed, 2011-12-28 at 14:51 -0800, zdravko wrote:
> > > So, when one has properly opted in and where html4 videos are being
> > > streamed, there are some cases where specific videos could be streamed
> > > in flash? So, in that "mixed" environment where some videos are
> > > <video> and some are _flash_ do flash videos "mascarade" as html5
> > > video. In other words, did YT build a wrapper that somehow makes the
> > > flash video appear to be html5 video - at least from the javascript
> > > perspective?
> >
> > Yes.
> >
> > The iframe API *should*[0] behave in the same way regardless of if the
> > underlying playback is via <video> or flash.
> >
> > The Developer using the api shouldn't have access to the actual <video>
> > anyway, so all communication is via the javascript YT.Player instance
> > which abstracts all that away.
> >
> > Tim
> >
> > [0] There are some complications - like needing to set wmode in some
> > situations where flash may be displayed.
>
--
You received this message because you are subscribed to the Google Groups "YouTube APIs Developer Forum" group.
To post to this group, send email to youtube-api-gdata@googlegroups.com.
To unsubscribe from this group, send email to youtube-api-gdata+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/youtube-api-gdata?hl=en.
No comments:
Post a Comment