SDK / exoplayer

PiperOrigin-RevId: 258752996

AV1 profile recognition requires additional info contained in format.

PiperOrigin-RevId: 258746315

2-letter codes (ISO 639-1) are the standard Android normalization and thus we
should prefer them to 3-letter codes (although both are technically allowed
according the BCP47).

This helps in two ways:
 1. It simplifies app interaction with our normalized language codes as the
    Locale class makes it easy to convert a 2-letter to a 3-letter code but
    not the other way round.
 2. It better normalizes codes on API<21 where we previously had issues with
    language+country codes (see tests).
 3. It allows us to normalize both ISO 639-2/T and ISO 639-2/B codes to the same
    language.

PiperOrigin-RevId: 258729728

Issue:#6192
PiperOrigin-RevId: 258592902

PiperOrigin-RevId: 258590215

If we use the default start position, we currently resolve it immediately
even if we need to play an ad first, and later try to project forward again
if we believe that the default start position should be used.

This causes problems if a specific start position is set and the later
projection after the preroll ad shouldn't take place.

The problem is solved by keeping the content position as TIME_UNSET (= default
position) if an ad needs to be played first. The content after the ad can
then be resolved to its current default position if needed.

PiperOrigin-RevId: 258583948

PiperOrigin-RevId: 258574110

Add appropriate unit tests.

PiperOrigin-RevId: 258552404

Issue: #6184
PiperOrigin-RevId: 258527533

These methods helps to indicate that a media source isn't used to create new
periods in the immediate term and thus limited resources can be released.

PiperOrigin-RevId: 258373069

These getters do not modify the instance.

PiperOrigin-RevId: 258345084

PiperOrigin-RevId: 258285645

The name of this parameter recently changed in https://github.com/google/ExoPlayer/commit/3fe0b1a6fee8e7631caa5a6f84306396ee6999ad and I forgot
to change these inline comment usages.

PiperOrigin-RevId: 258160659

PiperOrigin-RevId: 258110603

PiperOrigin-RevId: 258038961

This better reflects its usage as a caller identifier and not just a listener.

PiperOrigin-RevId: 257827188

PiperOrigin-RevId: 257777513

It's easy to forget to forward methods when using basic wrapping. For example,
ExtractorMediaSource.addEventListener is currently a no-op because it's not
forwarded.

PiperOrigin-RevId: 257757556

PiperOrigin-RevId: 257757496

PiperOrigin-RevId: 257668797

PiperOrigin-RevId: 257630168

PiperOrigin-RevId: 257624043

Non-functional change. Makes it easier to add the ExoMediaCrypto type information
to the formats.

PiperOrigin-RevId: 257598282

Potentially avoids up to two calls to synchronized methods

PiperOrigin-RevId: 257578304

PiperOrigin-RevId: 257576791

PiperOrigin-RevId: 257478434

This is a temporary workaround until we have migrated all MediaSources uses.
This change avoids having to migrate all uses of MediaSources immediately.

PiperOrigin-RevId: 257459138

PiperOrigin-RevId: 257456890

To use in HLS when session keys are provided

PiperOrigin-RevId: 257421156

- Remove manifest argument from callbacks of Player.EventListener and
  SourceInfoRefreshListener. Instead make it accessible through
  Player.getCurrentManifest() and Timeline.Window.manifest.
- Fix all MediaSource implementation to include the manifest in the
  Timeline instead of passing it to the SourceInfoRefreshListener.
- Refactor ExoPlayerTestRunner, FakeTimeline, FakeMediaSource to
  reflect these changes and make tests pass.

PiperOrigin-RevId: 257359662

PiperOrigin-RevId: 257185017

PiperOrigin-RevId: 257184313

Decode and add vorbis comments from the flac file to metadata.

 #5527

PiperOrigin-RevId: 257161518

Sending MESSAGE_PREPARE_SOURCE should happen last in the constructor.
It was previously happening before initialization finished (and in
particular before pendingMediaPeriods was instantiated).

Issue: #6146
PiperOrigin-RevId: 257158275

We currently use an alpha version which allowed us to access new threading
features. The stable version of this has been released now and we can
switch back.

PiperOrigin-RevId: 257149681

PiperOrigin-RevId: 257138448

We currently handle most the control code logic after handling special
characters. This includes filtering out repeated control codes and checking
for the correct channel. As the special character sets are control codes as well,
these checks should happen before parsing the characters.

Issue:#6133
PiperOrigin-RevId: 256993672