From: zdravko <email.workbench@gmail.com>
To: YouTube APIs Developer Forum <youtube-api-gdata@googlegroups.com>
Sent: Tuesday, December 27, 2011 1:06 PM
Subject: [YouTube-API] Re: HTML5 player in YouTube set top box app
I could be wrong but from somewhere I have this idea that tv set-top
boxes are such a special area that TOS may have special restrictions
regarding them. You should make sure that TOS allows you to do what
you are already in the process of doing, before you get it done and
find out that you are not allowed to.
On Dec 23, 7:24 am, "Adeline @ ANTplc" <adelinedarl...@googlemail.com>
wrote:
> Hi,
>
> I work for a company that develops set top box applications. We have our
> own platform, which consists of an in house browser (Galio), which is
> standards compliant but has some extra functionality to perform the
> middleware jobs we need in order to interact with the box. Because of the
> different nature of the environment I'm not sure how much help people are
> going to be able to offer, but thought I might as well give it a go.
>
> The apps we're building for one of our current customers includes a set of
> web applications, one of which is YouTube. We don't support Flash, so we're
> using the HTML5 player (I'm aware this is experimental at the moment, but
> this product won't be going into the market with this feature for a while).
> I've had horrendous issues getting to the point where we can actually play
> video, but finally got there yesterday. However I still have some problems.
>
> I don't think anyone outside of the YT dev team is likely to be able to
> have much insight on these...
>
> 1/ From some debugging in the browser code it looks as though multiple
> video elements are getting created. I only ever see one get inserted into
> the page, so wasn't worrying too much about this, until one of our browser
> team just informed me that the video load algorithm is also getting called
> multiple times. This would imply that the video tag is getting re-inserted
> over and over (5 times apparently!).
>
> 2/ The video size varies, even though I'm specifying it in the iFrame
> properties.
>
> 3/ My YT.Player object instantiation fails (meaning I get no video unless I
> create the iFrame myself) and therefore I can't interact with the video.
> This is almost certainly going to be an issue with our browser.
> Unfortunately, all the API code is obfuscated, so working out what support
> we're lacking isn't easy.
>
> 4/ The spinner remains after the video has started playing
>
> Like I said, it's probably unlikely anyone's going to be able to help much
> here. I was hoping to be able to contact YT and see about getting a bit of
> support with this, but that doesn't look like an option.
>
> Thanks for reading ;)
> Adeline
--
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.
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