Hi Tim,
Could you give me an example of the kind of non-standard text that
definitely seems to cause the problem?
I'll have a look at it.
Thanks for any info!
--
ChrisOwens
--
Christopher Owens
QA Manager
[EMAIL PROTECTED]
(510) 743-1152 x717
ChrisOwens Wrote:
> Hi Tim,
>
> Could you give me an example of the kind of non-standard text that
> definitely seems to cause the problem?
>
> I'll have a look at it.
>
> Thanks for any info!
Cheers, will post log when I get chance, can't get to my machine at the
moment, but KDF is correct i
KDF
I'm pretty sure that it is happening as you descrbibe, I did ask the
same question over on MM at the same time.
For what it's worth the log looks like this.
2006-03-29 13:28:02.0851 Import: Adding task for
cleanupStaleTrackEntries()..
2006-03-29 13:28:02.0874 Import: Starting db garbage col
I believe I have the same problem.
I've never used Music Magic 1.5, I went straight to MusicIP 1.6b2.
I'm using Windows XP with SP2, running SlimServer 6.2.1.
I'm running the MusicMagicService that came with MusicIP (the Slim
Service is set up to be dependant on MusicMagic so it starts in the
rig
The problem has been acknowledged by the MusicIP team on their forums
[Search for Unicode] and they have indicated they are working on a fix
(but experience suggests this may take a while).
--
Siduhe
Siduhe's Profile: http
Siduhe Wrote:
> The problem has been acknowledged by the MusicIP team on their forums
> [Search for Unicode] and they have indicated they are working on a fix
> (but experience suggests this may take a while).
Aha, did'nt spot this, have signed up and hopefully will get to play
with 1.6b3 later.
Yeah I saw that today. I shall have a play with it later, but I don't
think I saw anything regarding fixing unicode character encoding in the
API.
--
chris.mason
chris.mason's Profile: http://forums.slimdevices.com/member
chris.mason Wrote:
> Yeah I saw that today. I shall have a play with it later, but I don't
> think I saw anything regarding fixing unicode character encoding in the
> API.
You're right to pull me up - the comment I was referring to is the
promise to look at UTF-8 coding in ID3 tags.
--
Siduh
Quoting ChrisOwens <[EMAIL PROTECTED]>:
Could you give me an example of the kind of non-standard text that
definitely seems to cause the problem?
I believe that the poster is referring to unicode characters. MusicIP
doesn't appear to use unicode for it's UI, so I exect that the API
fails
Quoting TimM <[EMAIL PROTECTED]>:
Cheers, will post log when I get chance, can't get to my machine at the
moment, but KDF is correct in that basically it's any tag with unicode.
1.5 handles them OK but 1.6 seems to find them and then delete them at
the end of a rescan. So the likes of Sigur Ros
10 matches
Mail list logo
