Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Gregory Maxwell
On Sat, Jun 13, 2009 at 8:00 AM, Chris DiBona wrote: > Comparing Daily Motion to Youtube is disingenuous. If yt were to > switch to theora and maintain even a semblance of the current youtube > quality it would take up most available bandwidth across the internet. [snip] I'm not sure what mixture

Re: [whatwg] getImageData/putImageData comments

2009-06-13 Thread Boris Zbarsky
Boris Zbarsky wrote: It's not that hard, it's an extra four or five lines of code to fill in multiple pixels in a square (two nested for-loops and an expression or two to work out what the limit is). Compared to the maths such code would be doing anyway, this is trivial stuff. The hard part i

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Silvia Pfeiffer
On Sat, Jun 13, 2009 at 11:45 PM, Mike Shaver wrote: > On Sat, Jun 13, 2009 at 9:37 AM, Chris DiBona wrote: > If Youtube is held back by client compatibility, they should be glad > that we're working hard to move ~25% of the web to having Theora > support in the near future!  Google could help that

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Silvia Pfeiffer
On Sat, Jun 13, 2009 at 11:37 PM, Chris DiBona wrote: >> On Sat, Jun 13, 2009 at 8:00 AM, Chris DiBona wrote: >> to YouTube!  I used it as an example of converting content at scale, >> to speak to the relative impact of a codec change vs. API changes in >> terms of effort. >> I don't think the band

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Maik Merten
Frank Hellenkamp wrote: > Well, the thing is (perhabs unfortunately because of patents and > liscensing) that you can use h264 with the video tag (in safari and > chrome), but at the same time you can send the same video to every old > browser with the flash player 9 or 10, because it also supports

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Gregory Maxwell
On Sat, Jun 13, 2009 at 3:06 PM, Frank Hellenkamp wrote: [snip] > Well, the thing is (perhabs unfortunately because of patents and > liscensing) that you can use h264 with the video tag (in safari and > chrome), but at the same time you can send the same video to every old > browser with the flash

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Frank Hellenkamp
Hi, Mike Shaver wrote: > If Youtube is held back by client compatibility, they should be glad > that we're working hard to move ~25% of the web to having Theora > support in the near future! Google could help that cause a lot by > putting (well-encoded, ahem) Theora up there, even if it's just in

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread David Gerard
2009/6/13 Mike Shaver : > On Sat, Jun 13, 2009 at 10:08 AM, Chris DiBona wrote: >> No, but it is what I worry about. How agressive will mpeg.la be in >> their interpretation of the direction that theora is going? I don't >> think that is a reason to stop the current development direction (or >> th

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread David Gerard
2009/6/13 Chris DiBona : > No, but it is what I worry about. How agressive will mpeg.la be in > their interpretation of the direction that theora is going? Given what they've already expressly stated they're doing with H.264 licensing from 2010, it's entirely unclear how vague and likely spuriou

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread King InuYasha
On Sat, Jun 13, 2009 at 10:58 AM, Maik Merten wrote: > Mike Shaver wrote: > > Yep, I'll reach out to the o3d guys directly as well, see if they have > > the source video for that clip. More than happy to do the > > measurements on this side, I know what a pain travel can be... > > I'll happily pr

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Maik Merten
Mike Shaver wrote: > Yep, I'll reach out to the o3d guys directly as well, see if they have > the source video for that clip. More than happy to do the > measurements on this side, I know what a pain travel can be... I'll happily provide encoding-assistance if wanted :-) Maik

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Mike Shaver
On Sat, Jun 13, 2009 at 11:25 AM, Chris DiBona wrote: > It'll take a little while, I'm travelling a bit this month (brazil , > new york, etc..) Yep, I'll reach out to the o3d guys directly as well, see if they have the source video for that clip. More than happy to do the measurements on this sid

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Maik Merten
Gregory Maxwell wrote: > Perhaps then you wouldn't mind sharing the rough breakdown of how many > YouTube distributed videos are the 'high quality' files which are > encoded in H.264 and only provided on user-request vs the normal > quality, which is provided by default, and which doesn't use H.264

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Chris DiBona
It'll take a little while, I'm travelling a bit this month (brazil , new york, etc..) Chris On Sat, Jun 13, 2009 at 10:55 AM, Håkon Wium Lie wrote: > Also sprach Chris DiBona: > >  > > I don't think the bandwidth delta is very much with recent (and >  > > format-compatible) improvements to the Th

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Maik Merten
Mike Shaver wrote: > b) bandwidth concerns (but even if Theora took _double_ the bandwidth, > and _all_ the content was converted overnight, that's still only a 25% > increase in bandwidth, plus a few percent for Chrome when it ships > as well) Actually, looking at http://en.wikipedia.org/wiki/Yo

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Gregory Maxwell
On Sat, Jun 13, 2009 at 8:00 AM, Chris DiBona wrote: > Comparing Daily Motion to Youtube is disingenuous. If yt were to > switch to theora and maintain even a semblance of the current youtube > quality it would take up most available bandwidth across the internet. > The most recent public number wa

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Håkon Wium Lie
Also sprach Chris DiBona: > > I don't think the bandwidth delta is very much with recent (and > > format-compatible) improvements to the Theora encoders, if it's even > > in H.264's favour any more, but I'd rather get data than share > > suppositions.  Can you send me a link to raw video for t

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Mike Shaver
On Sat, Jun 13, 2009 at 10:39 AM, Chris DiBona wrote: > Let me ask David Sparks and see where it went, I remember we had it in > the inital drops, or thought we did. That'd be great -- all I can find reference to is Vorbis, as used for the ringtones and system sounds (righteous!) Mike

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Chris DiBona
Let me ask David Sparks and see where it went, I remember we had it in the inital drops, or thought we did. On Sat, Jun 13, 2009 at 10:35 AM, Mike Shaver wrote: > On Sat, Jun 13, 2009 at 8:00 AM, Chris DiBona wrote: >> actually shipping with Theora (also on android, too) > > I was looking for a re

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Mike Shaver
On Sat, Jun 13, 2009 at 8:00 AM, Chris DiBona wrote: > actually shipping with Theora (also on android, too) I was looking for a reference to this, but haven't found anything yet. http://developer.android.com/guide/appendix/media-formats.html lists Vorbis, but not Theora, and I can't find any anno

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Mike Shaver
On Sat, Jun 13, 2009 at 10:08 AM, Chris DiBona wrote: > No, but it is what I worry about. How agressive will mpeg.la be in > their interpretation of the direction that theora is going? I don't > think that is a reason to stop the current development direction (or > the funding of it) but I thought

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Chris DiBona
> We certainly believe so, but I'm certainly not qualified to evaluate > the different techniques. > > Would Theora inherently be any less able to than any other codec > system, though?  I hope you're not saying that it has to be H.264 > forever, given the spectre of the streaming license changes a

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Mike Shaver
On Sat, Jun 13, 2009 at 9:37 AM, Chris DiBona wrote: > I tried funding dirac a while back, to some good end, and we provide > students, but here's the challenge: Can theora move forward without > infringing on the other video compression patents? We certainly believe so, but I'm certainly not qual

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Chris DiBona
> On Sat, Jun 13, 2009 at 8:00 AM, Chris DiBona wrote: >> Comparing Daily Motion to Youtube is disingenuous. > > Much less so than comparing "promotion of H.264-in- via > Google's sites and client" to "support for legacy proprietary content > via plugin APIs", I would say.  But also, I didn't compa

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Mike Shaver
On Sat, Jun 13, 2009 at 8:00 AM, Chris DiBona wrote: > Comparing Daily Motion to Youtube is disingenuous. Much less so than comparing "promotion of H.264-in- via Google's sites and client" to "support for legacy proprietary content via plugin APIs", I would say. But also, I didn't compare DailyMo

Re: [whatwg] H.264-in- vs plugin APIs

2009-06-13 Thread Chris DiBona
Comparing Daily Motion to Youtube is disingenuous. If yt were to switch to theora and maintain even a semblance of the current youtube quality it would take up most available bandwidth across the internet. The most recent public number was just over 1 billion video streams a day, and I've seen what

Re: [whatwg] Vulgar fractions

2009-06-13 Thread Kristof Zelechovski
Actually aligning vulgar fractions is not even a CSS thing, it is an OpenType thing. Chris

Re: [whatwg] getImageData/putImageData comments

2009-06-13 Thread Robert O'Callahan
On Sat, Jun 13, 2009 at 6:57 PM, Ian Hickson wrote: > There's no practical difference as far as I can tell between hoping that > we can reuse the API, and then finding we can't, and introducing a second > API for high-res screens; and just giving up now and saying that it's a > low-res API, and t