- 09 May, 2022 12 commits
-
-
PiperOrigin-RevId: 445119411
huangdarwin committed -
Change test name prefix from `transform` to `transcode` for consistency. PiperOrigin-RevId: 445106224
claincly committed -
PiperOrigin-RevId: 445098397
bachinger committed -
We add an entire class like we do for parsing other codec initialization formats; it's currently not doing any parsing though (... initialization data is really simple for AV1 though: just the entire contents of the box). For testing, we add the sample file, having been re-encoded with ffmpeg (and we also happen to have another av1 file, too). PiperOrigin-RevId: 444890282
olly committed -
The parameter was removed in a previous CL but wasn't removed from the javadoc yet. PiperOrigin-RevId: 444879675
hschlueter committed -
PiperOrigin-RevId: 444874326
bachinger committed -
PiperOrigin-RevId: 444861268
ibaker committed -
Issue: google/ExoPlayer#10049 PiperOrigin-RevId: 444833508
claincly committed -
This fixes some small niggles: 1. `inferContentType(String)` is documented to take a path, but in the tests we're passing full URIs. 2. A `String` parameter is usually a path, but also a MIME type or an extension. In the new methods, the meaning of a `String` parameter is always clear from the name of the method. 3. `inferContentType(String)` is always passed an extension in 'production' code (which has to be manually prefixed with a dot). 4. `inferContentType(Uri, @Nullable String)` always ignores the Uri if the String is non-null. IMO this logic is clearer to a reader if it's just in-lined at the call-site. These methods are used from the demo apps, so will be part of the stable API. PiperOrigin-RevId: 444826053
ibaker committed -
PiperOrigin-RevId: 444816821
Ian Baker committed -
This can allow apps to test and demonstrate support for videos with pixelWidthHeightRatio != 1. PiperOrigin-RevId: 444815182
huangdarwin committed -
PiperOrigin-RevId: 444787307
Ian Baker committed
-
- 26 Apr, 2022 5 commits
-
-
PiperOrigin-RevId: 444585404
Oliver Woodman committed -
To ensure frame processor operations operate on square pixels, make the frame taller or wider for non-square input pixels. In addition to automated tests, this was tested by changing the inputFormat.pixelWidthHeightRatio in the TransformerVideoRenderer. PiperOrigin-RevId: 444553517
huangdarwin committed -
Remove unused saveTestBitmapToCacheDirectory throwOnFailure option. #cleanup PiperOrigin-RevId: 444516857
huangdarwin committed -
This allows the actual bitmap to be saved, even if output dimensions are different than expected. Otherwise, differing output dimensions would throw an exception, preventing the bitmap from being saved. PiperOrigin-RevId: 444512210
huangdarwin committed -
30 second clips at higher resolutions are useful for testing encoder behaviour compared to shorter clips. PiperOrigin-RevId: 444505865
samrobinson committed
-
- 25 Apr, 2022 1 commit
-
-
PiperOrigin-RevId: 444347415
samrobinson committed
-
- 26 Apr, 2022 22 commits
-
-
https://github.com/google/ExoPlayer/commit/8da6c35bbbae84c91c49fc2d723224642d1670f9
*** Original commit *** Keep AudioTrack on flush as default *** PiperOrigin-RevId: 444327724
samrobinson committed -
PiperOrigin-RevId: 444264961
samrobinson committed -
PiperOrigin-RevId: 444253425
huangdarwin committed -
PiperOrigin-RevId: 444221415
ibaker committed -
The last frame processor could use a different drawing command than a four vertex triangle strip. So we need call its drawing method again instead of assuming the shape. PiperOrigin-RevId: 444217274
hschlueter committed -
Avoid no-op FrameProcessors in VideoTranscodingSamplePipeline, to avoid creating resources for and executing GL for a no-op vertex+fragment shader. EncoderCompatibilityFrameProcessor will still always be exercised. PiperOrigin-RevId: 443675833
huangdarwin committed -
Issue: google/ExoPlayer#10165 #minor-release PiperOrigin-RevId: 443653894
claincly committed -
This test should run on all devices from API 21 (the media uses Baseline profile level 3.0 H.264) to give us coverage of the full pipeline (forcing re-encoding) and SSIM calculation on all devices. PiperOrigin-RevId: 443650002
andrewlewis committed -
Float I-frame intervals are only supported from API 25 onwards (see https://developer.android.com/reference/android/media/MediaFormat#KEY_I_FRAME_INTERVAL). Setting a null value for profile/level can cause a native crash when configuring the decoder. PiperOrigin-RevId: 443647924
andrewlewis committed -
PiperOrigin-RevId: 443620931
claincly committed -
ExoPlayer's default behaviour changed in https://github.com/google/ExoPlayer/commit/b12918d1e6b92763c0a7b870e598d260a052361f. Issue: google/ExoPlayer#10170 #minor-release PiperOrigin-RevId: 443611196
ibaker committed -
Split rotationDegrees changes to EncoderCompatibilityFrameProcessor, a new FrameProcessor. This removes automatic rotationDegrees adjustments from Presentation, which allows Presentation to be used for changes before the end of a FrameProcessorChain pipeline. PiperOrigin-RevId: 443387226
huangdarwin committed -
Issue: google/ExoPlayer#9544 The header must include the word "Basic", but the word is missing. #minor-release PiperOrigin-RevId: 443386880
claincly committed -
The issue with decoding getting stuck is still reproducible on `samsung/beyond1lteeea/beyond1:12/SP1A.210812.016/G973FXXUEGULB:user/release-keys`. PiperOrigin-RevId: 443368546
andrewlewis committed -
PiperOrigin-RevId: 443156130
samrobinson committed -
After this change the test will use EGL_NO_SURFACE or a pixel buffer surface if using no surface is not supported. PiperOrigin-RevId: 443113794
hschlueter committed -
Some devices under report their resolution support, like 2144 for 2160 in H265, 1072 for 1080 in H264. This CL only takes care of these two cases, - reporting 1920x1080 is supported when the device reports 1920x1072, and - reporting 3840x2160 is supported when the device reports 3840x2144 PiperOrigin-RevId: 443095042
claincly committed -
When downlading an adaptive asset, if an ExoPlaybackException happens during track selection, the player raises an UnsupportedOperationException which is not handled gracefully and can crash the app main thread. This change catches the error and forwards it to DownloadHelper.Callback.onPrepareError() as an IOException. PiperOrigin-RevId: 443015332
christosts committed -
PiperOrigin-RevId: 442844189
samrobinson committed -
PiperOrigin-RevId: 442835160
huangdarwin committed -
PiperOrigin-RevId: 442826391
hschlueter committed -
This is safer because it will prevent any future problems with creating a new FrameProcessorChain before the previous one has completed its async release. From [eglDestroyContext documentation](https://www.khronos.org/registry/EGL/sdk/docs/man/html/eglDestroyContext.xhtml): "If the EGL rendering context is not current to any thread, eglDestroyContext destroys it immediately." The context isn't current to any thread here because GlUtil calls eglMakeCurrent with EGL_NO_CONTEXT before calling eglDestroyContext. So everthing should be released once the FrameProcessorChain's release task terminates. PiperOrigin-RevId: 442807484
hschlueter committed
-