1. 16 Sep, 2022 1 commit
  2. 15 Sep, 2022 1 commit
  3. 14 Sep, 2022 3 commits
  4. 13 Sep, 2022 1 commit
  5. 12 Sep, 2022 3 commits
  6. 11 Sep, 2022 1 commit
  7. 09 Sep, 2022 4 commits
  8. 08 Sep, 2022 4 commits
  9. 07 Sep, 2022 4 commits
  10. 06 Sep, 2022 3 commits
  11. 30 Sep, 2022 2 commits
  12. 06 Sep, 2022 3 commits
  13. 05 Sep, 2022 5 commits
    • Merge RgbProcessor and MatrixTransformation. · 8da65d01
      PiperOrigin-RevId: 472325145
      (cherry picked from commit 672405af)
      leonwind committed
    • Fix 4 ErrorProneStyle findings: · 1bf43156
      * Non-standard parameter comment; prefer `/* paramName= */ arg`
        (see http://go/bugpattern/ParameterComment) (2 times)
      * This catch block catches an exception and re-throws another, but swallows the caught exception rather than setting it as a cause. This can make debugging harder.
        (see http://go/bugpattern/UnusedException)
      * This comment contains Javadoc or HTML tags, but isn't started with a double asterisk (/**); is it meant to be Javadoc?
        (see http://go/bugpattern/AlmostJavadoc)
      
      This CL looks good? Just LGTM and Approve it!
      This CL doesn’t look good? This is what you can do:
      * Revert this CL, by replying "REVERT: <provide reason>"
      * File a bug under go/error-prone-bug for category ErrorProneStyle if there's an issue with the CL content.
      * File a bug under go/rosie-bug if there's an issue with how the CL was managed.
      * Revert this CL and not get a CL that cleans up these paths in the future by
      replying "BLOCKLIST: <provide reason>". This is not reversible! We recommend to
      opt out the respective paths in your CL Robot configuration instead:
      go/clrobot-opt-out.
      
      This CL was generated by CL Robot - a tool that cleans up code findings
      (go/clrobot). The affected code paths have been enabled for CL Robot in //depot/google3/java/com/google/android/libraries/media/METADATA which is reachable following include_presubmits from //depot/google3/third_party/java_src/android_libs/media/METADATA.
      Anything wrong with the signup? File a bug at go/clrobot-bug.
      
      #codehealth
      
      Tested:
          Local presubmit tests passed.
      PiperOrigin-RevId: 472255768
      (cherry picked from commit 3a2e0d37)
      Googler committed
    • Fix 3 ErrorProneStyle findings: · 5426d02e
      * Non-standard parameter comment; prefer `/* paramName= */ arg`
        (see http://go/bugpattern/ParameterComment) (3 times)
      
      This CL looks good? Just LGTM and Approve it!
      This CL doesn’t look good? This is what you can do:
      * Revert this CL, by replying "REVERT: <provide reason>"
      * File a bug under go/error-prone-bug for category ErrorProneStyle if there's an issue with the CL content.
      * File a bug under go/rosie-bug if there's an issue with how the CL was managed.
      * Revert this CL and not get a CL that cleans up these paths in the future by
      replying "BLOCKLIST: <provide reason>". This is not reversible! We recommend to
      opt out the respective paths in your CL Robot configuration instead:
      go/clrobot-opt-out.
      
      This CL was generated by CL Robot - a tool that cleans up code findings
      (go/clrobot). The affected code paths have been enabled for CL Robot in //depot/google3/java/com/google/android/libraries/media/METADATA which is reachable following include_presubmits from //depot/google3/third_party/java_src/android_libs/media/METADATA.
      Anything wrong with the signup? File a bug at go/clrobot-bug.
      
      #codehealth
      
      Tested:
          Local presubmit tests passed.
      PiperOrigin-RevId: 472254253
      (cherry picked from commit 573ad66f)
      Googler committed
    • Fix 1 ErrorProneStyle finding: · e466155c
      * Non-standard parameter comment; prefer `/* paramName= */ arg`
        (see http://go/bugpattern/ParameterComment)
      
      This CL looks good? Just LGTM and Approve it!
      This CL doesn’t look good? This is what you can do:
      * Revert this CL, by replying "REVERT: <provide reason>"
      * File a bug under go/error-prone-bug for category ErrorProneStyle if there's an issue with the CL content.
      * File a bug under go/rosie-bug if there's an issue with how the CL was managed.
      * Revert this CL and not get a CL that cleans up these paths in the future by
      replying "BLOCKLIST: <provide reason>". This is not reversible! We recommend to
      opt out the respective paths in your CL Robot configuration instead:
      go/clrobot-opt-out.
      
      This CL was generated by CL Robot - a tool that cleans up code findings
      (go/clrobot). The affected code paths have been enabled for CL Robot in //depot/google3/java/com/google/android/libraries/media/METADATA which is reachable following include_presubmits from //depot/google3/third_party/java_src/android_libs/media/METADATA.
      Anything wrong with the signup? File a bug at go/clrobot-bug.
      
      #codehealth
      
      Tested:
          Local presubmit tests passed.
      PiperOrigin-RevId: 472252461
      (cherry picked from commit 83485bc5)
      Googler committed
    • Minor javadoc and scoping cleanup. · c4fa1978
      No functional changes.
      
      PiperOrigin-RevId: 472245797
      (cherry picked from commit fa1f09fc)
      huangdarwin committed
  14. 02 Sep, 2022 3 commits
    • Remove assertion that prevents masking of ad periods · 1b706077
      The assertion asserts against a `Period` and an `AdPlaybackState` which actually
      asserts against a resolved ad which is what `ExoPlayerImplInternal` does later and
      what gives us a `SEEK_ADJUSTMENT`. However, this assertion is not required at the
      moment of masking, because we are sure that the resolved seek results in a content
      period and never an ad period.
      
      #minor-release
      Issue: androidx/media#122
      PiperOrigin-RevId: 471827072
      (cherry picked from commit 73f86682)
      bachinger committed
    • Add sepia, grayscale, and inverted filters to the demo app. · 2dfca4fc
      PiperOrigin-RevId: 471782565
      (cherry picked from commit 305ea205)
      leonwind committed
    • Rename shouldPassthrough to shouldTranscode · eac48294
      shouldPassthrough's internal checks seem to be check whether we should *not*
      pass through, which seemed a bit like a confusing double-negative to me.
      
      shouldTranscode is slightly more clear, by instead returning true when we do
      want to transcode.
      
      No functional changes intended.
      
      PiperOrigin-RevId: 471753771
      (cherry picked from commit 7085c2fa)
      huangdarwin committed
  15. 01 Sep, 2022 2 commits