SDK / exoplayer

This methods allows to replace single items or a range of items directly
without using separate operations for add and remove. The advantage is
more readable code for apps and the potential for player
implementations to optimize this process (e.g. only replace values
without interrupting playback).

The current change just introduces the API with its default behavior.
The default logic will be removed again in the future in favor of
better logic in the Player implementations.

Issue: google/ExoPlayer#8046
PiperOrigin-RevId: 532151471
(cherry picked from commit 7289186c937245a4f328f4c9b6e9cda34129306a)

PiperOrigin-RevId: 532136692
(cherry picked from commit 4518dbfdc8e6d6228d2a39e0db4bb1b6245e15d7)

Use `DefaultDrmSessionManager.Builder` instead.

#minor-release

PiperOrigin-RevId: 532102375
(cherry picked from commit 9d039c6ff0452431d8ec30d42a615b4e85602e5d)

Allow the VideoFrameProcessor to output multiple textures at a time, so that
lifetime of textures is up to the consumer calling VFP.releaseOutputFrame.

The FinalShaderProgramWrapper also has a new maxCapacity limit added, to ensure
the a reasonable amount of textures is used and avoid using up memory.

PiperOrigin-RevId: 532094256
(cherry picked from commit 025f71bec45e06b19b7237967af2677b84387b08)

When exporting compositions with multiple images in a row, transformation could
get stuck if a shader was ready to accept input when end-of-stream was already
signaled and queued from upstream. Fix accounting for the downstream capacity.

Manually tested on concatenations with several images and several videos in a
row, by adding logging and verifying the capacity updates as expected across
edited media item transitions.

PiperOrigin-RevId: 532088793
(cherry picked from commit 73d05d5d9dc6fdf06c59c6cb2247efba3bbc9f86)

Use `DefaultBandwidthMeter.Builder` instead.

#minor-release

PiperOrigin-RevId: 532069549
(cherry picked from commit 8a9ac8a9de8a62f33f61257ace98440f4ab22bfc)

In the past, the SequenceAssetLoader was released in TransformerInternal
when the export ended.

