search

beetbox / beets

music library manager and MusicBrainz tagger
http://beets.io/
MIT License
12.78k stars 1.82k forks source link

Ideas for duplicates plugin #370

Closed DjSlash closed 10 years ago

DjSlash commented 11 years ago

The dupelicats plugin is great, but I like to provide some ideas to extend it's functionality. My ideas are mostly based on the fact that the plugin will be able to delete files some day (as stated on the plugin page). Some may be related to #116.

  1. Provide UI for selecting dupes that can be deleted. Give the user enough information to base their decision on (i.e. bitrate, path, length).
  2. In addition, put the most likely to-be-chosen-for-deletion first, based on several parameters: bitrate, not part of an album.
  3. Ability to move files, instead of deleting them. Just for the people who rather want to be sure they don't delete the wrong files by accident.
  4. As long as deleting is not build in the plugin itself, maybe provide some example in the documentation or wiki on how to do it with some CLI magic (I'm trying to work this out myself).
pedros commented 11 years ago

Hi Rutger,

Those are definitely good ideas. I'm in the process of moving out of the country, but I suppose I'll have some time in a couple weeks time to address them. Of course, feel free to work on it yourself if you feel like it!

Pedro

Rutger van Sleen notifications@github.com writes:

The dupelicats plugin is great, but I like to provide some ideas to extend it's functionality. My ideas are mostly based on the fact that the plugin will be able to delete files some day (as stated on the plugin page). Some may be related to #116.

  1. Provide UI for selecting dupes that can be deleted. Give the user enough information to base their decision on (i.e. bitrate, path, length).
  2. In addition, put the most likely to-be-chosen-for-deletion first, based on several parameters: bitrate, not part of an album.
  3. Ability to move files, instead of deleting them. Just for the people who rather want to be sure they don't delete the wrong files by accident.
  4. As long as deleting is not build in the plugin itself, maybe provide some example in the documentation or wiki on how to do it with some CLI magic (I'm trying to work this out myself).

Reply to this email directly or view it on GitHub: https://github.com/sampsyo/beets/issues/370

Formal courtesy between husband and wife is even more important than it is between strangers. -- Lazarus Long

sampsyo commented 11 years ago

Cool ideas; thanks. It seems like we might need two tickets here: (a) prioritizing and selecting duplicates based on certain criteria, a la #116, and (b) option to move aside instead of deleting. If that sounds right, let's open a separate issue to track (b) separately.

DjSlash commented 11 years ago

@pedros I'm afraid I don't have much time to work on it myself (and then I'm still not a real programmer). For the fourth point in my list, I'll share when I have found something that actually works (for me).

@sampsyo Do what you want with it. ;) I started it as one in the first place so the ideas can be discussed before decisions gets made what may get implemented. But yes, when things gets a "go", it might be wise to make seperate issues.

Another idea: find tracks that are very similar, maybe with help of acoustid or just artistname/trackname. For example to find instances as these:

% beet duplicates Cassius
% beet ls -f '$path' Cassius sound
/data/Muziek/singles/c./Cassius - The Sound of Violence.mp3
/data/Muziek/albums/Cassius/2002 - Au rêve/02 - Cassius - The Sound of Violence.mp3
sampsyo commented 10 years ago

@pedros has added a bunch of new stuff to the duplicates plugin, including metadata-based matching (like the previous comment) and a move-aside action. Awesome! Closing this ticket for now; the remaining ideas are best managed as part of the "trumping" line of inquiry.