Build run (#6226155662, attempt #1) artifacts

Build run (#6226203912, attempt #1) artifacts

Can you review this PR @touwys?

@Borewit

Fixes the repair process, on a selection of playlist entries.

Fixed, and well done, thank you. Will you take care of signing off on #196?

Result what written at the wrong location withing the playlist.

I do not comprehend this remark. Please, elaborate if it is something I should pay attention to?

Will you take care of signing off on #196 (comment)?

Github does close that issue, automatically, it understands "Resolves: #196" and created this relation (see right side):

Result what written at the wrong location within the playlist

Jeremy was a magician with indexes (read index as "track position number"). Operations on the playlist he would forward a list of track indexes to other functions. Then passed the list of indexes to other functions, then those functions would read back the tracks at those positions. Hard to explain, but I just pass the track (objects) to functions. Much simpler and less likely to break. Yet most likely I am the one who introduced this problem while rewriting code.

@touwys, did we also fix #194 with this one?

@touwys, did we also fix #194 with this one?

Yes, I tested it with single tracks, as well as with multiples thereof, and did not notice a recurrence.

The only thing that has changed on my side from the previous tests, is that I am using only a MP3 media directory as reference for the current test-repairs. Previously, I also had a FLAC media directory in there for reference. I mention it, just in case it bears relation to the upset of the repair results, as we have seen it manifest in this issue.