Phil Meyer;223767 Wrote: > I tried to do an Export to iTunes. Doesn't look like the "Path to > iTunes Music (export)" is working; I looked in the generated .txt file, > and saw that all of the paths to the music files are still pointing to > the SlimServer path. The path replacing logic should work this way: - If the track path in SlimServer begins with the path entered as "Music Folder" in "Server Settings" in SlimServer, it will be replaced with the path entered in "Path to iTunes Music (export)". - If no "Music Folder" path has been specific in "Server Settings" and the track path in SlimServer begins with the path entered as "Path to iTunes Music (import)", it will be replaced with the path entered in "Path to iTunes Music (export)". - Else no path conversion will be done besides the extension.
I guess the second point probably is the reason why it doesn't work in your case ? If this is the case I think I've changed it in the next TrackStat release not available yet. If a track matches the "Path to iTunes Music (import)" in the next release, it will result in path conversion. Phil Meyer;223767 Wrote: > I notice that there are some occasional weird characters in the .txt > file too. I think I may have some filenames containing accented > characters (I don't normally put any non-ascii chars in filenames, I > will probably change these), so maybe there's some problem with > unicode/UTF8.It might be, but I know it is working for me as I have Swedish characters in some of my paths. But there could still be some problem related to this. The character encoding stuff tends to get complicated and a lot of different situations exists. Phil Meyer;223767 Wrote: > It would be good to be able to run "Export to iTunes" on a specific > subset (essentially a configured mulit-library), rather than the whole > library. I can parse the .txt file through grep to remove unnecessary > export entries as an optimisation though.I'll add it to the wish list for a > future TrackStat release. Phil Meyer;223767 Wrote: > I see some files do some wildcard search and there are thousands of > possible hits. After iterating through thousands of lines, it says > track found and goes onto next. Perhaps the perl script could be > configured to only log errors and warnings (tracks that are not found)?There > is a ITUNES_DEBUG=1 flag in the beginning of the script, if you change this to 0 it should disable the logging. The default value should probably be changed to 0. -- erland Erland Isaksson 'My homepage' (http://erland.homeip.net) 'My download page' (http://erland.homeip.net/download) (Developer of 'TrackStat, SQLPlayList, DynamicPlayList, Custom Browse, Custom Scan, Custom Skip, Multi Library and RandomPlayList plugins' (http://wiki.erland.homeip.net/index.php/Category:SlimServer)) ------------------------------------------------------------------------ erland's Profile: http://forums.slimdevices.com/member.php?userid=3124 View this thread: http://forums.slimdevices.com/showthread.php?t=37986 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
