Skip to content

SDK / exoplayer

Go to a project
Switch branch/tag
  1. 21 Jul, 2022 3 commits
  3. 20 Jul, 2022 1 commit
  5. 19 Jul, 2022 6 commits
  7. 18 Jul, 2022 5 commits
    • HDR: Use FP16 color representation for texture processors. · 76093e25 
      * Introduced `useHdr` for `GlEffect#toGlTextureProcessor`, so
  `TextureProcessor` implementations can decide how to handle HDR.
* Creating FP16 color textures for HDR input.

Tested via manual testing, adding a no-op GlEffectWrapper to the transformation to
force use of intermediate textures, adding a linear ramp to the fragment shader,
and trying to ascertain that there's a real reduction in posterization when
switching from 4-bit to 8-bit unsigned bytes, and again from 8-bit unsigned bytes
to 16-bit floating point.

PiperOrigin-RevId: 461613117
(cherry picked from commit f67c1a73)
      huangdarwin committed
    • HDR: Throw when unexpected color transfer encountered. · 7d147509 
      This may happen when a containers' color transfer incorrectly does not match
the video's color transfer.

An example of a file with such a mismatch is the current Transformer demo HDR10
sample file.

Manually tested by confirming that no errors are emitted for SDR and HLG sample
files, and that errors are emitted for our incorrect HDR10 sample file.

PiperOrigin-RevId: 461583532
(cherry picked from commit fd046bd2)
      huangdarwin committed
    • Use the current overrides of the player as preset · 26b062bf 
      Issue: google/ExoPlayer#10429
PiperOrigin-RevId: 461577039
(cherry picked from commit f828130c)
      bachinger committed
    • Make minor fixes to HDR handling · 0e156891 
      - Update profile selection logic to pick an HDR-compatible profile when doing HDR editing on H.264/AVC videos.
- Handle doing the capabilities check for all MIME types that support HDR (not just H.265/HEVC).
- Fix a bug where we would pass an HDR input color format to the encoder when using tone-mapping.
- Tweak how `EncoderWrapper` works so decisions at made at construction time.

Manually tested cases:
- Transformation of an SDR video.
- Transformation of an HDR video to AVC (which triggers fallback/tone-mapping on a device that doesn't support HDR editing for AVC).
- Transformation of an HDR video with HDR editing.

PiperOrigin-RevId: 461572973
(cherry picked from commit 0db07c67)
      andrewlewis committed
    • Update demo HDR10 video URL · ce3cdf85 
      The old URL doesn't correctly signal the HDR10 color info in the container.

The new URL signals ST2084 (PQ) transfer function and BT.2020 color space as expected.

PiperOrigin-RevId: 461560107
(cherry picked from commit 405be80f)
      andrewlewis committed
  9. 15 Jul, 2022 1 commit
  11. 14 Jul, 2022 1 commit
  13. 13 Jul, 2022 5 commits
  15. 12 Jul, 2022 7 commits
  17. 11 Jul, 2022 2 commits
  19. 07 Jul, 2022 2 commits
  21. 06 Jul, 2022 2 commits
  23. 05 Jul, 2022 1 commit
  25. 04 Jul, 2022 1 commit
  27. 01 Jul, 2022 3 commits
    • Fallback to SDR if encoder doesn't support HDR (HLG only). · 67439206 
      If the input is HDR (HLG), check encoder capabilities for HDR support
and request tone-mapping to SDR during decoder configuration otherwise.
Capabilities are only checked for API 31 and above, as HDR editing is
not supported before.

As the encoder capabilities check needs to happen before selecting the
encoder to use (as this may depend on the resolution output by the
effects chain), the EncoderWrapper checks all candidate encoders
for the MIME type for HDR capabilities and only requests fallback to
SDR if none of them support it.

When the actual encoder is selected, the wrapper checks that it matches
one of the encoders is checked capabilities for.

PiperOrigin-RevId: 458511599
(cherry picked from commit 474e2f2c)
      hschlueter committed
    • HDR: Configure GL shaders and encoder. · 39047b56 
      Configure the GL shaders and encoder to take in HDR metadata.

This mostly just consists of passing the Format.colorInfo through
the VideoTranscodingSamplePipeline down to the encoder, rather than passing
the PQ-ness down to the GL step.

Due to b/237674316, this will remove HDR10+ support temporarily to introduce
support for HLG10.

Manually tested to confirm that HLG10 operations that don't affect color display
correctly after this CL with "HDR editing" in the demo checked, and continue to display incorrectly (as before this CL) without the option unchecked.

PiperOrigin-RevId: 458490810
(cherry picked from commit 53db3056)
      huangdarwin committed
    • Fix error in frame rate handling. · b440b556 
      The old getString() will throw because FRAME_RATE can only be float or int.

PiperOrigin-RevId: 458481251
(cherry picked from commit 2b6f62b2)
      claincly committed