![]() Tag Editor Plus: an alternative for Windows Media Player's Advanced Tag Editor (screenshot). So my recommendations in your specific case is to use ID3 v2.4 with UTF-8, and if this does not work as expected try v2.4 and v2.3 with ISO-8859-1 encoding.Windows Media Player Plus! includes the following enhancements: UPDATE: I just realized that for ID3 v2.3, which I recommended for compatibility and which you probably already use, you only have the choice between UTF-16 and ISO-8859-1. But ISO-8859-1 has a very limited character range (all ASCII characters plus some western European characters like Umlauts and accented characters). As long as you are using pure ASCII characters that doesn’t make a difference anyway, since for this character range UTF-8 is indistinguishable from ISO-8859-1. For older hardware players you might even need to use ISO-8859-1. Better go with UTF-8, it is better supported by software (btw, this is not only true for music metadata) and just like UTF-16 allows you to make use of the Unicode characters for international scripts. I really cannot recommend using UTF-16 for most use cases. It is also likely mostly luck you see the other characters correctly, if you would use anything outside of ASCII characters I bet your player would fail rendering this character properly and display some garbage. What you see as weird characters in front of the artist names is the so called BOM (Byte Order Mark), which is mandatory for UTF-16 and indicates in which order the bytes that make up each character should be interpreted. Use ISO-8859-1 only if UTF-8 does not work. TL DR: Change you Picard settings to use either UTF-8 or ISO-8859-1 for ID3v2 Text Encoding. I took a look at this file, and this clearly shows the data is encoded using UTF-16. That way you can downgrade the tagging for the albums as they get transferred to the player, but keep your main music library properly tagged.ĭo a few experiments to see what your player likes the most. And then make that temporary staging area to COPY albums to. ![]() (For example - deleting ALL comments)Īlso note how I am suggesting you keep your main library fully tagged up with Picard. It is also easy to load up dozens of albums and then just delete whole chunks of data in one go. Why do I keep pointing to MP3TAG? Well, you can use that to set a different profile in there following this older standard. Now move these albums to the SanDisk player and see how they behave. ![]() And set then in plain old ASCII (ISO 8859-1). Use MP3TAG to strip the tags down to a more basic set. Updating the firmware will help get you any bug fixes too. I would clear out the player, format, then start clean. Once they have something working it gets shipped. Kit like this doesn’t get much testing at the factory. That may explain why a few songs didn’t display correctly before all this.įrom looking around those SanDisk forums I think your MP3 player is like many of these kinds of products. Thanks for all the research! I didn’t know my MP3 was so out of the loop. (MP3TAG is quick good at that kind of bulk editing) And then when I want to put music on the SanDisk I’d copy the albums to a temporary set of folders first and downgrade the tags to make them more compatible with the player’s needs. So, if I was you, I’d keep my main music collection fully tagged up with Picard using the most up to date tags. ![]() This format is the most compatible with Sansas. Whatever tag editor you use, change the settings to save tags in ID3 v2.-1 format if possible. The best thing to do is to use a program like MP3Tag (highly recommended, and FREE) to clean up the tags, deleting comments and paring down the other tags to only the essentials. For some reason, some people try to put the artist’s entire history (or some other ridiculously verbose nonsense) in the “Comment” tag. The player can choke on messy tags, particularly very long comments. More about tags: when it says “refreshing your media”, what it’s really doing is building a database of all the information in the tags (title, artist, album, track number, etc.). I expect it will be the same with your player. Someone in the forums said that the SanDisk Sansa is “ most compatible with ID3v2 v2.3 ISO-8859-1 tags”. Either Windows Media Player editing the tags, or just right clicking on the files in the OS and editing them.Īh - bingo. It is also very noticeable that in the SanDisk help files everything is showing just default\basic Windows methods. (No idea why the player should be editing the files - probably a bug) There are plenty of other references to corrupting tags on the player. Though that thread didn’t say if it worked. Interesting idea there - setting the music files to read-only before they are copied onto the player.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |