The only problem with not syncing (or making songs »mixable«) is that the MusicIP gives you back everything with UTF-8 encoding, so all file paths are -also- UTF-8. Which is in principle a Good Thing because it allows foreign characters.
Theres just the drawback that the filenames SC reads -from the disc- (via »Music Folder«) dont match up with what MusicIP encodes. Let me demonstrate: SC »sees« on the local (Windows) disc a file called: M:\MP3\MUSIC\D\DIE ÄRZTE\DIE ÄRZTE - ROCK'N'ROLL ÜBERMENSCH.MP3 -(This can be encoded either in a Windows »codepage«, i.e. CP-1252, or Unicode (UTF-16), depending on which filesystem you use.)- Now SC wants to see if the file is »mixable« and tries to compare the string with whatever it got from the MusicIP API. Which is encoded UTF-8 and looks like this: M:\MP3\MUSIC\D\DIE ÃRZTE\DIE ÃRZTE - ROCK'N'ROLL ÃBERMENSCH.MP3 Match? -No- match. Presto! Not mixable. I dont know what »base« character set SC and the database use internally but whats needed is clearly to convert BOTH inputs (filesystem where we scan -and- response from foreign HTTP*API) into the -same- internal character set and we can -successfully- match this same file. All problems solved. PLUS faster scanning. -- Moonbase Moonbase: 'The Problem Solver' (http://www.kaufen-ist-toll.de/moonbase) ------------------------------------------------------------------------ Moonbase's Profile: http://forums.slimdevices.com/member.php?userid=21594 View this thread: http://forums.slimdevices.com/showthread.php?t=55833
_______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/ripping
