LordGSama Posted February 4, 2020 Share Posted February 4, 2020 Since I updated to V3 about 15 months ago, I've been having issues with Poweramp recognizing that an external playlist file has been altered. I make playlists on my PC and transfer them to my Android device, usually overwriting old playlist files in the process. After this process, Poweramp has no trouble at all recognizing that a new playlist has been added or that a playlist has been deleted. The UI immediately updates to show the changes. However, in the case of overwriting an existing file, Poweramp V3 has not yet once immediately recognized that the playlist file has changed (despite the change in the file's creation and modified dates). The new additions to the playlist do not appear on the UI and the track count is not updated. Triggering a manual rescan (even completely rebuilding the library) does not correct the playlist. Usually, if I wait a while, Poweramp will eventually update the playlist. I can't really detect a pattern in how long it takes to update or the circumstances surrounding it. Sometimes it only takes a few minutes to recognize that the playlist has changed, sometimes it doesn't recognize it for hours, and sometimes it doesn't recognize it at all. When I update the playlist using a text editor on my android device, Poweramp can immediately detect the change. The problem seems to occur when I overwrite the existing m3u8 files with new ones. It's as though Poweramp can detect when the file is changed but not overwritten (which I don't particularly understand). I don't necessarily think this is a bug but I'm wondering if someone could possibly come up with a way I could avoid this. The m3u8 files that I am transferring to my android device definitely have updated creation and modified dates. Thanks and I'd be happy to provide any additional detail or conduct any tests that might be requested. v3-build-860-arm32-play Android 6.0.1 SM-G900V Link to comment Share on other sites More sharing options...
This topic is now archived and is closed to further replies.