1. 18 Oct, 2022 7 commits
  2. 17 Oct, 2022 1 commit
  3. 14 Oct, 2022 5 commits
  4. 17 Oct, 2022 1 commit
  5. 13 Oct, 2022 4 commits
  6. 12 Oct, 2022 3 commits
    • Add Cea608DecoderTest · 3575b680
      When debugging and fixing Issue: google/ExoPlayer#10666 I wanted to write a regression
      test, but needed to add a test first... This is just a small bit of
      coverage to start with. It checks the field/channel filtering works
      correctly, but doesn't check any styling info. It also doesn't test
      'pop on' subtitles (i.e. when the subtitle isn't shown until a 'end of
      subtitle' signal is received).
      
      PiperOrigin-RevId: 480644568
      (cherry picked from commit 706b1299)
      ibaker committed
    • Demo: Shorten trim range from 60 seconds to 10 seconds. · cc672410
      Most demo videos aren't very long, and the default demo video is only 10 seconds.
      
      Shorten the maximum trim duration to 10 seconds, to demonstrate transformer functionality more easily, and allow this to be used more easily when trimming short sections of a longer video (ex. to make test clips)
      
      PiperOrigin-RevId: 480602037
      (cherry picked from commit f35bda35)
      huangdarwin committed
    • Demo: Hide player controls by default. · 28763e7d
      Player controls are somewhat distracting when showing the difference between the
      input and output video, as they obscure and darken the video players.
      
      PiperOrigin-RevId: 480597804
      (cherry picked from commit 51edb329)
      huangdarwin committed
  7. 11 Oct, 2022 2 commits
  8. 10 Oct, 2022 6 commits
  9. 07 Oct, 2022 5 commits
  10. 06 Oct, 2022 3 commits
  11. 05 Oct, 2022 3 commits
    • Misc fix on DefaultMediaNotificationProviderTest · 1cfeddc3
      PiperOrigin-RevId: 479079184
      (cherry picked from commit bf948db6)
      christosts committed
    • Fix RequestMetadata JavaDoc link to point to the right MediaController. · a31a6c6c
      The JavaDoc of RequestMetadata should point to the media3 controller,
      not the platform one.
      
      PiperOrigin-RevId: 479047924
      (cherry picked from commit b70258e4)
      tonihei committed
    • Add FrameProcessor functionality to release a frame immediately · 1b25dc26
      Currently `FrameProcessor.releaseOutputFrame()` method supports
      
      Release at a specific system time
      Drops the frame
      This API is not that convenient to use when the caller wants to release a frame, now, regardless of the release time. A use case is to release (present) a frame when no frame is shown for a while, and it's thus better to just release the frame, now.
      
      Currently if MCVR wants a frame to be rendered now, MCVR calls release frame with a set offset like 10us: `releaseOutputFrame(System.nanoTime() + 10_000)`. The 10us offset is to prevent the frame processor dropping the frame, due to thread hopping delays.
      
      To make the API better usable, consider adding a mode for releasing the frame now, like (bold marks the new mode)
      
      - Use C.TIME_UNSET to drop
      - **Use -1 to release the frame immediately, or**
      - Use an actual release time.
      
      PiperOrigin-RevId: 479044215
      (cherry picked from commit 139a6e8d)
      claincly committed