{"id":2971,"date":"2010-10-26T08:05:17","date_gmt":"2010-10-26T15:05:17","guid":{"rendered":"http:\/\/multimedia.cx\/eggs\/?p=2971"},"modified":"2010-10-26T08:05:17","modified_gmt":"2010-10-26T15:05:17","slug":"technically-correct-vp8-encoding","status":"publish","type":"post","link":"https:\/\/multimedia.cx\/eggs\/technically-correct-vp8-encoding\/","title":{"rendered":"Technically Correct VP8 Encoding"},"content":{"rendered":"

I know people are anxious to see what happens next with my toy VP8 encoder. First and foremost, I corrected the encoder’s DC prediction. A lot of rules govern that mode and if you don’t have it right, error cascades through the image. Now the encoder and decoder both agree on every fine detail of the bitstream syntax and rendering thereof. It still encodes to a neo-impressionist mosaic piece, but at least I’ve ironed the bugs out of this phase:<\/p>\n


\n\"\"
\n<\/center><\/p>\n

I also made it possible to adjust the quantization levels inside the encoder. This means that I’m finally getting some compression out of the thing, vs. the original approach of hardcoding the minimum quantizers.<\/p>\n","protected":false},"excerpt":{"rendered":"

My VP8 encoder is now doing the right thing, just poorly<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[219],"tags":[],"class_list":["post-2971","post","type-post","status-publish","format-standard","hentry","category-vp8"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t