7 ms·
The following blog posts from an x264 developer point out problems with the spec, including discrepancies with the implementation and chunks of cut&pasted C cod
by othermaciej 16y ago
The following blog posts from an x264 developer point out problems with the spec, including discrepancies with the implementation and chunks of cut&pasted C code:
http://x264dev.multimedia.cx/archives/377 http://x264dev.multimedia.cx/archives/377
http://x264dev.multimedia.cx/archives/486 http://x264dev.multimedia.cx/archives/486
Unfortunately, the VP8 Internet-Draft seems to be just a plaintext version of the bitstream guide complained about above, including the disclaimer that the implementation takes precedence and the snippets of C code. It would need a lot of work to actually be published as any kind of standard, this perhaps being a reason Google is going the individual submission RFC route.
- ZeroGravitas 16y agoInterestingly the latest draft of the IETF's Opus codec spec actually contains source code, zipped and then base64 encoded: http://www.ietf.org/mail-archive/web/codec/current/msg02022.html http://www.ietf.org/mail-archive/web/codec/current/msg02022....