Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Select Closest Matches" Modal & Playlists Editor • Mark Those Tracks For Which Closest Matches Could Not Be Found #292

Open
touwys opened this issue Dec 3, 2024 · 0 comments

Comments

@touwys
Copy link

touwys commented Dec 3, 2024

Steps

  1. Open a playlist due for repair in the Playlists Editor.
  2. Select the tracks in need of repair.
  3. Open the Context Menu for the selection, and select to run Select Closest Matches.
  4. Modal opens.
  5. Let the repair finish.

The Select Closest Matches modal often ends up delivering matches that are unsuitable. However, there is no way to tell to keep the suitable and the unsuitable tracks apart. Once the modal is closed on OK, all the unsuitable tracks are now disguised by their new ("false positive") matches, and users have no way of identifying these undesirable tracks in order to locate and correct them by other means available. Such as, is usually done via `Replace Selected Entries', available in the Context Menu.

What may go a long way toward fixing the aforesaid dilemma, is a distinct marking for all the unsuitable matches. This mark is first user-applied in the Select Closest Matches modal to all those track matches found to be unsuitable. The marking is carried over to sync with the same tracks listed in the playlist under edit. This "mark" can, for instance, take the form of a clearly visible red X or checkbox.

Note: in order to keep the unsuitable track matching process relational the "marked" tracks should retain their original i.e. unmatched/unchanged (pre-modal) file names.

Concurrent with this proposal?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant