Android - playback, position, seek methods executed in background thread #368
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.
Platforms affected
Android
Motivation and Context
By executing the playback, position, seek, duration and other media manipulation methods by a background thread, performance gain is achieved mostly when multiple audio files are prepared at the same time.
Description
play, pause, stop, seek, setRate, duration methods as well as onPrepared event are executed and handled by a background thread.
Testing
By running in my local application
Checklist
(platform)
if this change only applies to one platform (e.g.(android)
)