- 26 Oct, 2021 3 commits
-
-
PiperOrigin-RevId: 405598530
andrewlewis committed -
PiperOrigin-RevId: 405592960
andrewlewis committed -
This has been done for (almost) all span types. PiperOrigin-RevId: 405588294
andrewlewis committed
-
- 25 Oct, 2021 14 commits
-
-
PiperOrigin-RevId: 405473686
olly committed -
PiperOrigin-RevId: 405429757
olly committed -
PiperOrigin-RevId: 405408606
olly committed -
PiperOrigin-RevId: 405396600
andrewlewis committed -
PiperOrigin-RevId: 405394994
andrewlewis committed -
PiperOrigin-RevId: 405391455
olly committed -
The static and dynamic metadata now build up in a list, such that when the MediaMetadata is built, they are applied in an event order. This means that newer/fresher values will overwrite older ones. The MediaItem values are then applied at the end, as they take priority over any other. #minor-release PiperOrigin-RevId: 405383177
samrobinson committed -
PiperOrigin-RevId: 405379511
olly committed -
PiperOrigin-RevId: 405377964
olly committed -
PiperOrigin-RevId: 405375352
olly committed -
This introduces a new option `setAudioMimeType` in `TranscodingTransformer.Builder` and a corresponding check whether the selected type is supported. This check is done using `supportsSampleMimeType` which is now part of the `Muxer.Factory` and `MuxerWrapper` rather than `Muxer`. A new field `audioMimeType` is added to `Transformation` and the `TransformerAudioRenderer` uses this instead of the input MIME type if requested. PiperOrigin-RevId: 405367817
olly committed -
Decoded video frames can be large and there is no need to retrieve the corresponding ByteBuffer as we render the decoded frames on a surface for better performance. PiperOrigin-RevId: 405364950
kimvde committed -
The current API exposes an `ImmutableMap` of `TrackGroup` -> `TrackSelectionOverride`. This has several disadvantages: - A difficult to use API for mutation (`ImmutableMap.Builder` doesn't support key removal). - There is no track selection specific methods, how the generic map API mapps to the selection override is not complex but to obvious for a casual reader. - The internal data type is exposed, making internal refactor difficult. This was done to have the API ready as quick as possible. When transitioning the clients to the map API in <unknown commit>, it became clear that the map API was too verbose and not mapping to the clients needs, so utility methods were added to make operations clearer and more concise. Nevertheless, having to use utility method to use easily and correctly an API is not the sign of a good API. This cl refactors the track selection API for several improvements: - Add a type `TrackSelectionParameters` that encapsulate the internal data structure (map currently). - For iteration, expose as a list. - Add a `Builder` for easy mutable operations. - Add track selection specific methods to avoid having utilities functions. - Those operations are the same as `DefaultTrackSelector.Parameters` for easier migration. (`setOverride` was renamed to `addOverride`) - Move `TrackSelection` classes outside of `TrackSelectionParameters` as their own top level classes. The migration of the client code is straightforward as most of it were already using the previously mentioned utility functions that are now native methods. The full migration has not been done yet, and is pending on this cl approval. PiperOrigin-RevId: 405362719
krocard committed -
PiperOrigin-RevId: 404897119
olly committed
-
- 21 Oct, 2021 6 commits
-
-
PiperOrigin-RevId: 404876228
olly committed -
PiperOrigin-RevId: 404851976
olly committed -
PiperOrigin-RevId: 404810682
olly committed -
* @Reason is not a TYPE_USE annotation, so should appear before any modifiers and after Javadocs. (see go/java-style#s4.8.5-annotations) * Curly braces should be used for inline Javadoc tags: {@code ...} (see http://go/bugpattern/InvalidInlineTag) This CL looks good? Just LGTM and Approve it! This CL doesn’t look good? This is what you can do: * Revert this CL, by replying "REVERT: <provide reason>" * File a bug under go/error-prone-bug for category ErrorProneStyle if the change looks generally problematic. * Revert this CL and not get a CL that cleans up these paths in the future by replying "BLOCKLIST: <provide reason>". This is not reversible! We recommend to opt out the respective paths in your CL Robot configuration instead: go/clrobot-opt-out. This CL was generated by CL Robot - a tool that cleans up code findings (go/clrobot). The affected code paths have been enabled for CL Robot in //depot/google3/java/com/google/android/libraries/media/METADATA which is reachable following include_presubmits from //depot/google3/third_party/java_src/android_libs/media/METADATA. Anything wrong with the signup? File a bug at go/clrobot-bug. #codehealth PiperOrigin-RevId: 404769260olly committed -
Th purpose of this change is to speed up the instantiation of the DefaultMediaSourceFactory. PiperOrigin-RevId: 404665352
christosts committed -
SimpleExoPlayer Builder now wraps an ExoPlayer.Builder, rather than the other way round. PiperOrigin-RevId: 404509106
samrobinson committed
-
- 20 Oct, 2021 3 commits
- 19 Oct, 2021 3 commits
- 18 Oct, 2021 11 commits
-
-
PiperOrigin-RevId: 404079772
olly committed -
PiperOrigin-RevId: 404059404
olly committed -
PiperOrigin-RevId: 404007749
olly committed -
DrmConfiguration.Builder#setLicenseRequestHeaders now rejects null, since https://github.com/google/ExoPlayer/commit/8fd1381a84470813827a83921cf3dd2b8603ecb0 This private method isn't needed at all, it's extracting the headers from the item that the DrmConfiguration.Builder is already based on. PiperOrigin-RevId: 403973523
ibaker committed -
This prevents the demo app loading media.exolist.json. The exception was introduced by https://github.com/google/ExoPlayer/commit/8fd1381a84470813827a83921cf3dd2b8603ecb0 PiperOrigin-RevId: 403973062
ibaker committed -
PiperOrigin-RevId: 403965543
olly committed -
PiperOrigin-RevId: 403945085
olly committed -
Issue: #9392 reports occasional IllegalStateExceptions from release() in crashlytics,`with no way to reproduce locally. It seems likely there is a bug somewhere in DRM handling, and ideally we would find that and fix it. However we haven't been able to find the problem, and in the meantime these exceptions cause the entire app to crash. Although this is arguably useful from a debugging perspective, it's obviously a poor experience for developers and users, since all we're actually trying to do is release the session, so maybe we shouldn't strictly care that it's already released? This change replaces the exception with an error log, which might be a useful debugging hint if we see other DRM unexpected behaviour due to references to released sessions being held for too long. PiperOrigin-RevId: 403942546
ibaker committed -
PiperOrigin-RevId: 403928449
olly committed -
PiperOrigin-RevId: 403914807
olly committed -
PiperOrigin-RevId: 403910535
olly committed
-