SDK / exoplayer

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

flush() is guaranteed to be called in all these cases anyway.

Also clarify documentation for AudioProcessor-specific methods that can
change the 'active' flag.

Issue: #6601
PiperOrigin-RevId: 282515255

Issue: #6601
PiperOrigin-RevId: 282515179

This simplifies the contract of configure and is in preparation for
fixing a bug where more input can't be queued when draining audio
processors for a configuration change.

Issue: #6601
PiperOrigin-RevId: 282514367

PiperOrigin-RevId: 282227866

PiperOrigin-RevId: 281976465

Issue: #6636
PiperOrigin-RevId: 281972403

Note that the renderer changes will all disappear when we remove
legacy injection of DrmSessionManager into renderers.

PiperOrigin-RevId: 281952601

PiperOrigin-RevId: 281764207

PiperOrigin-RevId: 281763672

- Move property to DrmSession; it feels like a more natural place
  for it to go (and provides greater flexibility).
- Change flags to a boolean.

PiperOrigin-RevId: 281758729

PiperOrigin-RevId: 281724630

- DRM properties need to be on individual playlist items.

PiperOrigin-RevId: 281718153

This ensures other database readers can continue reading while we do our
write transaction.

PiperOrigin-RevId: 281520758

PiperOrigin-RevId: 281510703

They are all marked with a JavaDoc comment and the @WorkerThread annotation
which is useful if apps are using threading annotations. All other public
methods in the same classes are marked with @AnyThread to avoid the impression
we forgot to annotate them.

PiperOrigin-RevId: 281490301

The current workaround seems to cause compilation errors inside the
testutils module in Android Studio. This seems to fix them.

This doesn't introduce a circular dependency because it's only
the tests in library-core depending on testutils.

PiperOrigin-RevId: 281318192

Note:
- Fixing this uncovers another bug in how audio processor draining
  works, so the test playlist still doesn't play correctly after this
  change.
- Once we reconfigure the audio sink based on the ExoPlayer Format
  rather than the codec MediaFormat in a later change, this change can
  be reverted.

Issue: #6601
PiperOrigin-RevId: 281264149

PiperOrigin-RevId: 281086336

PiperOrigin-RevId: 281084720

- Make NonNull, which is already the case when using the manager builder.
- Better document PLAYREADY_CUSTOM_DATA_KEY, now that newPlayReadyInstance
  is no more.

PiperOrigin-RevId: 281079288

Issue:#4867
PiperOrigin-RevId: 281064793

PiperOrigin-RevId: 281051893

The implementation of writing HDR10+ static metadata assumed that the
application would use default (big endian) byte order for this metadata but
MediaCodec expects the order to match the specification CTA-861.3.

PiperOrigin-RevId: 281050806

PiperOrigin-RevId: 281050034

PiperOrigin-RevId: 281049383

Issue: #6612
PiperOrigin-RevId: 281048324

PiperOrigin-RevId: 281039634

PiperOrigin-RevId: 281037183

ISSUE: #6545
PiperOrigin-RevId: 281032120

This reverts commit 01a4cf98.

This reverts commit cd2c1f2f.

This reverts commit 5c2806ec.

This reverts commit b84a9bed.

This reverts commit 65b49a49.

This reverts commit c8e7ecd3.

*** Original commit ***

Disable test coverage again

https://issuetracker.google.com/issues/37019591 causes local variables can't be found while debugging.

***

PiperOrigin-RevId: 280666758

Also remove the "do we really need to do this" comment for AAC.
Parsing from codec specific data is likely to be more robust, so
I think we should continue to do it for formats where we've seen
this problem.

Issue: #6648
PiperOrigin-RevId: 280575466

PiperOrigin-RevId: 280573887