| Summary: | Would like MusicBrainz to be usable on more than one track at once | ||
|---|---|---|---|
| Product: | [Applications] amarok | Reporter: | Adeodato Simó <dato> |
| Component: | general | Assignee: | Amarok Developers <amarok-bugs-dist> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | ana, kamikazow, myriam, orensbruli, projects.gg.aaron, thomas, torotil |
| Priority: | NOR | ||
| Version: | 1.2.3 | ||
| Target Milestone: | --- | ||
| Platform: | Debian testing | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 2.4 | |
| Sentry Crash Report: | |||
| Attachments: |
Patch to allow musicbrainz queries on multiple files at a time
multiple music brainz queries multiple music brainz queries |
||
|
Description
Adeodato Simó
2005-05-01 04:27:42 UTC
Exactly what I was going to submit! This would be very useful. Created attachment 11906 [details]
Patch to allow musicbrainz queries on multiple files at a time
This will run a musicbrainz query against all files selected. Unfortunately, it
is not against SVN but beta1 of 1.3. I will add an updated patch later in the
week. In the meantime, perhaps someone can tell me if this is the best way of
doing it or not.
Created attachment 11925 [details]
multiple music brainz queries
this is a patch against current svn. it also fixes a problem the previous patch
had with filename encoding.
Created attachment 11926 [details]
multiple music brainz queries
corrected version of patch.
I was just about to submit this too, I'm going through manually now. As far as I can see, this could be done in three ways: just choosing the most likely option for each track (i.e. completely automating it), having the current "MusicBrainz Results" windows open once for each track, and making some kind of new interface with all tracks in it (unlikely). I think it should certainly allow the user to decide if it should be fully automated or ask. What system is implemented in the patch? I too was about to submit this. I think that juk has the best approach for this. In fact, that is the only reason I ever load up juk. Perhaps you could also show the current meta-data for the track in addition to the file name. I haven't looked too hard at the source code, but since they are both kde projects it might be very easy to just "borrow" the code, or even better, pull it out into a new KPart so both projects benefit from the enhancements. I'd vote for having the results window coming up for each track. This is a feature I would enjoy very much. The MusicBrainz Results window for each song would be good enough, but the way I imagine it is highlighting some tracks in my play list, right clicking and choosing "Find Tags with MusicBrainz" from the context menu. Then a dialog would pop up with file names on the left and a drop done list on the right so that each track would have a drop down of the possible results from MusicBrainz. And then a Save button at the button. Also on each drop down would be an option that says "Make no changes" in case MusicBrainz returns a bogus answer. *** Bug 131814 has been marked as a duplicate of this bug. *** *** Bug 144311 has been marked as a duplicate of this bug. *** MusicBrainz has been droped for a better solution to come later in Amarok 2 What will this better solution be? Is there already a bug report for it? I think this wish is still valid until this (or the better feature) is implemented or another report exists that covers this. I use a current Amarok 2.1 snapshot and there's no sign of any "better" solution. In fact there is no solution at all. So much for "WONTFIX": Amarok 2.4 with MusicBrainz support, incl. mass tagging. http://amarok.kde.org/en/releases/2.4/beta/1 Changing to "FIXED". |