Recherche avancée

Sur d’autres sites (3960)

• Vedanti and Max Sound vs. Google

  14 août 2014, par Multimedia Mike — Legal/Ethical

  Vedanti Systems Limited (VSL) and Max Sound Coporation filed a lawsuit against Google recently. Ordinarily, I wouldn’t care about corporate legal battles. However, this one interests me because it’s multimedia-related. I’m curious to know how coding technology patents might hold up in a real court case.

  Here’s the most entertaining complaint in the lawsuit :

  Despite Google’s well-publicized Code of Conduct — “Don’t be Evil” — which it explains is “about doing the right thing,” “following the law,” and “acting honorably,” Google, in fact, has an established pattern of conduct which is the exact opposite of its claimed piety.

  I wonder if this is the first known case in which Google has been sued over its long-obsoleted “Don’t be evil” mantra ?

  Researching The Plaintiffs
  
  I think I made a mistake by assuming this lawsuit might have merit. My first order of business was to see what the plaintiff organizations have produced. I have a strong feeling that these might be run of the mill patent trolls.

  VSL currently has a blank web page. Further, the Wayback Machine only has pages reaching back to 2011. The earliest page lists these claims against a plain black background (I’ve highlighted some of the more boisterous claims and the passages that make it appear that Vedanti doesn’t actually produce anything but is strictly an IP organization) :

  The inventions key :
  The patent and software reduced any data content, without compressing, up to a 97% total reduction of the data which also produces a lossless result. This physics based invention is often called the Holy Grail.

  Vedanti Systems Intellectual Property
  Our strategic IP portfolio is granted in all of the world’s largest technology development and use countries. A major value indemnification of our licensee products is the early date of invention filing and subsequent Issue. Vedanti IP has an intrinsic 20 year patent protection and valuation in royalties and licensing. The original data transmission art has no prior art against it.

  Vedanti Systems invented among other firsts, The Slice and Partitioning of Macroblocks within a RGB Tri level region in a frame to select or not, the pixel.

  Vedanti Systems invention is used in nearly every wireless chipset and handset in the world

  Our original pixel selection system revolutionized wireless handset communications. An example of this system “Slice” and “Macroblock Partitioning” is used throughout Satellite channel expansion, Wireless partitioning, Telecom – Video Conferencing, Surveillance Cameras, and 2010 developing Media applications.

  Vedanti Systems is a Semiconductor based software, applications, and IP Continuations Intellectual Property company.

  Let’s move onto the other plaintiff, Max Sound. They have a significantly more substantive website. They also have an Android app named Spins HD Audio, which appears to be little more than a music player based on the screenshots.

  Max Sound also has a stock ticker symbol : MAXD. Something clicked into place when I looked up their ticker symbol : While worth only a few pennies, it was worth a few more pennies after this lawsuit was announced, which might be one of the motivations behind the lawsuit.

  Here’s a trick I learned when I was looking for a new tech job last year : When I first look at a company’s website and am trying to figure out what they really do, I head straight to their jobs/careers page. A lot of corporate websites have way too much blathering corporatese that can be tough to cut through. But when I see what mix of talent and specific skills they are hoping to hire, that gives me a much better portrait of what the company does.

  The reason I bring this up is because this tech company doesn’t seem to have jobs/careers page.

  The Lawsuit
  The core complaint centers around Patent 7974339 : Optimized data transmission system and method. It was filed in July 2004 (or possibly as early as January 2002), issued in July 2011, and assigned (purchased ?) by Vedanti in May 2012. The lawsuit alleges that nearly everything Google has ever produced (or, more accurately, purchased) leverages the patented technology.

  The patent itself has 5 drawings. If you’ve ever seen a multimedia codec patent, or any whitepaper on a multimedia codec, you’ve seen these graphs before. E.g., “Raw pixels come in here -> some analysis happens here -> more analysis happens over here -> entropy coding -> final bitstream”. The text of a patent document isn’t meant to be particularly useful. I’ve tried to understand this stuff before and it never goes well. Skimming the text, I just see a blur of the words data, transmission, pixel, and matrix.

  So I read the complaint to try to figure out what this is all about. To summarize the storyline as narrated by the lawsuit, some inventors were unhappy with the state of video compression in 2001 and endeavored to create something better. So they did, and called it the VSL codec. This codec is so far undocumented on the MultimediaWiki, so it probably has yet to be seen “in the wild”. Good luck finding hard technical data on it now since searches for “VSL codec” are overwhelmed by articles about this lawsuit. Also, the original codec probably wasn’t called VSL because VSL is apparently an IP organization formed much later.

  Then, the protagonists of the lawsuit patented the codec. Then, years later, Google wanted to purchase a video codec that they could open source and use to supplant H.264.

  The complaint goes on to allege that in 2010, Google specifically contacted VSL to possibly license or acquire this mysterious VSL technology. Google was allegedly allowed to study the technology, eventually decided not to continue discussions, and shipped back the proprietary materials.

  Here’s where things get weird. When Google shipped back the materials, they allegedly shipped back a bunch of Post-It notes. The notes are alleged to contain a ton of incriminating evidence. The lawsuit claims that the notes contained such tidbits as :

  • Google was concerned that its infringement could be considered “recklessness” (the standard applicable to willful infringement) ;
  • Google personnel should “try” to destroy incriminating emails ;
  • Google should consider a “design around” because it was facing a “risk of litigation.”

  Actually, given Google’s acquisition of On2, I can totally believe that last one (On2’s codecs have famously contained a lot of weirdness which is commonly suspected to be attributable to designing around known patents).

  Anyway, a lot of this case seems to hinge on the authenticity of these Post-It notes :

  “65. The Post-It notes are unequivocal evidence of Google’s knowledge of the ’339 Patent and infringement by Defendants”

  I wish I could find a stock photo of a stack of Post-It notes in an evidence bag.

  I’ve worked at big technology companies. Big tech companies these days are very diligent about indoctrinating employees about IP liability issues. The reason this Post-It situation strikes me as odd is because the alleged contents of the notes basically outline everything the corporate lawyers tell you NOT to do.

  Analysis
  I’m trying to determine what specific algorithms and coding techniques. I guess I was expecting to see a specific claim that, “Our patent outlines this specific coding technique and here is unequivocal proof that Google A) uses the same technique, and B) specifically did so after looking at our patent.” I didn’t find that (well, a bit of part B, c.f., the Post-It note debacle), but maybe that’s not how these patent lawsuits operate. I’ve never kept up before.

  Maybe it’s just a patent troll. Maybe it’s for the stock bump. I’m expecting to see pump-n-dump stock spam featuring the stock symbol MAXD anytime now.

  I’ve never been interested in following a lawsuit case carefully before. I suddenly find myself wondering if I can subscribe to the RSS feed for this case ? Too much to hope for. But I found this item through Pando and maybe they’ll stay on top of it.

