Is VP8 a Duck codec?

There’s a blog out there with posts dedicated to the history of On2 (née Duck). And one particular post (archived version) brought an unsettling thought that refuses to leave me. Does VP8 belong to Duck or Baidu (yes, I’ll keep calling this company by value) codecs?

Arguments for Duck theory:

  1. it was released in 2008, before acquisition (which happened in 2010);
  2. it can be seen as an improvement of VP7, which is definitely a Duck codec;
  3. its documentation is as lacking as for the previous codecs.

Arguments for Baidu theory:

  1. it became famous after the company was bought and the codec was open-sourced;
  2. as a follow-up from the previous item, there is an open-source library for decoding and encoding it (I think the previous source dump had an encoder just for TMRT and maybe it was an oversight);
  3. it has its own ecosystem (all previous codecs were stored in AVI, this one uses WebMKV);
  4. I don’t have to implement it in NihAV (because I wanted nihav_duck crate to contain decoders for all Duck formats and if VP8 is not really a Duck codec I don’t have to do anything).

So, what do you think?

5 Responses to “Is VP8 a Duck codec?”

  1. lu says:

    If it quacks like a duck and moves like a duck it is …

  2. Kostya says:

    …Quack.264 codec?

  3. Peter says:

    Regardless of the company title, it would have been much the same people working on the code.

  4. Kostya says:

    True, but the management matters more in this case (and always in management eyes). Either it’s a typical Duck codec for showcasing what they can rip off (and license it to somebody else) or it’s a Baidu codec made exclusively for Baidu purposes (and thus I should not care about it).

  5. […] a recent post titled Is VP8 a Duck codec? the majority (both commenters) decided it’s a Duck codec after all so I’ll have to […]