INTERACT FORUM
More => Old Versions => Media Center 11 (Development Ended) => Topic started by: alexgit on January 11, 2005, 01:50:07 am
-
I am having the following problem.
I run MC11 (11.0.168) on server and on client machines. I have lots of tracks in library that have filenames and ID3 tags in Russian.
While they appear perfectly correct in Media Library, I can't play them.
Library Server reports something like that:
01/10/05 23:43:20 - Received request for a file: C:\Music\840 548I520\>;>B0O :>;;5:F8O @5B@>\07 - 5 @>48AL :@0A82>9.mp3
It suggests that Unicode is misinterpreted either on client or on server.
Similar problem was in MC10 however it it was resolved by setting appropritate encoding for non-unicode programs in Windows.
-
I'll check this out, though I thought this was working fine.
Can you mail me a filename (to gateley at jriver dot com)?
j
-
Any update? It still happens in 11.0.173
-
Haven't had a chance to work on it yet...
j
-
Could this be the same problem, discussed in the thread "mp3 file problems with mc10" ?
Rolf
-
Did it get fixed in 178? I can't upgrade until its resolved.....
Thanks
-
Not fixed yet. I'll get to it.
j
-
What is the status of the issue? Was it reproduced at least?
Thx
-
Hi Alex,
It's still on my list. I think I know what's happening, so it should be easy to fix once I get to it.
j
-
Does not seem to ever get to the top of the list....
Very unfortunate.
(you can't use it if half of your library screwed, can you?)
-
John, will you fix it by the time product is released?
Thanks
-
I can't reproduce a unicode problem.
Do you have authentication turned on?
Are you using the latest version?
j
-
Hi John,
I used 11.231 against 11.231, Both were fresh installs.
First I had to set my server to use Russian as language for non-unicode programms. Then I build library. (If I don't set language options - library is screwed up and can't be fixed without rebuilding).
At this point I see and I can play those file locally correctly.
Now, when I access this library from client machine - I get the error. Server log shows:
04/05/05 08:55:24 - Received request for cover art: C:/Music/Андрей Миронов/Я выхожу на сцену/01 - Я выхожу на сцену.mp3
04/05/05 08:55:24 - Received request for a file: C:\Music\=4@59 8@>=>2\/ 2KE>6C =0 AF5=C\03 - "0=3> 8>.mp3
04/05/05 08:55:24 - Error sharing file, file not found
Cover art art request shows correct file name but file request is corrupted. (I assume that while you may not speak the language you are still able to see if characters are ok or corrupted).
I use Windows XP Professional SP2 for client and Windows Server 2003 for server (no service pack, but I also tried it with SP1 - same result)
I think the reason is in the client since earlier when (MC10 to MC11 it still worked) I was connecting MC11 to working well MC10 server and was getting exactly the same problem.
My MC10 does not experience that problem in exactly the same set up.
Let me know if you want me to run more tests or provide you with some additional info.
Thanks
Alex
-
John,
Have you reproduced the problem? Do you need more info?
Any chance it gets fixed soon (it's been 3 month after all...)
-
Hi Alex,
Haven't had a chance to look at it yet.
j
-
Hi Alex,
I'm understanding things better. Can you confirm a detail for me:
1) The file name is NOT Unicode, instead it's a Russian character set with 1 byte per character.
(I'm guessing this because your tags are not unicode either).
That's why you had to set the non-unicode option in windows. (I'm guessing).
If you have any files that ARE Unicode, do they work?
j
-
Hi John,
I think my tags are not unicode. However, filenames should be Unicode. They are just normal filesnames on
NTFS system. They display the same way regardless of regional/language setting. In addition the same use case worked ok in MC10 with the same files.
I converted one file tags to unicode (using MC11 - filename to tag) and than file displayed correctly regardless of non-unicode settings but it still didn't go through library server.
Also, in my other post where I put network sniffer data - it is clear that error bytes map to appropriate letters in 04 unicode page with code page byte cut out. It may be coincidently though (I don't remember non unicode mapping) but the fact of missing byte remains.
Please let me know if you want me to run more test or provide more data.
Thanks
Alex
-
Hi Alex,
Try the next build, I think it's fixed. Build should be coming out momentarily...
j
-
It works !!!
Sunshine is back in my life :)
Thank you, John!
-
Yup, great, it also fixes a very related problem that I was having :-)
I can now access all that weird foreign stuff again ;-)
-
Good deal, sorry it took so long - I was always looking in the wrong direction...
j