https://github.com/google/ExoPlayer/commit/782f19edcf9dcc4ecf47dc32776429990c4a928f was made to release the SequenceAssetLoader earlier, when
loading ended. This was causing player release timeouts because the last
AssetLoader in the sequence was released before the SamplePipelines (see
https://github.com/google/ExoPlayer/commit/78669f874309aa1ea9d7679707afde8f747f0c2b for more information).

The code that was releasing the SequenceAssetLoader was first commented
out because we didn't have an understanding of what was happening.

This change removes the early SequenceAssetLoader release all together.
It doesn't have any effect as this code was already commented out.

PiperOrigin-RevId: 532065673
(cherry picked from commit ff515c1d74339df8dad11ed7b9ea6c571d3c90e9)

The output end-of-stream notification from the last shader could theoretically
arrive before the latch for detecting it is created, which might cause waiting
on the latch indefinitely. Create the latch before signaling end of stream so
that it's guaranteed to be set before the end-of-stream signal arrives.

PiperOrigin-RevId: 532056472
(cherry picked from commit 53c379cb98874c7697965a82fbd2aa29063a238b)

Use a non-deprecated constructor that takes a `DatabaseProvider`
instead for better performance.

#minor-release

PiperOrigin-RevId: 532046598
(cherry picked from commit 2dd3c3b31b758f24c9b2ff25479e63a8ddf1dd0d)

*** Original commit ***

Rollback of https://github.com/google/ExoPlayer/commit/221a56da38d52ae3f963dfd9e38de11262c0b725

*** Original commit ***

Rollback of https://github.com/google/ExoPlayer/commit/749d77b1d9989d091dc11269087093bc2c48d216

*** Original commit ***

PiperOrigin-RevId: 531530885
(cherry picked from commit 7e630fa90f85c29f9c2e6ac49e8ee176220aa6e0)

This can provide more information to help debug muxer errors

PiperOrigin-RevId: 531521974
(cherry picked from commit baeab6d06446cbfa2df33c30e6cf33084d031495)

This module will contain functionalities common to extractor and muxer.

PiperOrigin-RevId: 531501602
(cherry picked from commit 4cfab48709d29be3f1b0cfdb148ce1548f7f26c5)

Mp4Muxer supports adding Metadata track.
Added test file to cover this scenario.

PiperOrigin-RevId: 531496409
(cherry picked from commit 1bcd0cefd6ea8dd208f0829f810824fd0f9a97f1)

*** Original commit ***

Rollback of https://github.com/google/ExoPlayer/commit/f13f87ab58f7ee0de7d097364343f564ec8300a7

*** Original commit ***

Create InAppMuxer in transformer

To use the InAppMuxer, the client needs to pass InAppMuxer Factory.

***

***

PiperOrigin-RevId: 531470081
(cherry picked from commit 19bfa54011b5dd6b21c7839e1b488fc2b0904cbe)

The name was changed in https://github.com/google/ExoPlayer/commit/052c358dcd01481c3d1e2f9bec26775fcc2b04ba
and this check wasn't updated, meaning publishing no longer worked
(it didn't publish anything, just printed lots of warnings like
`Skipping task ':test-utils-robolectric:publish' as it has no
actions.`). This change means the check is now using the same
source-of-truth as the root project name, so it shouldn't go out of
sync again.

#minor-release

PiperOrigin-RevId: 531457952

Until the linked bug is fixed, relax constraints to allow this one device to
pass, to suppress failures and avoid triage toil.

PiperOrigin-RevId: 531259233

This was added in https://github.com/google/ExoPlayer/commit/75cde0aa4780371dabce8b847179aec8170891db
but was accidentally exported to the exoplayer2 GitHub repo (where
`MediaLibraryInfo` is not present).

#minor-release

PiperOrigin-RevId: 531235570

PiperOrigin-RevId: 531233480

PiperOrigin-RevId: 531193242

This change adds end-to-end Robolectric playback tests which handle
the scenario the player is playing audio via passthrough and
AudioTrack raises the ERROR_DEAD_OBJECT error upon which the player
attempts to recover by switching to another audio format.

PiperOrigin-RevId: 531180183

PiperOrigin-RevId: 531180020

The texture input tests in TransformerEndToEndTest were not passing on
Pixel 7. Implemented a fix and fixed other minor threading issues I
spotted while looking at the code.

PiperOrigin-RevId: 531141659

PiperOrigin-RevId: 531123743

Find and replace "mime" to "MIME", where appropriate, throughout media3.

PiperOrigin-RevId: 531122121

*** Original commit ***

Create InAppMuxer in transformer

To use the InAppMuxer, the client needs to pass InAppMuxer Factory.

***

PiperOrigin-RevId: 531056436

#minor-release

PiperOrigin-RevId: 530935437

PiperOrigin-RevId: 530888319

PiperOrigin-RevId: 530878135

PiperOrigin-RevId: 530711523

To use the InAppMuxer, the client needs to pass InAppMuxer Factory.

PiperOrigin-RevId: 530684007

Verified by running all the tests in mh (excluding the analysis tests) on a pixel 7 pro

PiperOrigin-RevId: 530655237

Tone-mapping an HDR video with MediaCodec on sm-s908u1 was timing out.
The reason for that is that the decoder was dropping frames, and the
ExternalTextureManager was therefore never propagating the end-of-stream
signal.

There was already a workaround for a similar issue but restricted to
sm-f936b. Removed the model check as the bug is probably present on more
devices.

PiperOrigin-RevId: 530639437

Exceptions thrown when switching AssetLoader were not reported through
the error listener. Therefore, the resources were not released and the
export was not ending.

PiperOrigin-RevId: 530626300

PiperOrigin-RevId: 530624195

Allow use of H265/H264 codecs for Dolby Vision video.

Also, reflow ExoPlayer code to use this new utility class

PiperOrigin-RevId: 530619388

If tone-mapping was requested for a device supporting HDR encoding,
isToneMapped was false in VideoSamplePipeline.EncoderWrapper. This was
causing the encoder to expect HDR.

Also did some renamings to improve readability

PiperOrigin-RevId: 530584010

similar error to https://github.com/google/ExoPlayer/commit/2c4a567c74088c639d699eeefe139c38e254e230L `registerInputStream` sets the textureManager, so reordering makes sure the textureManager is set before you set the frame info. This is important for texture input, where the frame info provides the width and height.

PiperOrigin-RevId: 530579584

PiperOrigin-RevId: 530578549

Adding items to an empty playlist is slightly different from adding
items to a non-empty playlist, because the former usually requires to
handle a change in the current item, position and playback state,
while the latter is not expected to affect the current item, position
or state.

The current ExoPlayer and SimpleBasePlayer code doesn't account for
this difference, leading to inconsistent behavior between
setMediaItem(s) and addMediaItem(s) when called on an empty playlist.

PiperOrigin-RevId: 530549928

PiperOrigin-RevId: 530314222