-
Notifications
You must be signed in to change notification settings - Fork 601
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
Manual configuration of ID3 tagging #499
Comments
Unfortunately I just realized WMP doesn't play well with the ID3 tags today... I'd guess this issue is going to the back burners. Hmmm what player hasn't completely pissed me off yet |
ah, sorry guys. github issue tracking is pretty bad when you have so many open issues :-) i'm trying to knuckle down and fix this code now - but i think it'd be easier to configure beets to write ID3v2.3 tags than add in a second tagger. beets uses mutagen as the backend, so that's probably where you want to start. if you find anything useful, let me know and i'll add it in on my end. |
As far as I can tell, mutagen will only do v2.4. http://code.google.com/p/mutagen/issues/detail?id=85 Someone created a diff, but that was back in March last year. |
Yeah that's what it looks like. Why doesn't wmp read v2.4 tags? On Mar 22, 2012, at 8:22 AM, fasteasyfreereply@reply.github.com wrote:
|
because it's Microsoft ;p Turns out Amarok is stable in windows finally, so screw WMP. |
Would it be possible to have a Beets configuration page, check off what is wanted in the ID3 tags when it auto-tags? for example, it places two entries for dates and when I auto convert FLAC > MP3 using Folder (date) config it puts both dates, when i just wanted the first entry which is the year. (Same goes for track and trackc) |
See yeah, I want to allow finer control of tagging. For me, personally, beets tags everything perfectly but I know how people are about their music collections. And beets is so robust now that it's almost a waste not to. It will probably be in v2. I'm just cleaning up a lot of code, especially the config stuff, so I'll make sure to fit in a beets config page On Apr 15, 2012, at 10:01 PM, AF9210reply@reply.github.com wrote:
|
What about using http://code.google.com/p/stagger/ to also add v2.3 tags? That would solve everything :) |
I'll look into it but it's not that high on my priority list right now On 12/6/12, dapozt notifications@github.com wrote:
|
I have very little coding experiences but ill try to figure out what needs to be changed (as soon as I got some time). Win8 still doesn't support v2.4 :( Let me follow-up with the devs and ask if it ever will be changed and/or what the reason is. |
Got an answer on why Microsoft doesn't support 2.4 in Windows, please e-mail me if you want the details. dapoztREMOVETHIS@thq.nl |
Currently Beets saves the tags in ID3v2.4 format, which to all intents and purposes is the standard. However, Windows (7) and Media Player (12) don't support 2.4, only 2.3. I can't find any mention of being able to alter this behaviour (either media player or beets), and I've submitted a ticket for this with the Beets project.
How much of a ballache would it be to allow users to switch out the default tagger? Until the Beets team adds the functionality (or I have time to look into writing it myself), a two-step approach is needed (Launch something like MP3Tag and re-save the tags).
Thanks.
The text was updated successfully, but these errors were encountered: