1. 20 Feb, 2018 1 commit
    • Yaowu Xu's avatar
      Remove CONFIG_EXT_QM · e11b68d1
      Yaowu Xu authored
      The experiment is now fully adopted.
      
      Change-Id: I09960ed25defae98d1c3e5ee8bc93691f79677ec
      e11b68d1
  2. 05 Feb, 2018 1 commit
    • Maxym Dmytrychenko's avatar
      Adding config file parsing implementation · cc6e0e16
      Maxym Dmytrychenko authored
      Parameters from config file will be added at --cfg options location to
      be processed
      
      Config file example:
       #ignore comment
       ext-partition   : 1 #ignore as well
       codec           : av1
       psnr            : ON
      
      Note(s):
          - Config file is a simple text file
          - Comment starts with hash(#)
            Can be full line or part of the line, after hash(#) details are
      ignored
          - Format: field : value
            colon(:) as delimeter, otherwise full line will be ignored
            Space(s) and tab(s) can be used, not inside field
          - long names for field are prefered
             existing --long_name option format
          - "no value" fields should contain ON as value
      
      Example of usage:
          aomenc --cfg=some.cfg src_filename
      
      Configurations support matrix:
      enable-ext-partition         : done
      enable-loop-restoration      : wip
      enable-deblocking            : wip
      ...
      
      Change-Id: Iad867c5d2da64271cdafa825c89f7d6444582f61
      cc6e0e16
  3. 31 Jan, 2018 1 commit
  4. 29 Jan, 2018 1 commit
  5. 24 Jan, 2018 2 commits
  6. 23 Jan, 2018 3 commits
    • Tom Finegan's avatar
      Revert "add scalability experiment" · 8695e987
      Tom Finegan authored
      This reverts commit 2eeadab1.
      
      Reason for revert: Did not address final review comments before landing.
      
      Change-Id: I29089767857bd20b3a3e42322e3887fb7027559d
      8695e987
    • Soo-Chul Han's avatar
      add scalability experiment · 2eeadab1
      Soo-Chul Han authored
      configure:  --enable-experimental --enable-scalability
      
      New applications:  scalable_encoder, scalable_decoder
      
      scalable_encoder:
        * Encodes inputs as 2-layer (same size) stream
        * Encodes as obu file (OBU_NO_IVF must be enabled)
        * Base layer encoded in IPPPP where P's reference
          only the previous (in time) base layer
        * Enhancement layer encoded using its base layer as
          sole reference frame
        * Base layer encoded with fixed high QP
        * Enhancement layer encoded with fixed low QP
      
      scalable_decoder:
        * Able to decode scalable stream generated by
          scalable_encoder
        * Able to decode any single-layer stream encoded
          by aomenc
        * Outputs base layer as out_lyr0.yuv, and enhancement
          layer (if they exist) as out_lyrN.yuv (N = 1, 2, 3, ..)
        * Able to decode N layers (more than 2)
      
      Change-Id: I8555735db71e5b9b6f900ffdf978e0ad6f6bfc00
      2eeadab1
    • Imdad Sardharwalla's avatar
      Don't calculate chroma data in monochrome mode · af8e2648
      Imdad Sardharwalla authored
      Encoder: Prior to this patch, some chroma data was calculated and
      later discarded when in monochrome mode. This patch ensures that
      the chroma planes are left uninitialised and that chroma
      calculations are not performed.
      
      Decoder: Prior to this patch, some chroma calculations were still
      being performed in monochrome mode (e.g. loop filtering). This
      patch ensures that calculations are only performed on the y
      plane, with the chroma planes being set to a constant.
      
      Change-Id: I394c0c9fc50f884e76a65e6131bd6598b8b21b10
      af8e2648
  7. 17 Jan, 2018 2 commits
    • Yunqing Wang's avatar
      ext_tile: Not to write large_scale_tile bit to bitstream · 8ae64a93
      Yunqing Wang authored
      This patch made several changes.
      1. Removed writing large_scale_tile bit to bitstream.
      2. Created SET_TILE_MODE API in decoder to pass in tile coding mode
      information.
      3. Modified related unit tests.
      
      BUG=aomedia:1204
      
      Change-Id: I2d729afba8b1b9278543a5da154be7ae6c99d184
      8ae64a93
    • David Barker's avatar
      Disallow 4:4:0 subsampling · 0c3545b6
      David Barker authored
      BUG=aomedia:1233
      
      Change-Id: Ib740ee063b87003cf8c6cbd8f2ae4b917892e41c
      0c3545b6
  8. 16 Jan, 2018 1 commit
  9. 11 Jan, 2018 2 commits
  10. 10 Jan, 2018 1 commit
  11. 21 Dec, 2017 2 commits
  12. 15 Dec, 2017 1 commit
  13. 14 Dec, 2017 1 commit
  14. 13 Dec, 2017 1 commit
  15. 10 Dec, 2017 1 commit
    • Imdad Sardharwalla's avatar
      Monochrome control now in colorspace header · 317002fb
      Imdad Sardharwalla authored
      The monochrome bit has been removed from the end
      of the sequence header.
      Monochrome is now coded as a type of colorspace.
      
      Encode in monochrome by using
        aomenc --color-space=monochrome ...
      
      Change-Id: I9550de58eb3d67dae0eb651697cb63dc8b137931
      317002fb
  16. 04 Dec, 2017 1 commit
    • Imdad Sardharwalla's avatar
      Added monochrome option to the decoder. · 730c8054
      Imdad Sardharwalla authored
      When this is set (use --monochrome), all decoded frames
      will be given constant chroma planes.
      
      If the rawvideo option is used in conjunction with the
      monochrome option (i.e. --monochrome --rawvideo), the
      written output will only consist of the Y (luma) plane.
      
      Change-Id: I967817f1c3ebb1162fa9771b51cf6431120b835c
      730c8054
  17. 10 Nov, 2017 1 commit
    • Rupert Swarbrick's avatar
      Plumb in a "monochrome" flag · e0b15997
      Rupert Swarbrick authored
      This bit appears in the sequence header. At the moment, it does
      nothing, but it will mean that we don't encode (or read) chroma
      planes.
      
      This patch adds the flag to the sequence header, and also adds an
      encoder option (--monochrome) which enables it. At the moment, this
      doesn't do anything except cause the bit to be set correctly in the
      header.
      
      Change-Id: If5598412c1c75101553d7f8f9098f9ed1163514e
      e0b15997
  18. 01 Nov, 2017 2 commits
  19. 17 Oct, 2017 2 commits
    • Yaowu Xu's avatar
      Move a call to free · 568bf107
      Yaowu Xu authored
      This insures the pointer is still valid.
      
      BUG=aomedia:919
      
      Change-Id: Ia6f37c1bcc82bc1078387db31f8d8bf0fddc297e
      568bf107
    • Frederic Barbier's avatar
      Hide coding details of fid_length/delta_fid_length · e83fcfeb
      Frederic Barbier authored
      Let the writing/parsing logic do the +7/+2 offseting,
      and let the rest of the code directly manipulate the actual values.
      
      Change-Id: I460d5bf18446c028f326cb747b3c26c8d451637c
      e83fcfeb
  20. 14 Oct, 2017 1 commit
  21. 03 Oct, 2017 1 commit
    • David Barker's avatar
      Deduplicate use_reference_buffer/frame_id_numbers_present_flag · 5e70a114
      David Barker authored
      These two flags serve essentially the same purpose, so we can
      simplify down to just having one flag. Since the
      frame_id_numbers_present_flag is older and listed in the
      reference-buffer design doc, this is the one we'll keep.
      
      Note that, previously, frame_id_numbers_present_flag was only
      sent when CONFIG_OBU was enabled - otherwise it was always set
      to 1. On the other hand, use_reference_buffer was always signalled
      so that allowed us to disable frame ids even without CONFIG_OBU.
      
      In order to keep the ability to disable frame IDs without
      CONFIG_OBU, we send a "real" sequence header (ie, with the same
      data as in CONFIG_OBU) in-line within the uncompressed header.
      This is sent every keyframe and every intra-only frame, just
      as the use_reference_buffer flag was before this patch.
      
      BUG=aomedia:853
      
      Change-Id: I4bb6c7a222aeddfb6d3737a39d10782d32ee2eee
      5e70a114
  22. 29 Sep, 2017 1 commit
  23. 28 Sep, 2017 1 commit
  24. 20 Sep, 2017 1 commit
  25. 12 Aug, 2017 1 commit
  26. 08 Aug, 2017 1 commit
  27. 20 Jul, 2017 1 commit
    • Yunqing Wang's avatar
      Make ext_tile compatible with reference_buffer · c2502b55
      Yunqing Wang authored
      In ext_tile experiment, when cm->large_scale_tile is 1, prev_frame_id can be
      the same as current_frame_id, which is prohibited in reference_buffer
      experiment and causes "CORRUPT_FRAME" error to be reported.
      
      In this patch, enable/disable reference_buffer according to large_scale_tile
      value, and thus make these 2 experiments compatible.
      
      Change-Id: If64943acb91e7a7b859db4e2ac62581e9b53ef85
      c2502b55
  28. 14 Jul, 2017 1 commit
    • Yunqing Wang's avatar
      Make EXT_TILE compatible with TILE_GROUPS · eeb08a9b
      Yunqing Wang authored
      Added a 1-bit flag 'large_scale_tile'. If it is 0 that is the default value,
      use normal tile coding in TILE_GROUPS. If it is 1, use large-scale tile
      coding in EXT_TILE.
      
      At large_scale_tile=1 case, if single-tile-decoding is required, then the
      loopfilter is disabled.
      
      Related API and unit tests were modified.
      
      Change-Id: I3ba12dc3d80ccf1ab21543ab3b16c02282c34e3b
      eeb08a9b
  29. 11 Jul, 2017 1 commit
    • Thomas Daede's avatar
      Don't desync with the default encoder configuration. · 85b49000
      Thomas Daede authored
      The allow_lowbitdepth shouldn't be exported to the API at all.
      This is a temporary hack to allow API users such as the analyzer,
      inspector, and simple_decoder.c to function correctly.
      
      Change-Id: Id171cc0c24d78216647e949a1dc30a81f4cc826d
      85b49000
  30. 07 Jul, 2017 1 commit
    • Sebastien Alaiwan's avatar
      Encode superframes in front · e4c6fc18
      Sebastien Alaiwan authored
      This moves the superframe index at the beginning of the frame packet.
      There's no change in the superframe index format, and it's still
      optional.
      
      BUG=aomedia:22
      
      Change-Id: I1488429bd114c220ed110be34baee19191ff730e
      e4c6fc18
  31. 15 Jun, 2017 1 commit
  32. 14 Jun, 2017 1 commit