A number of recent issues (#10, #14, #16, and possibly #17) could be addressed by finally switching to ExoPlayer as per the suggestion of @rohansohonee . The reason for not considering it until now was the difficulty of implementing untilPosition in ExoPlayer, however studying the APIs further, I think this should actually be possible as well.
It will take some time to read through all the documentation, but I plan to focus my attention here for the next while.
ryanheise
All 6 comments
The latest commit now integrates ExoPlayer, for testing.
I have not yet changed anything substantial in behaviour, but this will make it easier resolve the other open issues listed above.
ryanheise
on 31 Dec 2019
Will test and report.
(Edit)
Can you please set the min sdk to 16.
rohansohonee
on 31 Dec 2019
I'm very happy when you integrate Exoplayer. I will try to use it in my app and report to you if I have issues.
cnttechio
on 31 Dec 2019
@rohansohonee Done.
ryanheise
on 31 Dec 2019
@ryanheise
In java in the audioplayer constructor the player.addListener(this) is being used as the same listener when creating two instances of audioplayer in dart code.
The id are different but the listener is same.
This means on stopping player A, the player B also stops.
Am I correct???
rohansohonee
on 31 Dec 2019
That shouldn't be the case, since each instance of the audio player results in a new instance of the Java AudioPlayer class.
ryanheise
on 31 Dec 2019
Related issues
dankydev
路
6Comments
fabiochen
路
3Comments
llucax
路
9Comments
tcerven
路
10Comments
cnttechio
路
13Comments
Most helpful comment
The latest commit now integrates ExoPlayer, for testing.
I have not yet changed anything substantial in behaviour, but this will make it easier resolve the other open issues listed above.