r2.9.4 #5388
Merged
r2.9.4 #5388
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This also applies when seeking or transitioning to unprepared media, which isn't clear from the current documentation. Issue:#5267 PiperOrigin-RevId: 226486685
This is the same as in SsMediaSource. PiperOrigin-RevId: 225001911
PiperOrigin-RevId: 225812585
See also ietf-wg-cellar/matroska-specification#269. PiperOrigin-RevId: 226758584
PiperOrigin-RevId: 227500707
Issue: #4114 PiperOrigin-RevId: 227516509
PiperOrigin-RevId: 227520168
PiperOrigin-RevId: 227646358
ExoPlayer methods must not be called from any thread besides the specified app thread. Therefore we shouldn't use them here. Using a regular Handler instead is fully equivalent. Issue:#5240 PiperOrigin-RevId: 227650489
PiperOrigin-RevId: 227668426
Issue:#5312 PiperOrigin-RevId: 227673949
If a negative value is read, sniffing should just fail. PiperOrigin-RevId: 227689568
PiperOrigin-RevId: 227813461
PiperOrigin-RevId: 227822937
Also configure the FFmpeg context to ignore errors as far as possible (this appears to have an effect only for certain decoders). Issue: #5293 PiperOrigin-RevId: 227851397
These are part of published IMA SDK 3.10.2. PiperOrigin-RevId: 227861713
Issue:#5320 PiperOrigin-RevId: 228142567
…riants Issue:#5313 PiperOrigin-RevId: 228155222
Setting the target conpatibility only seems to work for Java. Added the equivalent Kotlin config options to the docs. Issue:#5276 PiperOrigin-RevId: 228482496
The window object is used without being filled with data. This used to work well for most cases as the same live stream is sending regular updates and the first update is almost never used if it's not the first item in a playlist. It causes problems when the first timeline update of a live stream is actually used for playback (e.g. when the live stream is lazily prepared in a playlist and played first). PiperOrigin-RevId: 228530232
Issue: #4519 PiperOrigin-RevId: 229145790
We currently forget whether a source is seekable at re-preparation. This was implemented intentionally this way under the assumption that we really can't seek until we have loaded the seek map again. However, seek operations are only allowed after a media period is prepared. So there is no harm in remembering whether a source is seekable. This problem currently prevents reusing ClippingMediaSources with ExtractorMediaSource and a non-zero start clip position. Issue: #5351 PiperOrigin-RevId: 229169441
Issue: #5378 PiperOrigin-RevId: 229261658
…ion. The buffered position is currently based on the mimimum queued timestamp of all AV tracks. If the tracks have unequal lengths, one track continues loading without bounds as the "buffered position" will always stay at the shorter track's duration. This change adds an optional buffer flag to mark the last sample of the stream. This is set in the Mp4Extractor only so far. ExtractorMediaSource uses this flag to ignore AV streams in the buffered duration calculation if they already finished loading. Issue:#3670 PiperOrigin-RevId: 229359899
PiperOrigin-RevId: 229364563
… track groups. When the extra adaptation set of a switch group isn't defined in the manifest, we currently assume it's the first adaptation group. This either leads to wrong grouping or duplicate track groups. Such a case may easily happen if the manifest is filtered such that only one of the switch adaptation sets will be present in the manifest. PiperOrigin-RevId: 229365379
|
Is there anything blocking this release? I'm waiting for the fix for #4114 to release my app.. |
|
We have one or two things that we want to add still. It'll be soon though (probably early next week). |
Issue: #5344 PiperOrigin-RevId: 229527963
That's the same position set in MediaPeriod.prepare (where it may be removed in the future). Having the position at an earlier point is necessary to fix an issue with lazy preparation in ConcatenatingMediaSource where the prepare position was assumed to be known but MediaPeriod.prepare hasn't been called yet. Issue:#5350 PiperOrigin-RevId: 229756637
Issue:#5402 PiperOrigin-RevId: 229758525
The Amlogic awesome decoder reduces the video size of interlaced videos by half if the internal configuration isn't force reset with new maximum input size values. The product of these new values must exceed 1920x1088 to force the reset. Issue:#5003 PiperOrigin-RevId: 230206675
Change the dependency to the new monolithic GVR SDK target. PiperOrigin-RevId: 229931549
PiperOrigin-RevId: 230213842
ExoPlaybackExceptions of type SOURCE are always associated with the loading period and thus we can use the event time for the loading period in onPlayerError. Renderer and unexpected exceptions are still associated with the currently playing period. Issue:#5407 PiperOrigin-RevId: 230216253
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.