App version
Production
Issue description
There is a slight pause/stutter in between gapless tracks on the latest production release (14.1)
Not sure exactly what version this broke but it definitely worked correctly with the same tracks/files before, and they work completely correctly in Musicbee.
Here are three pairs of tracks where the transition should be completely gapless and flow on with no break. gapless – Google Drive
In the logs I used the Avalanches tracks. I’ll upload a screen recording of this too.
Device type
Phone
Media provider
Local device
Steps to reproduce
Play track.
During transition to next track in queue, there is a stutter - this is notable in tracks where they are supposed to be seamless.
I searched existing issues first
on
I understand that logs are mandatory
on
Log upload name / description
tobyburton96
I was tagged in to check this…
On 15.0.0B1 this stutter is still present. I’ve never used gapless playback in any other software to compare, but there’s just a slight audio stutter/hiccup in the transition. I can blindly spot the transition every time, without even focusing on it.
Tested with one of my own tracks as well. Used ffmpeg to split a track at a random point, so the audio should definitely be continuous on both sides.
Let me know if you’d like additional logs or my audio files to test.
Did @tobyburton96 really tagged you ? WTF …
And your issue with custom split file is probably another one as the one from toby is different and as usual he can’t remember when it started and we need to guess 
Since this is a regression in the Google library that occurred like 2 years ago for that kind of files …
I simply asked him to check the new beta for me, as I am no longer in the beta testing group since I had to leave when an update was broken a few versions ago. Nothing more.
I guarantee you that gapless was working within the last few years. I don’t see why the scenario celorien presented where he has chopped his files would be any different to mine. Could you explain? To clarify, he also tested my files and achieved the same result.
Also, it’s not that I don’t remember when it started. I reported the bug as soon as I noticed it! I just can’t guarantee that I had listened to correctly working gapless songs on each prior version, to be sure at which version it broke.
Because WTF do you ask others users to do your own tests ? And the analysis of those files leads to a Media3 issue present for many years, it’s tied to the files having different kind of data, something a split by ffmpeg should not generate …
Again, usually I would test the beta, which I thought could have fixed it due to the changes in the audio engine. At the moment I am unable to join the beta group. I am grateful for celorien’s help.
Thank you for submitting fixes to media3.
Again you SHOULD NOT HAVE DONE THAT … If you directly bother other users to test things the normal only thing I should do is ban you as users do not register here to be bother by other users.
Do you actually understand that problem or not ? Because you absolutely do not sound like you’d not do that again …
And there’s no reason you actually could not join the beta so well that’s another point …
Right, I understand that those are your rules. I won’t do that again as I do not wish to be banned.
The beta program has been full. I can see that is now not the case but it was previously.
This is basic respect other people rules that usually applies everywhere…
The simple fact that Celorien wrote I was tagged in to check this… clearly show that it was not something appreciated.
I did not think it was anything inappropriate or that I was bothering him. I can see that was a mistake, and now I understand. My apologies.
Since this is a regression in the Google library that occurred like 2 years ago for that kind of files …