mirror of
https://github.com/samsonjs/media.git
synced 2026-04-05 11:15:46 +00:00
c0e8513b7a
Issue: When running the Transformer related test cases, the tests are flaky because the order in which audio and video samples are interleaved seems to differ in few instances. Root cause: When running a transformation the sample producer (Asset loader) and sample consumer (Sample pipeline) both runs on different thread and theoretically there is no reason for behaviour to be deterministic because the number of samples produced/written depends on how fast individual thread works. So it is indeed surprising that test somehow worked deterministically in majority of instances (may be something to do with Robolectric environment). Solution: Since we don't expect the order of sample interleaving to be deterministic, make the dumping logic deterministic where all the video samples will be collected and then dumped together (similarly for audio). This would mean we won't be able to see the interleaving so for that we need to add separate test case verifying the interleaving logic only. Pending: Test case for interleaving. PiperOrigin-RevId: 540930871 |
||
|---|---|---|
| .. | ||
| src | ||
| build.gradle | ||
| README.md | ||
Transformer module
Provides functionality for transforming media files.
Getting the module
The easiest way to get the module is to add it as a gradle dependency:
implementation 'androidx.media3:media3-transformer:1.X.X'
where 1.X.X is the version, which must match the version of the other media
modules being used.
Alternatively, you can clone this GitHub project and depend on the module locally. Instructions for doing this can be found in the top level README.