• How to create a widget – Introducing the Piwik Platform

  4 septembre 2014, par Thomas Steur — Development

  This is the next post of our blog series where we introduce the capabilities of the Piwik platform (our previous post was How to create a scheduled task in Piwik). This time you’ll learn how to create a new widget. For this tutorial you will need to have basic knowledge of PHP.

  What is a widget in Piwik ?

  Widgets can be added to your dashboards or exported via a URL to embed it on any page. Most widgets in Piwik represent a report but a widget can display anything. For instance a RSS feed of your corporate news. If you prefer to have most of your business relevant data in one dashboard why not display the number of offline sales, the latest stock price, or other key metrics together with your analytics data ?

  Getting started

  In this series of posts, we assume that you have already set up your development environment. If not, visit the Piwik Developer Zone where you’ll find the tutorial Setting up Piwik.

  To summarize the things you have to do to get setup :

  • Install Piwik (for instance via git).
  • Activate the developer mode : ./console development:enable --full.
  • Generate a plugin : ./console generate:plugin --name="MyWidgetPlugin". There should now be a folder plugins/MyWidgetPlugin.
  • And activate the created plugin under Settings => Plugins.

  Let’s start creating a widget

  We start by using the Piwik Console to create a widget template :

  ./console generate:widget

  The command will ask you to enter the name of the plugin the widget should belong to. I will simply use the above chosen plugin name “MyWidgetPlugin”. It will ask you for a widget category as well. You can select any existing category, for instance “Visitors”, “Live !” or “Actions”, or you can define a new category, for instance your company name. There should now be a file plugins/MyWidgetPlugin/Widgets.php which contains already some examples to get you started easily :

  class Widgets extends \Piwik\Plugin\Widgets
  {
      /**
       * Here you can define the category the widget belongs to. You can reuse any existing widget category or define your own category.
       * @var string
       */
      protected $category = 'ExampleCompany';
   
      /**
       * Here you can add one or multiple widgets. You can add a widget by calling the method "addWidget()" and pass the name of the widget as well as a method name that should be called to render the widget. The method can be defined either directly here in this widget class or in the controller in case you want to reuse the same action for instance in the menu etc.
       */
      protected function init()
      {
          $this->addWidget('Example Widget Name', $method = 'myExampleWidget');
          $this->addWidget('Example Widget 2',    $method = 'myExampleWidget', $params = array('myparam' => 'myvalue'));
      }
   
      /**
       * This method renders a widget as defined in "init()". It's on you how to generate the content of the widget. As long as you return a string everything is fine. You can use for instance a "Piwik\View" to render a twig template. In such a case don't forget to create a twig template (eg. myViewTemplate.twig) in the "templates" directory of your plugin.
       *
       * @return string
       */
      public function myExampleWidget()
      {
          $view = new View('@MyWidgetPlugin/myViewTemplate');
          return $view->render();
      }
  }
  Télécharger

  As you might have noticed in the generated template we put emphasis on adding comments to explain you directly how to continue and where to get more information. Ideally this saves you some time and you don’t even have to search for more information on our developer pages. The category is defined in the property $category and can be changed at any time. Starting from Piwik 2.6.0 the generator will directly create a translation key if necessary to make it easy to translate the category into any language. Translations will be a topic in one of our future posts until then you can explore this feature on our Internationalization guide.

  A simple example

  We can define one or multiple widgets in the init method by calling addWidget($widgetName, $methodName). To do so we define the name of a widget which will be seen by your users as well as the name of the method that shall render the widget.

  protected $category = 'Example Company';
  
  
  
  public function init()
  
  {
  
      // Registers a widget named 'News' under the category 'Example Company'. 
  
      // The method 'myCorporateNews' will be used to render the widget.
  
      $this->addWidget('News', $method = 'myCorporateNews'); 
  
  }
  
  
  
  public function myCorporateNews()
  
  {
  
      return file_get_contents('http://example.com/news');
  
  }

  This example would display the content of the specified URL within the widget as defined in the method myCorporateNews. It’s on you how to generate the content of the widget. Any string returned by this method will be displayed within the widget. You can use for example a View to render a Twig template. For simplification we are fetching the content from another site. A more complex version would cache this content for faster performance. Caching and views will be covered in one of our future posts as well.

  

  Did you know ? To make your life as a developer as stress-free as possible the platform checks whether the registered method actually exists and whether the method is public. If not, Piwik will display a notification in the UI and advice you with the next step.

  Checking permissions

  Often you do not want to have the content of a widget visible to everyone. You can check for permissions by using one of our many convenient methods which all start with \Piwik\Piwik::checkUser*. Just to introduce some of them :

  // Make sure the current user has super user access
  
  \Piwik\Piwik::checkUserHasSuperUserAccess(); 
  
  
  
  // Make sure the current user is logged in and not anonymous
  
  \Piwik\Piwik::checkUserIsNotAnonymous(); 

  And here is an example how you can use it within your widget :

  public function myCorporateNews()
  
  {
  
      // Make sure there is an idSite URL parameter
  
      $idSite = Common::getRequestVar('idSite', null, 'int');
  
  
  
      // Make sure the user has at least view access for the specified site. This is useful if you want to display data that is related to the specified site.
  
      Piwik::checkUserHasViewAccess($idSite); 
  
  
  
      $siteUrl = \Piwik\Site::getMainUrlFor($idSite);
  
  
  
      return file_get_contents($siteUrl . '/news');
  
  }

  In case any condition is not met an exception will be thrown and an error message will be presented to the user explaining that he does not have enough permissions. You’ll find the documentation for those methods in the Piwik class reference.

  How to test a widget

  After you have created your widgets you are surely wondering how to test it. First, you should write a unit or integration test which we will cover in one of our future blog posts. Just one hint : You can use the command ./console generate:test to create a test. To manually test a widget you can add a widget to a dashboard or export it.

  Publishing your Plugin on the Marketplace

  In case you want to share your widgets with other Piwik users you can do this by pushing your plugin to a public GitHub repository and creating a tag. Easy as that. Read more about how to distribute a plugin.

  Advanced features

  Isn’t it easy to create a widget ? We never even created a file ! Of course, based on our API design principle “The complexity of our API should never exceed the complexity of your use case.” you can accomplish more if you want : You can clarify parameters that will be passed to your widget, you can create a method in the Controller instead of the Widget class to make the same method also reusable for adding it to the menu, you can assign different categories to different widgets, you can remove any widgets that were added by the Piwik core or other plugins and more.

  Would you like to know more about widgets ? Go to our Widgets class reference in the Piwik Developer Zone.

  If you have any feedback regarding our APIs or our guides in the Developer Zone feel free to send it to us.

