Linked by Thom Holwerda on Thu 30th Sep 2010 23:04 UTC
Google A few months ago, Google open sourced the VP8 video codec as part of the WebM video project, to create a truly Free/free unencumbered video format for the web as an answer to the non-Free/free patent-encumbered H264 format. Today, Google launched a new image format for the web, WebP, which aims to significantly reduce the file size of photos and images on the web.
Permalink for comment 443466
To read all comments associated with this story, please click here.
RE[6]: Comment by hornett
by Valhalla on Fri 1st Oct 2010 22:29 UTC in reply to "RE[5]: Comment by hornett"
Valhalla
Member since:
2006-01-24

Dark Shikari doesn't care about "web video" per se, he's just interested in high quality.
If h264 becomes the 'web standard' he and other x264 devs will stand to make more money from licencing x264 then they would otherwise.

so be it. won't chance the fact that by constantly accusing DS of bias, you're doing nothing but actually showing *your* bias)

Again, he has money to make on the success/dominance of h264, I am always VERY sceptical when people with a monetary interest claim their technology is much better than the competition.

Oh, and regarding using a motion picture... here's what Dark himself said (yes, it's advisable to read all the comments to his blog post):
"That video is taken on 65mm film by a camera that costs more than most houses — it is higher quality than almost any image taken by any “photo camera”. I highly doubt your average Creative Commons images even have a quarter the detail that an Arriflex 765 can take."

Well, A) that is his words B) it is ONE image, hardly makes for a serious study by any measurement. Also, I wonder what codec the video was encoded in, if it was in h264 then it would seem logical that in reencoding a still frame from it x264 would be favored since it uses the same compression technique as the source (note, I do not know what codec was used for the original video from which the frame was captured, I am just assuming it was h264, I may be dead wrong here). Also, why did he use jpgcrush on the jpg image? It seems to me that he wanted to be able to use a higher quality setting for the jpg while keeping it at the same file size as the webp file. I don't know exactly what jpgcrush does (other than optimizing the file size obviously) but I guess the added compression time from using that is why it's not normally part of standard jpeg compression and chances are the same techniques used in jpgcrush could be applied to a webp image to make it smaller while keeping the same quality. Again, this test smells tailored to me. Again, I will await a serious study using a wide range of non-lossy images.

Reply Parent Score: 3