SDK / exoplayer

PiperOrigin-RevId: 231171425

This brings in a memory leak fix.

Issue: #4114
PiperOrigin-RevId: 230880521

PiperOrigin-RevId: 230743198

PiperOrigin-RevId: 230734189

r2.9.4

ExoPlaybackExceptions of type SOURCE are always associated with the loading
period and thus we can use the event time for the loading period in
onPlayerError. Renderer and unexpected exceptions are still associated with the
currently playing period.

Issue:#5407
PiperOrigin-RevId: 230216253

PiperOrigin-RevId: 230213842

Change the dependency to the new monolithic GVR SDK target.

PiperOrigin-RevId: 229931549

The Amlogic awesome decoder reduces the video size of interlaced videos by half
if the internal configuration isn't force reset with new maximum input size
values. The product of these new values must exceed 1920x1088 to force the
reset.

Issue:#5003
PiperOrigin-RevId: 230206675

Issue:#5402
PiperOrigin-RevId: 229758525

That's the same position set in MediaPeriod.prepare (where it may be removed
in the future).

Having the position at an earlier point is necessary to fix an
issue with lazy preparation in ConcatenatingMediaSource where the prepare
position was assumed to be known but MediaPeriod.prepare hasn't been called
yet.

Issue:#5350
PiperOrigin-RevId: 229756637

Issue: #5344
PiperOrigin-RevId: 229527963

When the extra adaptation set of a switch group isn't defined in the manifest, we
currently assume it's the first adaptation group. This either leads to wrong grouping
or duplicate track groups.

Such a case may easily happen if the manifest is filtered such that only one of the
switch adaptation sets will be present in the manifest.

PiperOrigin-RevId: 229365379

PiperOrigin-RevId: 229365333

PiperOrigin-RevId: 229364563

The buffered position is currently based on the mimimum queued timestamp of
all AV tracks. If the tracks have unequal lengths, one track continues loading
without bounds as the "buffered position" will always stay at the shorter
track's duration.

This change adds an optional buffer flag to mark the last sample of the
stream. This is set in the Mp4Extractor only so far. ExtractorMediaSource
uses this flag to ignore AV streams in the buffered duration calculation if
they already finished loading.

Issue:#3670
PiperOrigin-RevId: 229359899

Issue: #5378
PiperOrigin-RevId: 229261658

We currently forget whether a source is seekable at re-preparation. This was
implemented intentionally this way under the assumption that we really can't seek
until we have loaded the seek map again. However, seek operations are only
allowed after a media period is prepared. So there is no harm in remembering
whether a source is seekable.

This problem currently prevents reusing ClippingMediaSources with
ExtractorMediaSource and a non-zero start clip position.

Issue: #5351
PiperOrigin-RevId: 229169441

Issue: #4519
PiperOrigin-RevId: 229145790

The window object is used without being filled with data. This used to work
well for most cases as the same live stream is sending regular updates and the
first update is almost never used if it's not the first item in a playlist.

It causes problems when the first timeline update of a live stream is actually
used for playback (e.g. when the live stream is lazily prepared in a playlist
and played first).

PiperOrigin-RevId: 228530232

Setting the target conpatibility only seems to work for Java. Added the
equivalent Kotlin config options to the docs.

Issue:#5276
PiperOrigin-RevId: 228482496

PiperOrigin-RevId: 228296962

Issue:#5313
PiperOrigin-RevId: 228155222

Issue:#5320
PiperOrigin-RevId: 228142567

These are part of published IMA SDK 3.10.2.

PiperOrigin-RevId: 227861713

Also configure the FFmpeg context to ignore errors as far as possible (this
appears to have an effect only for certain decoders).

Issue: #5293
PiperOrigin-RevId: 227851397

PiperOrigin-RevId: 227822937

PiperOrigin-RevId: 227813461

If a negative value is read, sniffing should just fail.

PiperOrigin-RevId: 227689568

Issue:#5312
PiperOrigin-RevId: 227673949

PiperOrigin-RevId: 227668426

ExoPlayer methods must not be called from any thread besides the specified
app thread. Therefore we shouldn't use them here. Using a regular Handler
instead is fully equivalent.

Issue:#5240
PiperOrigin-RevId: 227650489

PiperOrigin-RevId: 227646358

PiperOrigin-RevId: 227520168

Issue: #4114
PiperOrigin-RevId: 227516509

PiperOrigin-RevId: 227500707

See also https://github.com/Matroska-Org/matroska-specification/issues/269.

PiperOrigin-RevId: 226758584

Issue:#4160
Issue:#4743
PiperOrigin-RevId: 225813243