-
Notifications
You must be signed in to change notification settings - Fork 856
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: ExoPlayer for Android #1526
Comments
I already started a new branch: But as some features are not available, I thought about using a completely new module like |
@Gustl22 Oh that's great! Looking forward to that! |
@Gustl22 So... Does it work now, or is there any problems? |
@fzyzcjy it's not really functional (only experimental), and I also propose a new module, which does not mess around with the "old" android code. So it may be better to restart from the beginning. |
@Gustl22 I see :) |
# Description The tests in Windows & Android are possibly flaky for this reason: - In general it is not tested, if a source starts to play for app tests. - In the app test for `ReleaseMode.loop`, the source starts to play, but never completes or stops. See: https://github.com/bluefireteam/audioplayers/blob/fe81f3b1e600fe005febbe7cd3da02735a3de004/packages/audioplayers/example/integration_test/app/tabs/controls_tab.dart#L104 . This is now checked by getting the current position. The solution to the problem also raises another issue on Android, as the position can not be retrieved on very short sources, thus they are excluded from these tests and it is expected to make it work with Exoplayer (#1526).
# Description The tests in Windows & Android are possibly flaky for this reason: - In general it is not tested, if a source starts to play for app tests. - In the app test for `ReleaseMode.loop`, the source starts to play, but never completes or stops. See: https://github.com/bluefireteam/audioplayers/blob/fe81f3b1e600fe005febbe7cd3da02735a3de004/packages/audioplayers/example/integration_test/app/tabs/controls_tab.dart#L104 . This is now checked by getting the current position. The solution to the problem also raises another issue on Android, as the position can not be retrieved on very short sources, thus they are excluded from these tests and it is expected to make it work with Exoplayer (#1526). (cherry picked from commit c5b0b6e)
# Description The tests in Windows & Android are possibly flaky for this reason: - In general it is not tested, if a source starts to play for app tests. - In the app test for `ReleaseMode.loop`, the source starts to play, but never completes or stops. See: https://github.com/bluefireteam/audioplayers/blob/fe81f3b1e600fe005febbe7cd3da02735a3de004/packages/audioplayers/example/integration_test/app/tabs/controls_tab.dart#L104 . This is now checked by getting the current position. The solution to the problem also raises another issue on Android, as the position can not be retrieved on very short sources, thus they are excluded from these tests and it is expected to make it work with Exoplayer (#1526).
It seems that many people prefer ExoPlayer than AudioPlayer (eg. https://www.reddit.com/r/androiddev/comments/95l3hc, and searching demo apps in Github for Android + audio). ExoPlayer also seems to have a lot of pros (see https://developer.android.com/guide/topics/media/exoplayer/pros-and-cons), and is an official android thing.
Therefore, shall we switch to ExoPlayer?
The text was updated successfully, but these errors were encountered: