Skip to content

SDK / exoplayer

Go to a project
Switch branch/tag
  1. 27 May, 2021 4 commits
    • Remove the default RTSP message handling off playback thread. · cfb90e4b 
      The callbacks received RTSP messages and RTSP sending errors are now invoked
directly from RtspMessageChannel's internal threads. It's up to the handler
implementation to decide which thread to handle the messages.

#minor-release

PiperOrigin-RevId: 375908282
      claincly committed
    • Move RTP packet forwarding off playback thread. · 68b2875a 
      Previously, RTSP interleaved binary data is posted onto the playback thread
for handling, the playback thread then adds the received data to a queue.
A loader thread will later dequeue the data and process it.

In this CL, the binary data is sent through a separate listener, on
RtspMessageChannel's RTSP receiving thread.

#minor-release

PiperOrigin-RevId: 375907609
      claincly committed
    • Allow RtspHeaders to take multiple header values under the same name. · 4a780fb9 
      Some RTSP servers will offer multiple WWW-Authenticate options. We wanted to
be able to pick them up.

#minor-release

PiperOrigin-RevId: 375907276
      claincly committed
    • Throw from (pre)acquireSession if the DrmSessionManager isn't prepared · e7516fe4 
      Currently acquireSession() fails with an NPE from
checkNotNull(exoMediaDrm). A follow-up change will result in exoMediaDrm
sometimes being non-null while prepareCount==0 (and in this case we
still want acquireSession() to fail).

preacquireSession() doesn't currently fail in a way the caller can
observe - the same NPE is thrown, but asynchronously and it doesn't
propagate out of the background thread. Throwing directly seems
preferable since it's a clear bug to be trying to preacquire sessions
from an unprepared/released manager.

PiperOrigin-RevId: 375906450
      ibaker committed
  3. 26 May, 2021 14 commits
  5. 21 May, 2021 9 commits
  7. 20 May, 2021 9 commits
  9. 19 May, 2021 4 commits