- 22 Sep, 2022 3 commits
-
- 21 Sep, 2022 2 commits
-
-
Tested: * Manually using both path and file descriptor. PiperOrigin-RevId: 475860978 (cherry picked from commit 9ec4e134)
samrobinson committed
-
- 20 Sep, 2022 1 commit
-
- 16 Sep, 2022 2 commits
-
-
Currently doSomeWork is never closed and so tracing is deceiving. See https://screenshot.googleplex.com/eZDzn5APpBNnhe5 PiperOrigin-RevId: 474755816 (cherry picked from commit 06230f19)
yschimke committed
- 15 Sep, 2022 1 commit
-
- 14 Sep, 2022 3 commits
-
-
By skipping every other row and column, SSIM calculation time reduces by 10-30%. PiperOrigin-RevId: 474286702 (cherry picked from commit 314b312a)
samrobinson committed -
PiperOrigin-RevId: 474279220 (cherry picked from commit bca9c9b2)
samrobinson committed
- 13 Sep, 2022 1 commit
-
- 12 Sep, 2022 3 commits
-
-
As part of this change, MssimCalculator is moved from androidTest/ to main/ PiperOrigin-RevId: 473771344 (cherry picked from commit 8ce42f06)
samrobinson committed
-
- 11 Sep, 2022 1 commit
-
- 09 Sep, 2022 4 commits
-
-
https://github.com/androidx/media/commit/3d5ddf0c42f1d2b91d4ef33c75f59656c6e566bc
*** Original commit *** Handle int instead of byte in SSIM. The value of pixels are converted to integers at the point of use, move this logic to the initialisation step. This is a prerequisite step for testing SSIM calculation, which will lead on to some SSIM improvements being verifiable. Tested manually and SSIM values match for the same video before and after this change. *** PiperOrigin-RevId: 473259446 (cherry picked from commit d188babd)
samrobinson committed -
The value of pixels are converted to integers at the point of use, move this logic to the initialisation step. This is a prerequisite step for testing SSIM calculation, which will lead on to some SSIM improvements being verifiable. Tested manually and SSIM values match for the same video before and after this change. PiperOrigin-RevId: 473231779 (cherry picked from commit 3d5ddf0c)
samrobinson committed -
PiperOrigin-RevId: 473212543 (cherry picked from commit 4133bb60)
huangdarwin committed
- 08 Sep, 2022 4 commits
-
-
PiperOrigin-RevId: 472974903 (cherry picked from commit 260aabb6)
christosts committed -
Test that HDR editing succeeds on devices supporting HDR editing, tone maps on devices supporting tone mapping, and throws exceptions on all other devices. Also, only restrict HDR editing and tone mapping support to API 31+ only when transcoding, not for all transformations. PiperOrigin-RevId: 472958965 (cherry picked from commit 0d8fd3d4)
huangdarwin committed
- 07 Sep, 2022 4 commits
-
-
The exception fires when intent resolution fails to find a service which declares an appropriate intent-filter. The existing message is confusing; it's trying to say that the service couldn't be found but the double negative renders it incorrect. #cleanup #minor-release PiperOrigin-RevId: 472736740 (cherry picked from commit 15d3d74e)
Googler committed -
If the back buffer is using too much memory, there is a risk playback could get stuck because LoadControl refuses to load further data. This eventually results in a stuck-buffering playback error. We can detect this case, clear the back buffer and then ask the LoadControl again to avoid failing playback in such a case. PiperOrigin-RevId: 472679797 (cherry picked from commit 310e0fec)
tonihei committed
- 06 Sep, 2022 3 commits
-
-
The stream offset is used to calculate the presentation time of a metadata object when reading and later when playing, to calculate the current presentation time to decide whether to send the metadata to the output. Accordingly, the presentation time of a pending metadata that has been calculated with a given offset needs to be recalculated when the stream offset changes. #minor-release PiperOrigin-RevId: 472499943 (cherry picked from commit 0896c4dd)
bachinger committed
- 30 Sep, 2022 2 commits
-
-
PiperOrigin-RevId: 472488921 (cherry picked from commit a18ab374)
Marc Baechinger committed -
PiperOrigin-RevId: 472475124 (cherry picked from commit cec6f045)
Marc Baechinger committed
-
- 06 Sep, 2022 3 commits
-
- 05 Sep, 2022 3 commits
-
-
* 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 -
* 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
