SDK / exoplayer

PiperOrigin-RevId: 283958680

Also remove redundant line

PiperOrigin-RevId: 283956203

PiperOrigin-RevId: 283951181

PiperOrigin-RevId: 283949259

PiperOrigin-RevId: 283810554

Saves around 200 lines of code. High level overview:
- Rename SampleQueue to SampleDataQueue.
- Rename SampleMetadataQueue to SampleQueue.

This CL should not introduce behavior changes. The only significant
changes in synchronization should be:
+ Add synchronized keyword to isReady.
  - Seems to be necessary.
+ Add synchronized keyword to SampleQueue.sampleMetadata.
  - Before this change, SampleQueue.sampleMetadata could acquire the
    SampleMetadataQueue lock three times in a single method call.

Other miscellaneous improvements:
+ Put all private methods at the bottom.
+ Move release() to the right category.

PiperOrigin-RevId: 283795844

PiperOrigin-RevId: 283795201

PiperOrigin-RevId: 283791815

This simplifies documentation and adds compiler checks that the correct values
are used.

PiperOrigin-RevId: 283754163

Also remove MetadataRenderer and SpliceInfoDecoder from the
nullness blacklist

PiperOrigin-RevId: 283744417

PiperOrigin-RevId: 283744017

I'd like to add a custom CueSubject, and if we upgrade first
we won't have to migrate from Subject<S, T> to Subject later:
https://truth.dev/subject_named_actual_type_parameters.html

PiperOrigin-RevId: 283737561

This parameter is a little confusing, especially as the behaviour
can be surprising if the intended use-case isn't clear. This change
moves the description of the parameter into the class javadoc,
adds context/justification and slims down each method's
javadoc to refer to the class-level.

Related to investigating/fixing issue:#6700

PiperOrigin-RevId: 283724826

PiperOrigin-RevId: 283722376

Issue: #6657
PiperOrigin-RevId: 283563218

PiperOrigin-RevId: 283559073

This is a minor change ahead of merging a full variant of
https://github.com/google/ExoPlayer/pull/6706, to make
re-buffers less likely.

Also remove variable substitution when parsing
AVERAGE-BANDWIDTH (it's not required for integer attributes)

PiperOrigin-RevId: 283554106

PiperOrigin-RevId: 283551324

PiperOrigin-RevId: 283546707

PiperOrigin-RevId: 283544187

PiperOrigin-RevId: 283543456

Calls to new Handler() without arguments are deprecated as of the latest Android
version. Replace them by a Util.createHandler call similar to the ones we
already have.

PiperOrigin-RevId: 283532891

Fixes issue:#6700

sample_cbs_truncated.adts test file produced using
`$ split -b 31795 sample_truncated.adts` to remove the last 10 bytes

PiperOrigin-RevId: 283530136

If LoadControl.shouldContinueLoading returns false and the renderers are not
ready for playback using the already buffered data, playback is stuck.

To prevent this situation, we always continue loading if the buffer is almost
empty. We already have a similar workaround for when
LoadControl.shouldStartPlayback returns false even if loading stopped.

Having both workarounds allows playback to continue even if the LoadControl
tries to prevent loading and playing all the time.

PiperOrigin-RevId: 283516750

PiperOrigin-RevId: 283515315

PiperOrigin-RevId: 283366568

Clarify `Format` vs `MediaFormat` in MediaCodecRenderer.

PiperOrigin-RevId: 283353651

PiperOrigin-RevId: 283347700

PiperOrigin-RevId: 283324784

PiperOrigin-RevId: 283324612

PiperOrigin-RevId: 283319944

PiperOrigin-RevId: 283310946

Enable using MediaCodec in async mode. Expose experimental
API to enable/disable the feature.

PiperOrigin-RevId: 283309798

This allows easy overriding of the resources by app developers

Issue: #6709
PiperOrigin-RevId: 283306121

PiperOrigin-RevId: 283296427

Issue: #6687
PiperOrigin-RevId: 283023548

*** Original commit ***

Improve `Format` propagation within the `MediaCodecRenderer`.

For example, fix handling of pixel aspect ratio changes in
playlists where video resolution does not change.

Issue:#6646

***

PiperOrigin-RevId: 282903626

PiperOrigin-RevId: 282837404

PiperOrigin-RevId: 282836739

When transitioning to a new stream in a different format, the audio
processors are reconfigured. After this, they are drained and then
flushed so that they are ready to handle data in updated formats for the
new stream.

Before this change, some audio processors made the assumption that after
reconfiguration no more input would be queued in their old input format,
but this assumption is not correct: during draining more input may be
queued. Fix this behavior so that the new configuration is not referred
to while draining and only becomes active once flushed.

Issue: #6601
PiperOrigin-RevId: 282515359