SDK / exoplayer

PiperOrigin-RevId: 256147805

1. Only output video starting from a keyframe
2. When calculating the timestamp offset to adjust live streams to start
   at t=0, use the timestamp of the first tag from which a sample is actually
   output, rather than just the first audio/video tag. The test streams in
   the referenced GitHub issue start with a video tag whose packet type is
   AVC_PACKET_TYPE_SEQUENCE_HEADER (i.e. does not contain a sample) and whose
   timestamp is set to 0 (i.e. isn't set). The timestamp is set correctly on
   tags that from which a sample is actually output.

Issue: #6111
PiperOrigin-RevId: 256147747

PiperOrigin-RevId: 256147742

Issue: #6047
PiperOrigin-RevId: 255992898

PiperOrigin-RevId: 255964199

The total window and period count, as well as the period offset for each holder
are not actually needed and can be removed.

Also added a TODO to remove two other variables if possible.

PiperOrigin-RevId: 255945584

Issue:#6109
PiperOrigin-RevId: 255933121

PiperOrigin-RevId: 255584000

ISSUE: #6093
PiperOrigin-RevId: 255471282

PiperOrigin-RevId: 255442455

PiperOrigin-RevId: 255412493

PiperOrigin-RevId: 255410268

PiperOrigin-RevId: 255380951

PiperOrigin-RevId: 255380796

PiperOrigin-RevId: 255379393

PiperOrigin-RevId: 255378274

PiperOrigin-RevId: 255377347

The updated version issues more warnings than before.
Most of the changes are related to annotation placement.

PiperOrigin-RevId: 255371743

Also add layer of indirection between code and the guide, to
make moving content easier going forward.

PiperOrigin-RevId: 255182216

This better reflects its usage and fits into our general naming pattern.

PiperOrigin-RevId: 255157159

stack trace contains MediaCodec.

PiperOrigin-RevId: 254781909

PiperOrigin-RevId: 254746146

Fix a super tiny typo.

Issue: #5928
PiperOrigin-RevId: 254379085

PiperOrigin-RevId: 254372134

Reads from a SampleQueue, associating each read format with a
DrmSession, if needed.

PiperOrigin-RevId: 254192562

PiperOrigin-RevId: 254187403

PiperOrigin-RevId: 254182080

PiperOrigin-RevId: 254172906

PiperOrigin-RevId: 254156143

PiperOrigin-RevId: 254048233

PiperOrigin-RevId: 254046126

Builds now fail when raw generics are used.

PiperOrigin-RevId: 253969682

PiperOrigin-RevId: 253959976

ISSUE: #6041
PiperOrigin-RevId: 253958225

More information (LSC)
https://docs.google.com/document/d/16tpK6aXqN68PvTyvt4siM-m7f0NXi_8xEeitLDzr8xY/edit?usp=sharing

Tested:
    tap_presubmit: http://test/OCL:253818309:BASE:253788332:1560879553629:9dc07a48
    Some tests failed; test failures are believed to be unrelated to this CL
PiperOrigin-RevId: 253858263

PiperOrigin-RevId: 253808562

We are currently queuing periods in a way such that the new start position
lines up with the end of the previous period (to ensure continuous playback).
However, if the start position of the new period is larger than the total of
all previously played period durations, we may end up with negative renderer
timestamps when seeking back to the beginning of this new period. Negative
timestamps should be avoided as most decoders have problems handling them
correctly.

This change forces a renderer reset if we detect such a seek to a negative
renderer time and also resets the renderer offset to 0 every time all
renderers are disabled, as this is the only time where we can savely change
the offset of an existing media period.

Also, if playback starts with an ad, we choose the content position as
renderer offset to prevent the whole issue from occurring for the seek-behind-
midroll case.

Issue:#6009
Issue:#5323
PiperOrigin-RevId: 253790054