SDK / exoplayer

This typo was introduced in https://github.com/google/ExoPlayer/commit/ddb70d96ad99f07fe10f53a76ce3262fe625be70
when migrating a static method with parameter `durationUs` to an
instance method where the correct field to use was `blockDurationUs`
(but `durationUs` also exists).

The test that catches this was only added in https://github.com/google/ExoPlayer/commit/45013ece1e3fe054ff8960355a89559241eeb288 (and
therefore configured with the wrong expected output data).

issue:#6833
PiperOrigin-RevId: 288274197

Remove unused method
MediaCodecRenderer#getDequeueOutputBufferTimeoutUs().

PiperOrigin-RevId: 288005572

PiperOrigin-RevId: 287999703

It's not used. I was trying to work out how to correctly cascade my
text-combine-upright styling, but deleting the method seemed easier...

PiperOrigin-RevId: 287989480

I decided the flags bit was a bit unclear so I played around with this

It's also needed for more 'complex' assertions like colors - I didn't
want to just chuck in a fourth int parameter to create:
hasForegroundColorSpan(int start, int end, int flags, int color)

PiperOrigin-RevId: 287989424

Relying on the precedence of spans seems risky - I can't find it
defined anywhere. It might have changed in Android 6.0?
https://stackoverflow.com/q/34631851

PiperOrigin-RevId: 287989365

PiperOrigin-RevId: 287973192

Issue: #6552
PiperOrigin-RevId: 287964221

PiperOrigin-RevId: 287854701

Issue: #5789
PiperOrigin-RevId: 287828559

Issue: #6779
PiperOrigin-RevId: 287828273

Issue: #6266
PiperOrigin-RevId: 287821640

Issue: #6602
PiperOrigin-RevId: 287816831

It's unreliable for at least one IMA ADPCM file I've found.
Calculating the blockIndex to seek to using exact properties
also seems more robust.

Note this doesn't change anything for the existing PCM test,
since averageBytesPerSecond is set correctly. It does make
a difference for an upcoming IMA ADPCM test though.

PiperOrigin-RevId: 287814947

PiperOrigin-RevId: 287810018

An experiment with this algorithm didn't show positive results. We can
therefore keep the simpler default algorithm.

Startblock:
  <unknown commit> is submitted
PiperOrigin-RevId: 287807538

PiperOrigin-RevId: 287669425

Issue: #6733
PiperOrigin-RevId: 286621715

Where media segments are specified using byte ranges, it makes
sense that a server might return 416 (which we don't consider
for blacklisting) if the segment is unavailable, rather than
the 404 (which we do consider for blacklisting) that we expect
when media segments are only specified using a URL.

Issue: #6775
PiperOrigin-RevId: 286620698

PiperOrigin-RevId: 286587978

PiperOrigin-RevId: 286586865

PiperOrigin-RevId: 286585978

PiperOrigin-RevId: 286583957

Inspired by the `vertical` cue setting in WebVTT:
https://www.w3.org/TR/webvtt1/#webvtt-vertical-text-cue-setting

PiperOrigin-RevId: 286583621

PiperOrigin-RevId: 286581465

Issue: #6774
PiperOrigin-RevId: 286576383

The Download constructor considers it invalid to have a failure
reason if the download isn't in the failed state. Unfortunately,
calling DefaultDownloadIndex.removeAllDownloads when there's a
failed download will change the state without clearing the reason.
If the downloads are then read back from the DefaultDownloadIndex
we end up violating the Download constructor assertion.

This change clears the failed reason for any existing rows in the
invalid state, and also fixes the root cause that allows invalid
rows to enter the table in the first place.

Issue: #6785
PiperOrigin-RevId: 286576242

Issue: #6774
PiperOrigin-RevId: 286575797

Merge of https://github.com/google/ExoPlayer/pull/6793

PiperOrigin-RevId: 286556008

PiperOrigin-RevId: 286551438

Without this @Nullable, potential subclasses can't  override the
method to return null if they don't want to use the renderer as a
media clock.

Issue:#6792
PiperOrigin-RevId: 286545736

PiperOrigin-RevId: 286381499

PiperOrigin-RevId: 286368964

PiperOrigin-RevId: 286225012

This seems to work with R8 but interact badly with ProGuard.

issue:#6771
PiperOrigin-RevId: 286215262

PiperOrigin-RevId: 286203692

PiperOrigin-RevId: 286201458

Clarify that the units used here are microseconds

PiperOrigin-RevId: 286200583

This class is only used to hold temporary data while we parse the
settings and text, so we don't need it outside the Parser class.

Also remove all state from WebvttCueParser - this increases
the number of allocations, but there are already many
and  subtitles generally aren't very frequent (compared to
e.g. video frames).

PiperOrigin-RevId: 286200002

PiperOrigin-RevId: 286197990