You may have also shed some light on it. The installation I did this on was not my main one where I'd made the database changes, but a virtual PC installation using the built-in database. What has changed, however, are the composer tags in my music files that I mentioned in my post earlier today (the virtual installation points to the same files as my main install).
Slimserver would therefore see that the file's tags have been changed (the composer tag being blanked) and this would trigger the updates in the database. I can't see any TCMP tags anywhere, so it's looking like this is perhaps related to the composer tag, which brings me back to the problems I detailed at the start of this thread. -- DoomWolf ------------------------------------------------------------------------ DoomWolf's Profile: http://forums.slimdevices.com/member.php?userid=8839 View this thread: http://forums.slimdevices.com/showthread.php?t=37135 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
