Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[windowsx]

I bought MC17 hoping to update to MC18 when officially launched with Windows 8 but some problems prevented me from upgrading to MC18 because it can't read tag properly from some formats. I use dbpoweramp to convert files with tag information and everything worked fine in Windows 7. I waited for months for issue to be resolved itself but somehow it didn't so I'm posting here hoping dev team will consider this.

I tested MC18 on Windows 8 and found that it'll read any non-English tag as weird characters instead respective languages. It did read quite OK for FLAC/MP3/M4A but not for AIFF/WAV. I haven't tested other formats yet but will report me after further testing.

Does anyone have similar issue like me?

[MrC]

http://yabb.jriver.com/interact/index.php?topic=77630.0

[windowsx]

Ah. Thanks. I tested this on build 120 few days ago and just got back home yesterday. Hope build 122 fixes it all.

[windowsx]

Tested again on Windows 8 with build 122. Not fixed yet for WAV/AIFF but MP3/M4A/FLAC worked fine though

[MrC]

This is the critical step:

    ... pick your files and do Right-click > Library Tools > Update Library (from tags).

Did you do this?

[windowsx]

I did and it didn't work on Windows 8 with build 122. I also did reply in another topic about doing that including clearing library and I also tested dragging new file in playing now. None worked. From what I read in another topic has no mention about Windows 8 at all. Hope this will be fixed soon because I have lots of Japanese songs ripped myself too.

[Matt]

If you have a file that does not import properly, please mail a copy to logs at jriver dot com.

Thanks.

[windowsx]

Where can I find log? If you're referring to in-depth summary, everything shown alright there without problems. There's no error reported during import. It's just tag data from WAV/AIFF couldn't handle non-English ones properly.

[MrC]

Help > Logging.

Turn it on, do your import test, and then go back to logging to Report problem.

[windowsx]

Thank you. I got log file now with some test actions (import library and playing problem files). Going to send log file now.

[Matt]

We're hoping for a file that imports improperly, not a log.

Could you send a WAV file that shows the problem?

Thanks.

[windowsx]

Link sent.

[Matt]

Thanks for the file.

It appears that the strange tag values are baked into the tag.

For example, the name field is the string of bytes:
0
164
211
181
205
186

The first 0 means ISO-8859 (ANSI) encoding and the rest are character codes, which correspond to the string คำตอบ

You will need to correct these files manually.  If they have good filenames, you can do it using Library Tools > Fill Properties From Filename.

Sorry for the trouble.

[windowsx]

But Flac/M4A/MP3 all worked fine. Do you need more format for analysis? Is it fault from app I use? I used PlexTools for ripping as flac and dbpoweramp for conversion. I want to use proper tools to avoid this manual work every single file.

[Matt]

I don't know why the tags contain that data, only that they do.

[windowsx]

But that file worked just fine in Windows 7. What difference between Windows 7 and 8 caused that? I'm going to send FLAC version for further analysis.

[windowsx]

Did you receive FLAC file I sent?

[Matt]

The FLAC file had "คำตอบ" in the name tag and filename.

I'm afraid I don't know any more than I said above.  You should be able to use Media Center to get the values you want in the WAV filenames / tags.

[windowsx]

So FLAC file is alright but conversion app to pass tag data to wav doesn't work properly in Windows 8 but worked fine in Windows 7. Could you give some hints why it shows differently between these two like parts or files it uses from OS?