Or you can use ExoPlayer component, because ExoPlayer works with aab.
See: Error 701 when installing app from the play store
The exoplayer component has bugs with fast sounds. For buttons it’s bad because of that…
I discovered the problem … wav format is bad, we have to use mp3 format
No, which bugs with “fast sound”?
No, I’ve never used MP3, but always OGG - not least because it’s the only (compressed) audio format that is loopable.
Too bad exoplayer, I click the first button and there is no sound, only the second time I click. long songs, no problems.sound up to 500milliseconds, do not work the first time,
exoplayer solved my problem, but created another one. Rapid sounds up to 300ms happen bug. I will stick with the standard player and format in APK that resolved for now
yes, unfortunately, long voices cause problems as I said workaround is your decision
Of course it works also for the first time, see here:
Please explain this in more detail.
What does long voices mean?
Here is a test aia with an additional sound (creek_250ms.ogg → 250 milliseconds):
ExoPlayer_test.aia (115.4 KB)
No issues with ExoPlayer.
Btw, the ExoPlayer is much faster than the MediaPlayer. Why you should prefer the ExoPlayer (like YouTube, and it’s the same with audio files), see here:
Which issue?
And again: Which issue with long voices?
PLAYER + .mp3 = Error 701 [ aab format ]
Subject owner stated this issue
We already know that long enough.
I reported the bug myself.
Now for the third time: what issues with long voices?
Sorry, because of the translation you don’t understand what I am writing so wait for the error to appear
If the subject owner has reached the solution, there is no need to continue, good luck.
With Exoplayer sometimes not working or not progressing when listening to long sounds
But sometimes it happens not always
@bodymindpower
This has nothing to do with long or short sounds, but with the fact that the ExoPlayer stops in the background (idle / Doze mode) on some devices (especially Samsung). This problem has been discussed extensively in the forum.
In the meantime I have found a solution for this. You need a foreground service for this.
PS: Maybe one of the moderators can split this and merge it with the other topic.
Thanks for the example. I found that the problem is in the initialization of the “sound source”. The sound source must be initialized in the blocks. ! If you boot to the designer screen, the first time you press the button, the sound does not come out.
No, I’ve no issues with that.
Post a test aia that reproduces it.