Jump to content

Remember playback positions in tracks

Recommended Posts

Yes, this will most likely be caused by the USB device not being initialised before PA starts scanning the folders for any new music (or before it tries to load any saved track). Thus PA thinks this is a 'new' scanned item, not the same file as before. You could try turning all the auto-scanning features off and see if that helps. 


Share this post

Link to post
Share on other sites
On 4/8/2019 at 4:12 PM, andrewilley said:

Yes, that's how PA works by default. The current track and its playback position are remembered even if you exit the app, close it, or even reboot your phone. This has been standard form day one, and has nothing to do with the relatively new option to permanently save the position of longer tracks and return to them some time late (even if you've played other music in the meantime).


In my experience with PA V3 build 828, the 'Store/Restore Per Track Progress' feature will not function as expected if you restart or shut down and power up your phone.
Refer to this thread for details on my issue:

What I found is this:
In order for PA to remember track progress when returning to a long track - after having listened to another track - you must indeed pause the long track and listen to another track.
If you simply pause the long track, then close PA (or not) and restart your phone, it will return to the beginning of the long track. ** keep reading this post for clarification on this ***
So it appears that the track position is being written to the storage on the phone only when you switch to another track.

Here is another scenario:
You are listening to a long track, and have Store/Restore Per Track Progress enabled.
You are 30 minutes through a 60 minute track. You hit pause, and listen to something else on PA.
With or without restarting your phone, you later resume playing the long track. PA will remember where you were, and restart the track at 30 minutes - the position you were at when  you paused it.
Now, let's say you listen to another 15 minutes of the long track - so you're now at 45 minutes.
For some reason, you need to reboot your phone. You do not leave the long track to listen to anything else before closing PA (actually, it makes no difference if you close PA or not) and rebooting your phone.
You restart your phone, and open PA. Sure enough, the long track you were listening to is up as the current track. But when you press play, you find that it begins playing from the 30 minute position you were at before you paused it to listen to that other track, not the 45 minute position you were at before you rebooted your phone.
I believe this is a bug, or maybe just an oversight by the developers. For whatever reason, PA only writes the Per Track position into storage (non-volatile memory) when the long track is paused and another track is selected, but not when the track is only paused, and no other track is selected.

That said, if you simply pause the long track (or any track, long or short) and close PA - but do not restart your phone - then return to PA and resume playing the same track, it will begin play at the point you left off. This, as has been stated here, has nothing to do with Per Track Progress.

Share this post

Link to post
Share on other sites

Poweramp saves position when it's paused/stopped (normally). If there is sudden poweroff / app kill it's not possible to store position, unfortunately.

Also, some tracks can't be seeked precisely due to (for example) VBR + missing seek table or broken seek table. Poweramp implements fast seek (that is, it can seek files fast and accurately provided seek table exists and correct, or files are CBR), as doing full file decoding just to accurately seek is not battery friendly (esp. for long files).

Share this post

Link to post
Share on other sites
9 hours ago, maxmp said:

as doing full file decoding just to accurately seek is not battery friendly (esp. for long files).

Might be worth making this (another) option? "Attempt Accurate Seek (may consume extra battery)" for example? A lot of longer tracks are likely to be things like podcasts/etc where the user has no control over the encoding, and where seek accuracy can drift by several minutes (such as the fairly extreme example I gave before, http://traffic.libsyn.com/alohomora/Alohomora_Cursed_Child_NYC_Earth_One_and_Earth_Two.mp3 )


Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now