-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Import: allow edit right after applying search results #2441
Comments
Hi! It sounds like you want to edit the candidate metadata, which is actually possible already. At this prompt:
choose the "edit Candidates" option instead of the "eDit" option. Does that do what you want? |
Hey, wait a moment, I've never seen that option!!! Ah, it must be because of (quoting the Edit plugin documentation):
I almost always import files that lack any tags, so I can't use that option :( |
Hmm, that's odd—I wonder why the documentation says that! In a little experiment I ran here, it did actually appear after entering an ID. I can't really think of a reason that would have been a limitation in the past, but maybe it's just out of date somehow? |
You are talking about a different use-case. Here is mine, in detail:
My problem is: I would like to have the beets version 1.4.3 |
Ah, sorry, I did misunderstand. But I did another experiment here too, using the "Enter search" option… and the screen that appeared after that did include the "edit Candidates" option. I'm guessing you had a single high-confidence match. Have you tried choosing "More candidates"? I think the option should then appear after it shows you a listing. |
No it doesn't. I tried removing the if clause in Once we fix this, the next step would be to remove the limitation of only being able to edit the item-level fields, and also allow editing the album-level fields. |
Weird! I don't know why I can't seem to reproduce the same problem. Are you running the latest source? (Sorry it's been so long since the last release—totally my fault.) |
I was running 1.4.3, so I pip-uninstalled it, downloaded the latest zip source from github, installed it via setup.py and repeated the test, but I still can't get the edit candidates option. I also tried moving away my config file, to use the default config values: same result. The kind of files that I usually import are m4a, with no information in the file name (e.g. 01.m4a etc) and sometimes the artist and/or title tag (but often they have no tags). |
Weird! I'm still pretty stumped. I don't know why we're not seeing the same behavior. Any chance you could include some pastes from full interactions—one where you did get the prompt and one where you didn't? Including verbose output would be even better. |
...
Ok, I hope this can help. See the attached images. Images 01.jpg and 02.jpg show what happens when I run Image 03.jpg shows what happens when I repeat the same operation on a file that already has tags. All this with beets 1.4.5. I'd really love to see this fixed, so please let me know how I can help. |
Thank you for the extra detail! That really did help shed light on what was going on. Essentially, the plugin was seeing the original candidates found for an imported album, of which there were none, instead of the new ones after doing the manual search. Can you please try out #2731 to see if it solves the problem for you? |
Thanks a lot! Yes, it solves the problem, and I haven't noticed anything strange at least from a user's point of view. |
Uhm, actually I've now noticed a problem: if I import an album making some changes with the "Edit candidates" option, beets doesn't fetch and embed the album art automatically, as it always does in my configuration. I tried re-importing the same album without making any changes via "Edit candidates", and beets correctly fetches and embeds the album art as expected. I don't know if this is a regression in your patch, or if it's the default behaviour when "Edit candidates" is used (I had never used it before! :) ), anyway it seems a bug to me. |
Hmm! Would you mind trying it with and without the patch to see if that's the cause? A verbose log from when things went wrong would also be really helpful. |
Ok, I tried without the patch and the album art problem is still there. This is what happens when I import something without making changes via "Edit candidates":
And here's what happens when I make some changes: it seems the fetchart and embedart plugins are not called at all:
|
Very strange! Well, it sounds like this is a separate issue deserving of a separate investigation, unfortunately. In the mean time, I'll leave this PR open for a little while longer so we can test it more thoroughly before merging. |
Indeed, I opened #2734 for that. |
Feature request. Often the information retrieved automatically by search engines during the import procedure needs some corrections (e.g. most CD reissues have the year of release as "year", instead of the year of the original recording): I'd like to make these fixes right away, using the "edit" command, instead of waiting for the import procedure to finish, and then run
beet edit ...
with the proper query to only match the album just imported.Currently an "Edit" command is available in import mode, but it can be used alternatively to the Search command (i.e. starting from a blank template), it would be very convenient if "Edit" would be available right after applying the results of a search, using those as starting values in the editor.
The text was updated successfully, but these errors were encountered: