mirror of
https://github.com/afkarxyz/SpotiFLAC.git
synced 2026-04-26 07:35:52 +03:00
[GH-ISSUE #202] [Feature Request] Detect and handle duplicate files before download #170
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/SpotiFLAC#170
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @TomDep on GitHub (Dec 29, 2025).
Original GitHub issue: https://github.com/afkarxyz/SpotiFLAC/issues/202
Description
When downloading a song or a playlist, SpotiFLAC should check whether files already exist in the managed directory (as defined in the File Manager).
If a file is already present, the application should prompt the user to choose whether to :
Most users will likely prefer skipping files that have already been downloaded, so this option should be selected by default.
Additional Requirement
For this feature to be usable and transparent, SpotiFLAC should maintain and expose a list of already-downloaded files once the download process is complete. This could be:
Benefits
Contribution
If this feature is considered useful by others, I would be happy to work on it and open a pull request.
@rcMarty commented on GitHub (Dec 29, 2025):
+1
Also I already created very similar issue (#194)
And I would be glad if you also implement support for .m3u8 playlists
@TomDep commented on GitHub (Dec 29, 2025):
Support for the .m3u8 format seems to be part of another feature and should be implemented separately.
Furthermore, the folder structure is already implemented in the File Manager tab. To my knowledge, it is only used to view the library and rename files from a template.
If by “playlist support” you mean creating a playlist file from downloaded tracks, that would be a good idea to add but also is another feature.
I haven't dig into the code yet but I'm sure we can reutilized the current logic to read/write from the track files.
Also, I'm not sure if the owner of the project is open to pull requests so I'm not going to invest time into this before any validation from them.