1. 07 Dec, 2015 1 commit
  2. 04 Dec, 2015 1 commit
    • Angie Chiang's avatar
      comment out range_check of fdct in dct.c · 08b157da
      Angie Chiang authored
      The range_check is not used because the bit range
      in fdct# is not correct. Since we are going to merge in a new version
      of fdct# from nextgenv2, we won't fix the incorrect bit range now.
      
      Change-Id: I54f27a6507f27bf475af302b4dbedc71c5385118
      08b157da
  3. 03 Dec, 2015 1 commit
    • hui su's avatar
      Remove palette from VP10 · 5d3327e8
      hui su authored
      Store it in nextgenv2 for now.
      
      Change-Id: Iab0af0e15246758e3b6e8bde4a74b13c410576fc
      5d3327e8
  4. 19 Nov, 2015 1 commit
  5. 09 Nov, 2015 1 commit
    • Johann's avatar
      Release v1.5.0 · cbecf57f
      Johann authored
      Javan Whistling Duck release.
      
      Change-Id: If44c9ca16a8188b68759325fbacc771365cb4af8
      cbecf57f
  6. 06 Nov, 2015 1 commit
  7. 27 Oct, 2015 4 commits
  8. 24 Oct, 2015 1 commit
  9. 23 Oct, 2015 1 commit
    • Jingning Han's avatar
      Use explicit block position in foreach_transformed_block · caeb10bf
      Jingning Han authored
      Add the row and column index to the argument list of unit functions
      called by foreach_transformed_block wrapper. This avoids the
      repeated internal parsing according to the block index.
      
      Change-Id: Ie7508acdac0b498487564639bc5cc6378a8a0df7
      caeb10bf
  10. 21 Oct, 2015 2 commits
  11. 20 Oct, 2015 2 commits
    • Ronald S. Bultje's avatar
      vp10: disallow coding zero-sized tiles-in-frame/frames-in-superframe. · dec4405c
      Ronald S. Bultje authored
      See issue 1088.
      
      Change-Id: Icb15d33b4e316add848f210b50cbccd7c7847207
      dec4405c
    • Geza Lore's avatar
      Optimize vpx_quantize_{b,b_32x32} assembler. · 9cfba09a
      Geza Lore authored
      Added optimization of the 8 bit assembly quantizer routines. This makes
      these functions up to 100% faster, depending on encoding parameters.
      
      This patch maskes the encoder faster in both the high bitdepth and 8bit
      configurations. In the high bitdepth configuration, it effects profile 0
      only.
      
      Based on my profiling using 1080p input the net gain is between 1-3% for
      the 8 bit config, and around 2.5-4.5% for the high bitdepth config,
      depending on target bitrate. The difference between the 8 bit and high
      bitdepth configurations for the same encoder run is reduced by 1% in all
      cases I have profiled.
      
      Change-Id: I86714a6b7364da20cd468cd784247009663a5140
      9cfba09a
  12. 19 Oct, 2015 1 commit
  13. 16 Oct, 2015 6 commits
    • Ronald S. Bultje's avatar
      vp10: per-segment lossless coding. · 60c58b52
      Ronald S. Bultje authored
      Some more testing of this patch would probably be useful, but I
      think the basics of it should work fine now.
      
      See issue 1035.
      
      Change-Id: I4a36d58f671c5391cb09d564581784a00ed26245
      60c58b52
    • Ronald S. Bultje's avatar
      vp10: add extended-intra prediction edges experiment. · c7dc1d78
      Ronald S. Bultje authored
      This experiment allows using full above/right edges for all transform
      sizes whenever available (for d45/d63), and adds bottom/left edges for
      d207.
      
      See issue 1043.
      
      Change-Id: I5cf7f345e783e8539bb6b6d2c9972fb1d6d0a78b
      c7dc1d78
    • Ronald S. Bultje's avatar
      vp10: allow forward updates for keyframe y intra mode probabilities. · 1eb51a20
      Ronald S. Bultje authored
      See issue 1040 point 5.
      
      Change-Id: I51a70b9eade39efba392a1457bd70a3c515525cb
      1eb51a20
    • Ronald S. Bultje's avatar
      vp10: merge keyframe/interframe uvintramode/partition probabilities. · d8f3bb18
      Ronald S. Bultje authored
      This has various benefits:
      - simplify implementations because we don't have to switch between
        multiple probability tables depending on frametype
      - allows fw subexp and bw adaptivity for partitions/uvmode in keyframes
      
      See issue 1040 point 5.
      
      Change-Id: Ia566aa2863252d130cee9deedcf123bb2a0d3765
      d8f3bb18
    • Ronald S. Bultje's avatar
      vp10: make segmentation probs use generic probability model. · 6e5a1165
      Ronald S. Bultje authored
      Locate them (code-wise) in frame_context, and have them be updated
      as any other probability using the subexp forward and adaptive bw
      updates.
      
      See issue 1040 point 1.
      
      TODOs:
      - real-world default probabilities
      - why is counts sometimes NULL in the decoder? Does that mean bw
        adaptivity updates only work on some frames? (I haven't looked
        very closely yet, maybe this is a red herring.)
      
      Change-Id: I23b57b4e5e7574b75f16eb64823b29c22fbab42e
      6e5a1165
    • hui su's avatar
      VP10: some changes to palette mode · 17c817ad
      hui su authored
      Account for rounding in distortion calculation in k-means;
      carry out rounding before duplicates removal of base colors;
      replace numbers with macros;
      use prefix increment.
      
      Slight coding gain (<0.1%) on screen_content testset.
      
      Change-Id: Ie8bd241266da6b82c7b2874befc3a0c72b4fcd8c
      17c817ad
  14. 15 Oct, 2015 3 commits
  15. 13 Oct, 2015 1 commit
  16. 12 Oct, 2015 6 commits
  17. 06 Oct, 2015 4 commits
    • Ronald S. Bultje's avatar
      vp10: use subexp probability updates for MV probs. · 177e7b53
      Ronald S. Bultje authored
      See issue 1040 point 2.
      
      Change-Id: I0b37fe74be764610696620f1fe296dc74e4806d7
      177e7b53
    • Ronald S. Bultje's avatar
      vp10: skip unreachable cat6 token extrabits. · 3461e8ce
      Ronald S. Bultje authored
      We have historically added new bits to cat6 whenever we added a new
      transform size (or bitdepth, for that matter). However, we have
      always coded these new bits regardless of the actual transform size,
      which means that for smaller transforms, we code bits that cannot
      possibly be set. The coding (quality) impact of this is negligible,
      but the bigger issue is that this allows creating bitstreams with
      coefficient values that are nonsensible and can cause int overflows,
      which then de facto become part of the bitstream spec. By not coding
      these bits, we remove this possibility.
      
      See issue 1065.
      
      Change-Id: Ib3186eca2df6a7a15ddc60c8b55af182aadd964d
      3461e8ce
    • Ronald S. Bultje's avatar
      vp10: use superframe marker index/size mechanism for tile size. · 7460798b
      Ronald S. Bultje authored
      See issue 1042. Should provide slight bitstream savings in most cases
      where tiles are being used.
      
      Change-Id: Ie2808cf8ef30b3efe50804396900c4d63a3fa026
      7460798b
    • Ronald S. Bultje's avatar
      vp10: extend range for delta Q values. · 612104bb
      Ronald S. Bultje authored
      See issue 1051. 6 bits is fairly arbitrary but at least allows writing
      delta Q values that are fairly normal in other codecs. I can extend to
      8 if people want full range, although I personally don't have any need
      for that.
      
      Change-Id: I0a5a7c3d9b8eb3de4418430ab0e925d4a08cd7a0
      612104bb
  18. 02 Oct, 2015 1 commit
  19. 26 Sep, 2015 2 commits
    • Ronald S. Bultje's avatar
      vp9/10: improve support for render_width/height. · 812945a8
      Ronald S. Bultje authored
      In the decoder, map this to the output variable vpx_image_t.r_w/h.
      This is intended as an improved version of VP9D_GET_DISPLAY_SIZE,
      which doesn't work with parallel frame decoding. In the encoder,
      map this to a codec control func (VP9E_SET_RENDER_SIZE) that takes
      a w/h pair argument in a int[2] (identical to VP9D_GET_DISPLAY_SIZE).
      
      Also add render_size to the encoder_param_get_to_decoder unit test.
      
      See issue 1030.
      
      Change-Id: I12124c13602d832bf4c44090db08c1009c94c7e8
      812945a8
    • Ronald S. Bultje's avatar
      Rename display_{size,width,height} to render_*. · 36ffe644
      Ronald S. Bultje authored
      The name "display_*" (or "d_*") is used for non-compatible information
      (that is, the cropped frame dimensions in pixels, as opposed to the
      intended screen rendering surface size). Therefore, continuing to use
      display_* would be confusing to end users. Instead, rename the field
      to render_*, so that struct vpx_image can include it.
      
      Change-Id: Iab8d2eae96492b71c4ea60c4bce8121cb2a1fe2d
      36ffe644