Unicode and WAV Tags

This forum is for reporting bugs in MediaMonkey for Windows 4. Note that version 4 is no longer actively maintained as it has been replaced by version 5.

Moderator: Gurus

bullmoon
Posts: 6
Joined: Mon Jul 10, 2006 9:00 pm
Location: ATL
Contact:

Unicode and WAV Tags

Post by bullmoon »

Media Monkey version 3.2.0.1294
Window7 Ultimate x64
Tagging Options Set to ID3v1 and v2, ASCII+UTF-16 - although I have tried other combinations and nothing works.

Problem 1: Tags written to WAV files don't seem to be using Unicode.

Here is an Example:
File Folder Name is Blue Öyster Cult, however, when written to the File as Artist (tag from filename), and inspected using dBPowerAmp, they show up as Blue Öyster Cult.

Many Latin Artists have similar problems. I don't think I had this problem until version 3.x.

I can manually repair these Tags with dBPowerAmp and re-write them and all is well - although any work done like this can be potentially broken by doing any Tag updates with Media Monkey.

Problem 2: Tags are not written to WAV files so that other applications can read them any longer. For example Windows Media Player and Windows no longer see Tags written to WAV files. I can Batch convert the Tags in dBPowerAamp (it somehow sees them) and rewrite them, but I get the non-unicode character set issue above.

I have been using MM for a long time to manage my WAV file for Audiotron playback - I have not had any WAV file Tag issues until lately (v 3.x I am fairly sure).

Thank you,

Steve
steve powell
Peke
Posts: 18655
Joined: Tue Jun 10, 2003 7:21 pm
Location: Earth
Contact:

Re: Unicode and WAV Tags

Post by Peke »

If you want to force ASCII in WAV Tags instead of UTF8 add these lines to Mediamonkey.ini:
----
[WAVTagging]
ReadWriteUTF8=0
----

NOTE: (Unicode is non Standard due the fact that all RIFF LISTINFO Tags are Zero terminated and Unicode is Zero Filled due UTF-16 standard and its implementations are breaking of initial standard. Althru like you said some apps use it. That issue is main reason why WAVELIST format is added/used in some WMP x64 but still not wide spread as standard across apps and platforms.
Best regards,
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
Image
Image
Image
How to attach PICTURE/SCREENSHOTS to forum posts
bullmoon
Posts: 6
Joined: Mon Jul 10, 2006 9:00 pm
Location: ATL
Contact:

Re: Unicode and WAV Tags

Post by bullmoon »

Thank you so much.

The .ini entries fixed the Character problems in the Tags. However, Explorer still cannot see the Tagged info in the files (so neither does my XBOX/Media Center Extender). In fact, if I use MM to re-TAG a WAV file, any TAG information that Explorer can see no longer is seen.

I can use dBPoweramp to batch update the WAV files - somehow it reads the MM tag info from the WAV files, and then rewrites it so that Explorer/Windows sees it. I can use this combo of tools to manage my library, although it would be really cool if MM would write the WAV tags the same way dBPA does so I would only need one tool.

Or could you recommend an alternative lossless format that is compatible with both Windows Media Center/XBox as well as iPod that supports relatively easy Tag management? WMA is no good for iPod. Not sure how well Apple Lossless works with Media Center if at all. I'd rather use something a bit less tied to either Microsoft or Apple if possible.

Thanks again.
Peke wrote:If you want to force ASCII in WAV Tags instead of UTF8 add these lines to Mediamonkey.ini:
----
[WAVTagging]
ReadWriteUTF8=0
----

NOTE: (Unicode is non Standard due the fact that all RIFF LISTINFO Tags are Zero terminated and Unicode is Zero Filled due UTF-16 standard and its implementations are breaking of initial standard. Althru like you said some apps use it. That issue is main reason why WAVELIST format is added/used in some WMP x64 but still not wide spread as standard across apps and platforms.
steve powell
vokimon

Re: Unicode and WAV Tags

Post by vokimon »

Utf8, plays well with zero terminated strings and supports any unicode character.
Post Reply