However, once doing so, I use the results from avprobe before and after deletion of said tag and I see no difference. I can however delete the tag with success. Notes: In Kid3, when I try to edit data contained in “Arranger”, it will not save. No blame intended in any direction there. What I have found is what I believe to be a malformed metadata resulting from the Picard save… or … something in a format in which tosses Kid3 off… which would mean it is not to spec in some way, in theory. I still only see the Arranger tag though in my trials, but none the less, the happenings are the same. I doubt that is a factor, but it may be as it is a function that is otherwise not done.ĮDIT: I understand I can use the “remove existing tags” as a test, but I would never want that option since Picard does not show ALL tags… I would not know what is actually going to be removed. Oh, if it might matter, I did ‘remove’ a bunch of tags prior to hitting save. The files were a “junk” old rip, so I just tagged as there were no existing tags of value to keep. I also need to consider, with that, that Picard does not show all tags in its view, just the ones it is programmed to show… so it is possible the tag may have been preexisting and I just did not see it / know it was there. I normally do not tag anything in Picard, so there could very well be a setting somewhere or even just user error that is the cause. One thing after reading your reply that came to mind is I do not believe I checked tags prior to using Picard. My plugins are only 4, Add cluster as release, feat artist in titles, generate cuesheet and keep tags.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |