SDK / exoplayer

TI can use this Format as part of creating the SamplePipelines.

PiperOrigin-RevId: 513777622

Renamed MuxerEndToEndTest.java to Mp4MuxerEndToEndTest.java to align it with class under test.
Removed muxed prefix from dump file name because Mp4 implicitely means muxed only.

PiperOrigin-RevId: 513574681

r2.18.4

#minor-release

PiperOrigin-RevId: 513555559
(cherry picked from commit 4f68f891)

#minor-release

PiperOrigin-RevId: 513533248
(cherry picked from commit af6807d9)

PiperOrigin-RevId: 513516267
(cherry picked from commit 658b5030)

#minor-release

PiperOrigin-RevId: 513555559

#minor-release

PiperOrigin-RevId: 513533248

PiperOrigin-RevId: 513529059

This implements `GlShaderProgram` (and is GL-specific).

PiperOrigin-RevId: 513528160

PiperOrigin-RevId: 513516267

PiperOrigin-RevId: 513514142

#minor-release

PiperOrigin-RevId: 513488487
(cherry picked from commit 3b16231e)

PiperOrigin-RevId: 513482096
(cherry picked from commit b634005c)

#minor-release

PiperOrigin-RevId: 513488487

PiperOrigin-RevId: 513482096

Add some additional information which methods to override
for available commands.

#minor-release

PiperOrigin-RevId: 513251805
(cherry picked from commit a64a9e67)

PiperOrigin-RevId: 513213229
(cherry picked from commit d2ba2907)

These are not supported by Dackka

#minor-release

PiperOrigin-RevId: 513176533
(cherry picked from commit ef5a1ce9)

#minor-release

PiperOrigin-RevId: 512897269
(cherry picked from commit 48047cf9)

#minor-release

PiperOrigin-RevId: 512890813
(cherry picked from commit 13a86b38)

Once the value returned from AudioTimestampPoller advances, we
only need getPlaybackHeadPosition to sample sync params and
verify the returned timestamp. Both of these happen less often
and we can avoid calling getPlaybackHeadPosition if we don't
actually need it.

PiperOrigin-RevId: 512882170
(cherry picked from commit 4cf7d3c7)

Playback parameter signalling can be quite complex because
 (a) the renderer clock often has a delay before it realizes
     that it doesn't support a previously set speed and
 (b) the speed set on media clock sometimes intentionally
     differs from the one surfaced to the user, e.g. during
     live speed adjustment or when overriding ad playback
     speed to 1.0f.

This change fixes two problems related to this signalling:
 1. When resetting the media clock speed at a period transition,
    we don't currently tell the renderers that this happened.
 2. When a delayed speed change update from the media clock is
    pending and the renderer for this media clock is disabled
    before the change can be handled, the pending update becomes
    stale but it still applied later and overrides any other valid
    speed set in the meantime.

Both edge cases are also covered by extended or new player tests.

Issue: google/ExoPlayer#10882

PiperOrigin-RevId: 512658918
(cherry picked from commit d3639771)

PiperOrigin-RevId: 513289716

Used an actual captured image with set color profile for test to minimise the chance of the test flaking. Also renamed the media/bitmap/overlay folder to media/bitmap/input_images for clarity.

PiperOrigin-RevId: 513273353

If the Metadata passed to SegmentSpeedProvider is null, then the
SegmentSpeedProvider will always return 1f from getSpeed.

Initializing a SpeedChangingAudioProcessor requires a SpeedProvider.
Once configured,this audioProcessor is always active, so buffers are
passed through it. Because getSpeed is always 1, the processor performs
a no-op, but still has to do a buffer copy for each buffer.

By not initializing the audio processor when metadata is null, this
copy can be skipped and the audio pipeline is more performant.

Note: This change does not affect the multiple media-item case, which
is not supported with speed changes, as per Transformer API
documentation.
PiperOrigin-RevId: 513261811

Add some additional information which methods to override
for available commands.

#minor-release

PiperOrigin-RevId: 513251805

Changes include:
1. Move the test fine into muxer module.
2. Use dump file infra for test cases.
3. Add one additional test for adding float metadata.
4. Few improvements in the code.

In next CL will remove Mp4 term from the file name as we are not using this term in test file names.

PiperOrigin-RevId: 513222506

PiperOrigin-RevId: 513213229

PiperOrigin-RevId: 513186205

These are not supported by Dackka

#minor-release

PiperOrigin-RevId: 513176533

We shouldn't have this logging unless we really need it to debug
a specific problem, as it can be noisy (even at debug level).

PiperOrigin-RevId: 512904412

Reference docs are now generated by the standard Jetpack machinery, so there's no need for us to generate these docs ourselves.

PiperOrigin-RevId: 512898248

#minor-release

PiperOrigin-RevId: 512897269

#minor-release

PiperOrigin-RevId: 512890813

This lays the groundwork for full multi-asset, and more particularly for
adding looping background audio.

PiperOrigin-RevId: 512887888

Once the value returned from AudioTimestampPoller advances, we
only need getPlaybackHeadPosition to sample sync params and
verify the returned timestamp. Both of these happen less often
and we can avoid calling getPlaybackHeadPosition if we don't
actually need it.

PiperOrigin-RevId: 512882170

Based on 1000 test runs an emulator, with the current timeout releasing
fails (even with no custom effects) about one percent of the time.
Releasing normally completes in about 30 ms but occasionally
`eglTerminate` took up to 200 ms (and even releasing an effect
took up to 80 ms in one case).

With the new timeout of 500 ms, we still catch stuck effects reasonably
quickly but the number of flaky test failures should be less than one in
ten thousand.

PiperOrigin-RevId: 512690715

This timeline will be used in unit test cases of follow-up
CLs. It basically can be used to emulate the timeline created by a
multi-period live media source when the real time advances.

PiperOrigin-RevId: 512665552