• Revision a49d80bfc8 : Squash commits from master to playground Moving RD-opt related code from vp9_en

  26 juin 2014, par Yue Chen

  Changed Paths :
   Modify /build/make/gen_msvs_proj.sh

  
   Modify /build/make/gen_msvs_vcxproj.sh

  
   Modify /build/make/iosbuild.sh

  
   Modify /examples/vp9_spatial_svc_encoder.c

  
   Modify /test/decode_test_driver.cc

  
   Modify /test/decode_test_driver.h

  
   Add /test/invalid_file_test.cc

  
   Modify /test/svc_test.cc

  
   Modify /test/test-data.sha1

  
   Modify /test/test.mk

  
   Modify /test/test_vectors.cc

  
   Add /test/user_priv_test.cc

  
   Add /third_party/libmkv/EbmlIDs.h

  
   Add /third_party/libmkv/EbmlWriter.c

  
   Add /third_party/libmkv/EbmlWriter.h

  
   Modify /vp8/common/rtcd_defs.pl

  
   Modify /vp8/encoder/x86/quantize_sse2.c

  
   Delete /vp8/encoder/x86/quantize_sse4.asm

  
   Add /vp8/encoder/x86/quantize_sse4.c

  
   Modify /vp8/vp8cx.mk

  
   Modify /vp9/common/arm/neon/vp9_convolve_neon.c

  
   Modify /vp9/common/arm/neon/vp9_loopfilter_16_neon.c

  
   Modify /vp9/common/vp9_alloccommon.c

  
   Modify /vp9/common/vp9_alloccommon.h

  
   Modify /vp9/common/vp9_convolve.c

  
   Modify /vp9/common/vp9_mvref_common.c

  
   Modify /vp9/common/vp9_mvref_common.h

  
   Modify /vp9/common/vp9_quant_common.c

  
   Modify /vp9/common/vp9_quant_common.h

  
   Modify /vp9/common/vp9_scale.h

  
   Modify /vp9/decoder/vp9_decodeframe.c

  
   Modify /vp9/decoder/vp9_decoder.c

  
   Modify /vp9/decoder/vp9_dthread.h

  
   Modify /vp9/decoder/vp9_read_bit_buffer.c

  
   Modify /vp9/encoder/vp9_bitstream.c

  
   Modify /vp9/encoder/vp9_block.h

  
   Modify /vp9/encoder/vp9_denoiser.c

  
   Modify /vp9/encoder/vp9_denoiser.h

  
   Modify /vp9/encoder/vp9_encodeframe.c

  
   Modify /vp9/encoder/vp9_encoder.c

  
   Modify /vp9/encoder/vp9_encoder.h

  
   Modify /vp9/encoder/vp9_firstpass.c

  
   Modify /vp9/encoder/vp9_firstpass.h

  
   Modify /vp9/encoder/vp9_lookahead.c

  
   Modify /vp9/encoder/vp9_lookahead.h

  
   Modify /vp9/encoder/vp9_pickmode.c

  
   Modify /vp9/encoder/vp9_pickmode.h

  
   Modify /vp9/encoder/vp9_ratectrl.c

  
   Modify /vp9/encoder/vp9_ratectrl.h

  
   Modify /vp9/encoder/vp9_rdopt.c

  
   Modify /vp9/encoder/vp9_rdopt.h

  
   Modify /vp9/encoder/vp9_speed_features.c

  
   Modify /vp9/encoder/vp9_speed_features.h

  
   Modify /vp9/encoder/vp9_svc_layercontext.c

  
   Modify /vp9/encoder/vp9_svc_layercontext.h

  
   Modify /vp9/vp9_cx_iface.c

  
   Modify /vp9/vp9_dx_iface.c

  
   Modify /vp9/vp9cx.mk

  
   Modify /vpx/src/svc_encodeframe.c

  
   Modify /vpx/svc_context.h

  
  
  Squash commits from master to playground

  Moving RD-opt related code from vp9_encoder.h to vp9_rdopt.h.

  Squashed-Change-Id : I8fab776c8801e19d3f5027ed55a6aa69eee951de

  gen_msvs_proj : fix in tree configure under cygwin

  strip trailing ’/’ from paths, this is later converted to ’\’ which
  causes execution errors for obj_int_extract/yasm. vs10+ wasn’t affected
  by this issue, but make the same change for consistency.

  gen_msvs_proj :
  + add missing ’"’ to obj_int_extract call
  unlike gen_msvs_vcproj, the block is duplicated
  missed in : 1e3d9b9 build/msvs : fix builds in source dirs with spaces

  Squashed-Change-Id : I76208e6cdc66dc5a0a7ffa8aa1edbefe31e4b130

  Improve vp9_rb_bytes_read

  Squashed-Change-Id : I69eba120eb3d8ec43b5552451c8a9bd009390795

  Removing decode_one_iter() function.

  When superframe index is available we completely rely on it and use frame
  size values from the index.

  Squashed-Change-Id : I0011d08b223303a8b912c2bcc8a02b74d0426ee0

  iosbuild.sh : Add vpx_config.h and vpx_version.h to VPX.framework.

   Rename build_targets to build_framework
   Add functions for creating the vpx_config shim and obtaining
  preproc symbols.

  Squashed-Change-Id : Ieca6938b9779077eefa26bf4cfee64286d1840b0

  Implemented vp9_denoiser_alloc,free()

  Squashed-Change-Id : I79eba79f7c52eec19ef2356278597e06620d5e27

  Update running avg for VP9 denoiser

  Squashed-Change-Id : I9577d648542064052795bf5770428fbd5c276b7b

  Changed buf_2ds in vp9 denoiser to YV12 buffers

  Changed alloc, free, and running average code as necessary.

  Squashed-Change-Id : Ifc4d9ccca462164214019963b3768a457791b9c1

  sse4 regular quantize

  Squashed-Change-Id : Ibd95df0adf9cc9143006ee9032b4cb2ebfd5dd1b

  Modify non-rd intra mode checking

  Speed 6 uses small tx size, namely 8x8. max_intra_bsize needs to
  be modified accordingly to ensure valid intra mode checking.
  Borg test on RTC set showed an overall PSNR gain of 0.335% in speed
   6.

  This also changes speed -5 encoding by allowing DC_PRED checking
  for block32x32. Borg test on RTC set showed a slight PSNR gain of
  0.145%, and no noticeable speed change.

  Squashed-Change-Id : I1502978d8fbe265b3bb235db0f9c35ba0703cd45

  Implemented COPY_BLOCK case for vp9 denoiser

  Squashed-Change-Id : Ie89ad1e3aebbd474e1a0db69c1961b4d1ddcd33e

  Improved vp9 denoiser running avg update.

  Squashed-Change-Id : Ie0aa41fb7957755544321897b3bb2dd92f392027

  Separate rate-distortion modeling for DC and AC coefficients

  This is the first step to rework the rate-distortion modeling used
  in rtc coding mode. The overall goal is to make the modeling
  customized for the statistics encountered in the rtc coding.

  This commit makes encoder to perform rate-distortion modeling for
  DC and AC coefficients separately. No speed changes observed.
  The coding performance for pedestrian_area_1080p is largely
  improved :

  speed -5, from 79558 b/f, 37.871 dB -> 79598 b/f, 38.600 dB
  speed -6, from 79515 b/f, 37.822 dB -> 79544 b/f, 38.130 dB

  Overall performance for rtc set at speed -6 is improved by 0.67%.

  Squashed-Change-Id : I9153444567e5f75ccdcaac043c2365992c005c0c

  Add superframe support for frame parallel decoding.

  A superframe is a bunch of frames that bundled as one frame. It is mostly
  used to combine one or more non-displayable frames and one displayable frame.

  For frame parallel decoding, libvpx decoder will only support decoding one
  normal frame or a super frame with superframe index.

  If an application pass a superframe without superframe index or a chunk
  of displayable frames without superframe index to libvpx decoder, libvpx
  will not decode it in frame parallel mode. But libvpx decoder still could
  decode it in serial mode.

  Squashed-Change-Id : I04c9f2c828373d64e880a8c7bcade5307015ce35

  Fixes in VP9 alloc, free, and COPY_FRAME case

  Squashed-Change-Id : I1216f17e2206ef521fe219b6d72d8e41d1ba1147

  Remove labels from quantize

  Use break instead of goto for early exit. Unbreaks Visual Studio
  builds.

  Squashed-Change-Id : I96dee43a3c82145d4abe0d6a99af6e6e1a3991b5

  Added CFLAG for outputting vp9 denoised signal

  Squashed-Change-Id : Iab9b4e11cad927f3282e486c203564e1a658f377

  Allow key frame more flexibility in mode search

  This commit allows the key frame to search through more prediction
  modes and more flexible block sizes. No speed change observed. The
  coding performance for rtc set is improved by 1.7% for speed -5 and
  3.0% for speed -6.

  Squashed-Change-Id : Ifd1bc28558017851b210b4004f2d80838938bcc5

  VP9 denoiser bugfixes

  s/stdint.h/vpx\/vpx_int.h

  Added missing ’break ;’s

  Also included other minor changes, mostly cosmetic.

  Squashed-Change-Id : I852bba3e85e794f1d4af854c45c16a23a787e6a3

  Don’t return value for void functions

  Clears "warning : ’return’ with a value, in function returning void"

  Squashed-Change-Id : I93972610d67e243ec772a1021d2fdfcfc689c8c2

  Include type defines

  Clears error : unknown type name ’uint8_t’

  Squashed-Change-Id : I9b6eff66a5c69bc24aeaeb5ade29255a164ef0e2

  Validate error checking code in decoder.

  This patch adds a mechanism for insuring error checking on invalid files
  by creating a unit test that runs the decoder and tests that the error
  code matches what’s expected on each frame in the decoder.

  Disabled for now as this unit test will segfault with existing code.

  Squashed-Change-Id : I896f9686d9ebcbf027426933adfbea7b8c5d956e

  Introduce FrameWorker for decoding.

  When decoding in serial mode, there will be only
  one FrameWorker doing decoding. When decoding in
  parallel mode, there will be several FrameWorkers
  doing decoding in parallel.

  Squashed-Change-Id : If53fc5c49c7a0bf5e773f1ce7008b8a62fdae257

  Add back libmkv ebml writer files.

  Another project in ChromeOS is using these files. To make libvpx
  rolls simpler, add these files back unitl the other project removes
  the dependency.

  crbug.com/387246 tracking bug to remove dependency.

  Squashed-Change-Id : If9c197081c845c4a4e5c5488d4e0190380bcb1e4

  Added Test vector that tests more show existing frames.

  Squashed-Change-Id : I0ddd7dd55313ee62d231ed4b9040e08c3761b3fe

  fix peek_si to enable 1 byte show existing frames.

  The test for this is in test vector code ( show existing frames will
  fail ). I can’t check it in disabled as I’m changing the generic
  test code to do this :

  https://gerrit.chromium.org/gerrit/#/c/70569/

  Squashed-Change-Id : I5ab324f0cb7df06316a949af0f7fc089f4a3d466

  Fix bug in error handling that causes segfault

  See : https://code.google.com/p/chromium/issues/detail?id=362697

  The code properly catches an invalid stream but seg faults instead of
  returning an error due to a buffer not having been initialized. This
  code fixes that.

  Squashed-Change-Id : I695595e742cb08807e1dfb2f00bc097b3eae3a9b

  Revert 3 patches from Hangyu to get Chrome to build :

  Avoids failures :
  MSE_ClearKey/EncryptedMediaTest.Playback_VP9Video_WebM/0
  MSE_ClearKey_Prefixed/EncryptedMediaTest.Playback_VP9Video_WebM/0
  MSE_ExternalClearKey_Prefixed/EncryptedMediaTest.Playback_VP9Video_WebM/0
  MSE_ExternalClearKey/EncryptedMediaTest.Playback_VP9Video_WebM/0
  MSE_ExternalClearKeyDecryptOnly/EncryptedMediaTest.Playback_VP9Video_WebM/0
  MSE_ExternalClearKeyDecryptOnly_Prefixed/EncryptedMediaTest.Playback_VP9Video_We
  bM/0
  SRC_ExternalClearKey/EncryptedMediaTest.Playback_VP9Video_WebM/0
  SRC_ExternalClearKey_Prefixed/EncryptedMediaTest.Playback_VP9Video_WebM/0
  SRC_ClearKey_Prefixed/EncryptedMediaTest.Playback_VP9Video_WebM/0

  Patches are
  This reverts commit 9bc040859b0ca6869d31bc0efa223e8684eef37a
  This reverts commit 6f5aba069a2c7ffb293ddce70219a9ab4a037441
  This reverts commit 9bc040859b0ca6869d31bc0efa223e8684eef37a

  I1f250441 Revert "Refactor the vp9_get_frame code for frame parallel."
  Ibfdddce5 Revert "Delay decreasing reference count in frame-parallel
  decoding."
  I00ce6771 Revert "Introduce FrameWorker for decoding."

  Need better testing in libvpx for these commits

  Squashed-Change-Id : Ifa1f279b0cabf4b47c051ec26018f9301c1e130e

  error check vp9 superframe parsing

  This patch insures that the last byte of a chunk that contains a
  valid superframe marker byte, actually has a proper superframe index.
  If not it returns an error.

  As part of doing that the file : vp90-2-15-fuzz-flicker.webm now fails
  to decode properly and moves to the invalid file test from the test
  vector suite.

  Squashed-Change-Id : I5f1da7eb37282ec0c6394df5c73251a2df9c1744

  Remove unused vp9_init_quant_tables function

  This function is not effectively used, hence removed.

  Squashed-Change-Id : I2e8e48fa07c7518931690f3b04bae920cb360e49

  Actually skip blocks in skip segments in non-rd encoder.

  Copy split from macroblock to pick mode context so it doesn’t get lost.

  Squashed-Change-Id : Ie37aa12558dbe65c4f8076cf808250fffb7f27a8

  Add Check for Peek Stream validity to decoder test.

  Squashed-Change-Id : I9b745670a9f842582c47e6001dc77480b31fb6a1

  Allocate buffers based on correct chroma format

  The encoder currently allocates frame buffers before
  it establishes what the chroma sub-sampling factor is,
  always allocating based on the 4:4:4 format.

  This patch detects the chroma format as early as
  possible allowing the encoder to allocate buffers of
  the correct size.

  Future patches will change the encoder to allocate
  frame buffers on demand to further reduce the memory
  profile of the encoder and rationalize the buffer
  management in the encoder and decoder.

  Squashed-Change-Id : Ifd41dd96e67d0011719ba40fada0bae74f3a0d57

  Fork vp9_rd_pick_inter_mode_sb_seg_skip

  Squashed-Change-Id : I549868725b789f0f4f89828005a65972c20df888

  Switch active map implementation to segment based.

  Squashed-Change-Id : Ibb841a1fa4d08d164cf5461246ec290f582b1f80

  Experiment for mid group second arf.

  This patch implements a mechanism for inserting a second
  arf at the mid position of arf groups.

  It is currently disabled by default using the flag multi_arf_enabled.

  Results are currently down somewhat in initial testing if
  multi-arf is enabled. Most of the loss is attributable to the
  fact that code to preserve the previous golden frame
  (in the arf buffer) in cases where we are coding an overlay
  frame, is currently disabled in the multi-arf case.

  Squashed-Change-Id : I1d777318ca09f147db2e8c86d7315fe86168c865

  Clean out old CONFIG_MULTIPLE_ARF code.

  Remove the old experimental multi arf code that was under
  the flag CONFIG_MULTIPLE_ARF.

  Squashed-Change-Id : Ib24865abc11691d6ac8cb0434ada1da674368a61

  Fix some bugs in multi-arf

  Fix some bugs relating to the use of buffers
  in the overlay frames.

  Fix bug where a mid sequence overlay was
  propagating large partition and transform sizes into
  the subsequent frame because of :-
  sf->last_partitioning_redo_frequency > 1 and
  sf->tx_size_search_method == USE_LARGESTALL

  Squashed-Change-Id : Ibf9ef39a5a5150f8cbdd2c9275abb0316c67873a

  Further dual arf changes : multi_arf_allowed.

  Add multi_arf_allowed flag.
  Re-initialize buffer indices every kf.
  Add some const indicators.

  Squashed-Change-Id : If86c39153517c427182691d2d4d4b7e90594be71

  Fixed VP9 denoiser COPY_BLOCK case

  Now copies the src to the correct location in the running average buffer.

  Squashed-Change-Id : I9c83c96dc7a97f42c8df16ab4a9f18b733181f34

  Fix test on maximum downscaling limits

  There is a normative scaling range of (x1/2, x16)
  for VP9. This patch fixes the maximum downscaling
  tests that are applied in the convolve function.

  The code used a maximum downscaling limit of x1/5
  for historic reasons related to the scalable
  coding work. Since the downsampling in this
  application is non-normative it will revert to
  using a separate non-normative scaler.

  Squashed-Change-Id : Ide80ed712cee82fe5cb3c55076ac428295a6019f

  Add unit test to test user_priv parameter.

  Squashed-Change-Id : I6ba6171e43e0a43331ee0a7b698590b143979c44

  vp9 : check tile column count

  the max is 6. there are assumptions throughout the decode regarding
  this ; fixes a crash with a fuzzed bitstream

  $ zzuf -s 5861 -r 0.01:0.05 -b 6- \
  < vp90-2-00-quantizer-00.webm.ivf \
  | dd of=invalid-vp90-2-00-quantizer-00.webm.ivf.s5861_r01-05_b6-.ivf \
  bs=1 count=81883

  Squashed-Change-Id : I6af41bb34252e88bc156a4c27c80d505d45f5642

  Adjust arf Q limits with multi-arf.

  Adjust enforced minimum arf Q deltas for non primary arfs
  in the middle of an arf/gf group.

  Squashed-Change-Id : Ie8034ffb3ac00f887d74ae1586d4cac91d6cace2

  Dual ARF changes : Buffer index selection.

  Add indirection to the section of buffer indices.
  This is to help simplify things in the future if we
  have other codec features that switch indices.

  Limit the max GF interval for static sections to fit
  the gf_group structures.

  Squashed-Change-Id : I38310daaf23fd906004c0e8ee3e99e15570f84cb

  Reuse inter prediction result in real-time speed 6

  In real-time speed 6, no partition search is done. The inter
  prediction results got from picking mode can be reused in the
  following encoding process. A speed feature reuse_inter_pred_sby
  is added to only enable the resue in speed 6.

  This patch doesn’t change encoding result. RTC set tests showed
  that the encoding speed gain is 2% - 5%.

  Squashed-Change-Id : I3884780f64ef95dd8be10562926542528713b92c

  Add vp9_ prefix to mv_pred and setup_pred_block functions

  Make these two functions accessible by both RD and non-RD coding
  modes.

  Squashed-Change-Id : Iecb39dbf3d65436286ea3c7ffaa9920d0b3aff85

  Replace cpi->common with preset variable cm

  This commit replaces a few use cases of cpi->common with preset
  variable cm, to avoid unnecessary pointer fetch in the non-RD
  coding mode.

  Squashed-Change-Id : I4038f1c1a47373b8fd7bc5d69af61346103702f6

  [spatial svc]Implement lag in frames for spatial svc

  Squashed-Change-Id : I930dced169c9d53f8044d2754a04332138347409

  [spatial svc]Don’t skip motion search in first pass encoding

  Squashed-Change-Id : Ia6bcdaf5a5b80e68176f60d8d00e9b5cf3f9bfe3

  decode_test_driver : fix type size warning

  like vpx_codec_decode(), vpx_codec_peek_stream_info() takes an unsigned
  int, not size_t, parameter for buffer size

  Squashed-Change-Id : I4ce0e1fbbde461c2e1b8fcbaac3cd203ed707460

  decode_test_driver : check HasFailure() in RunLoop

  avoids unnecessary errors due to e.g., read (Next()) failures

  Squashed-Change-Id : I70b1d09766456f1c55367d98299b5abd7afff842

  Allow lossless breakout in non-rd mode decision.

  This is very helpful for large moving windows in screencasts.

  Squashed-Change-Id : I91b5f9acb133281ee85ccd8f843e6bae5cadefca

  Revert "Revert 3 patches from Hangyu to get Chrome to build :"

  This patch reverts the previous revert from Jim and also add a
  variable user_priv in the FrameWorker to save the user_priv
  passed from the application. In the decoder_get_frame function,
  the user_priv will be binded with the img. This change is needed
  or it will fail the unit test added here :
  https://gerrit.chromium.org/gerrit/#/c/70610/

  This reverts commit 9be46e4565f553460a1bbbf58d9f99067d3242ce.

  Squashed-Change-Id : I376d9a12ee196faffdf3c792b59e6137c56132c1

  test.mk : remove renamed file

  vp90-2-15-fuzz-flicker.webm was renamed in :
  c3db2d8 error check vp9 superframe parsing

  Squashed-Change-Id : I229dd6ca4c662802c457beea0f7b4128153a65dc

  vp9cx.mk : move avx c files outside of x86inc block

  same reasoning as :
  9f3a0db vp9_rtcd : correct avx2 references

  these are all intrinsics, so don’t depend on x86inc.asm

  Squashed-Change-Id : I915beaef318a28f64bfa5469e5efe90e4af5b827

  Dual arf : Name changes.

  Cosmetic patch only in response to comments on
  previous patches suggesting a couple of name changes
  for consistency and clarity.

  Squashed-Change-Id : Ida3a359b0d5755345660d304a7697a3a3686b2a3

  Make non-RD intra mode search txfm size dependent

  This commit fixes the potential issue in the non-RD mode decision
  flow that only checks part of the block to estimate the cost. It
  was due to the use of fixed transform size, in replacing the
  largest transform block size. This commit enables per transform
  block cost estimation of the intra prediction mode in the non-RD
  mode decision.

  Squashed-Change-Id : I14ff92065e193e3e731c2bbf7ec89db676f1e132

  Fix quality regression for multi arf off case.

  Bug introduced during multiple iterations on : I3831*

  gf_group->arf_update_idx[] cannot currently be used
  to select the arf buffer index if buffer flipping on overlays
  is enabled (still currently the case when multi arf OFF).

  Squashed-Change-Id : I4ce9ea08f1dd03ac3ad8b3e27375a91ee1d964dc

  Enable real-time version reference motion vector search

  This commit enables a fast reference motion vector search scheme.
  It checks the nearest top and left neighboring blocks to decide the
  most probable predicted motion vector. If it finds the two have
  the same motion vectors, it then skip finding exterior range for
  the second most probable motion vector, and correspondingly skips
  the check for NEARMV.

  The runtime of speed -5 goes down
  pedestrian at 1080p 29377 ms -> 27783 ms
  vidyo at 720p 11830 ms -> 10990 ms
  i.e., 6%-8% speed-up.

  For rtc set, the compression performance
  goes down by about -1.3% for both speed -5 and -6.

  Squashed-Change-Id : I2a7794fa99734f739f8b30519ad4dfd511ab91a5

  Add const mark to const values in non-RD coding mode

  Squashed-Change-Id : I65209fd1e06fc06833f6647cb028b414391a7017

  Change-Id : Ic0be67ac9ef48f64a8878a0b8f1b336f136bceac