Problem exporting playlists as usual

[Kloppstock]

1: Exported playlists: 0.

Why is this happening? i have tested serveral folders on my SD-card and they generates 0 now,

Yesterday though it exported several playlist that was not M3u8, why not M3u8 lists?

 

 

 

2: The other problem, when i press Rescan/Resolve playlists it removes newley added songs to a playlist.

and it goes back to the amount tracks that was present in the list during a past moment it have defined self that cant be understood by the user,

why not all are being removed, i jave notcied that this scan can remove error-playlists from showing, but i have no idea what it does above that?

that will say... this removal of new added items to the list, extremly annoying

 

 

 

 

[andrewilley]

M3U8 Playlists are already file-based (i.e. they have been read from your device's storage, rather than created locally within Poweramp) so they wouldn't normally be exported as they are already files. Playlists that are shown without any file extenders (so no .M3U, .M3U8, etc) are internally created and they should get exported to files, using the same base name. There is a tickbox option within the Export screen which can force re-exporting of existing files, but it's disabled by default.

However, it does seem from your second comment that there might be an issue with writing data to your storage location (SD Card). When you make changes to add or remove items from a Playlist file (such as an .M3U8 file) those changes are made in PA's local copy of the list and also meant to be written back to the original file. When you do a Resolve, that file should be re-read from storage and all the entries re-matched with songs in your library. But of course if the write failed, the old list will be read back in from storage. This could be made worse by recent changes in Android, so if your device has suffered from been enhanced by an Android 11 update, it might be worth revoking and re-applying storage permissions.

To test this theory, please make a small change to any .M3U8 playlist (just add one song for example) and then use a File Explorer app to locate the file and load it into a text editor (playlists are plain text). If the earlier write succeeded, you will see the new entry at the end of the file. If it didn't, you will only see the original contents.

Andre

[Kloppstock]

On 4/2/2021 at 7:44 PM, andrewilley said:

M3U8 Playlists are already file-based (i.e. they have been read from your device's storage, rather than created locally within Poweramp) so they wouldn't normally be exported as they are already files. Playlists that are shown without any file extenders (so no .M3U, .M3U8, etc) are internally created and they should get exported to files, using the same base name. There is a tickbox option within the Export screen which can force re-exporting of existing files, but it's disabled by default.

However, it does seem from your second comment that there might be an issue with writing data to your storage location (SD Card). When you make changes to add or remove items from a Playlist file (such as an .M3U8 file) those changes are made in PA's local copy of the list and also meant to be written back to the original file. When you do a Resolve, that file should be re-read from storage and all the entries re-matched with songs in your library. But of course if the write failed, the old list will be read back in from storage. This could be made worse by recent changes in Android, so if your device has suffered from been enhanced by an Android 11 update, it might be worth revoking and re-applying storage permissions.

To test this theory, please make a small change to any .M3U8 playlist (just add one song for example) and then use a File Explorer app to locate the file and load it into a text editor (playlists are plain text). If the earlier write succeeded, you will see the new entry at the end of the file. If it didn't, you will only see the original contents.

Andre

Thank you, it turned out my PA version was old on that old phone it concerns, so that export setting did not exist until updating

Concerning the second problem, it turned out it was only 1 of 7 playlist who had this problem, so i was forced to delete

and reload the playlist into the player.  now it have stopped deleting from that list acctually.