Announcement

Collapse
No announcement yet.

Libvpx 1.7.0 Released With AVX Optimizations & More

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Libvpx 1.7.0 Released With AVX Optimizations & More

    Phoronix: Libvpx 1.7.0 Released With AVX Optimizations & More

    Google's WebM folks quietly released libvpx 1.7.0 earlier this week as the latest version of their VP8/VP9 encoder/decoder library...

    http://www.phoronix.com/scan.php?pag...leased-VP8-VP9

  • #2
    And some benchmark ?? 1.6.1 vs 1.7.0 ??

    Comment


    • #3
      I second the benchmarks, especially encoding with before/after with new --row-mt option if possible

      Also the changelog, seems they didn't push it to the github mirror?

      https://chromium.googlesource.com/webm/libvpx/+/v1.7.0

      Code:
      2017-01-04 v1.7.0 "Mandarin Duck"
        This release focused on high bit depth performance (10/12 bit) and vp9
        encoding improvements.
      
        - Upgrading:
          This release is ABI incompatible due to new vp9 encoder features.
      
          Frame parallel decoding for vp9 has been removed.
      
        - Enhancements:
          vp9 encoding supports additional threads with --row-mt. This can be greater
          than the number of tiles.
      
          Two new vp9 encoder options have been added:
            --corpus-complexity
            --tune-content=film
      
          Additional tooling for respecting the vp9 "level" profiles has been added.
      
        - Bug fixes:
          A variety of fuzzing issues.
          vp8 threading fix for ARM.
          Codec control VP9_SET_SKIP_LOOP_FILTER fixed.
          Reject invalid multi resolution configurations.

      Comment


      • #4
        Originally posted by Mr. Octus View Post
        I second the benchmarks, especially encoding with before/after with new --row-mt option if possible
        I completely agree!
        ## VGA ##
        AMD: X1950XTX, HD3870, HD5870
        Intel: GMA45, HD3000 (Core i5 2500K)

        Comment


        • #5
          I would also like to see some benchmarks!

          Comment

          Working...
          X