MaxOfS2D Posted October 30, 2018 Share Posted October 30, 2018 After a cold start (app wasn't in memory or was force closed), the previous song will play for a few seconds, and then seamlessly switch into the very first song of the playlist, at the same timestamp. After that, shuffle is broken: the songs play in order (which is, in my playlist, alphabetical sorting) until you fix shuffle by picking a track manually or switch playlists back & forth. Here's a video of the issue. Note that I am not triggering the first track switch: that's the bug. The button doesn't light up and you can't see the little "touch feedback" dot, which should be proof enough I'm not messing with you Link to comment Share on other sites More sharing options...
maxmp Posted October 30, 2018 Share Posted October 30, 2018 Thanks for the report. I don't think I can reproduce that. Will keep eye on similar reports, may be some specific reproduce details will help. Poweramp can forcibly change track - if it's missing after the rescan (which usually happens during cold start), but it shouldn't play it (should go to paused state). There is no code which reloads it into playing state. Can you please try to disable Initial rescan in Poweramp Library Settings => Scanner and check what happens than? Link to comment Share on other sites More sharing options...
MaxOfS2D Posted October 31, 2018 Author Share Posted October 31, 2018 Yep, I can confirm that disabling "initial rescan" fixes it and that it is responsible for this issue on my device. Thanks for the speedy reply In case this is important info: I'm on a Galaxy S7 Edge (SM-G935F) with Android 8.0, and all of my music library is on a SD card, not the phone's internal storage. I can also reproduce this issue with a manual scan! See this video: Link to comment Share on other sites More sharing options...
Blasem Posted October 31, 2018 Share Posted October 31, 2018 I have the same issue, it always happen in my Playlists. I will open the app and it will show the last music I was playing in the playlist, so if I hit play poweram will go automatically to the first song of the playlist and it will be in the same secs as the previous song was when Poweramp was closed. Link to comment Share on other sites More sharing options...
maxmp Posted November 1, 2018 Share Posted November 1, 2018 In build 804 I tweaked this a bit - it may help with the issue (or make it worse:-) as I can’t reproduce/test it). To be published tonight. Link to comment Share on other sites More sharing options...
MaxOfS2D Posted November 2, 2018 Author Share Posted November 2, 2018 As of 804 a rescan still exhibits this behaviour, however now it pauses when the track gets reset to the first one. (it still arrives at the same timestamp too) Link to comment Share on other sites More sharing options...
maxmp Posted November 2, 2018 Share Posted November 2, 2018 I can’t reproduce this issue, but from your description and code analysis this can happen only if track paths match (the same position/previously resuming). Can you please do a Full Rescan once? Link to comment Share on other sites More sharing options...
maxmp Posted November 2, 2018 Share Posted November 2, 2018 Can you please check this build: Please let me know if it works. Link to comment Share on other sites More sharing options...
MaxOfS2D Posted November 3, 2018 Author Share Posted November 3, 2018 On 11/2/2018 at 2:22 PM, maxmp said: Can you please check this build: Please let me know if it works. It did! Running a rescan while my file-based playlist is active is not pausing / restarting it / breaking shuffle anymore. Thank you :) Link to comment Share on other sites More sharing options...
Blasem Posted November 4, 2018 Share Posted November 4, 2018 On 11/2/2018 at 10:22 AM, maxmp said: Can you please check this build: Please let me know if it works. Thx for the last update because it fixed! I updated my Poweramp some secs ago and it didn't reset the position of the track! v3-build-805-play Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.