JJZolx;265992 Wrote: > SlimServer uses the date that a file was last modified for sorting New > Music. Normally, when you move files or copy them from place to place > they maintain the last modified date. When you rip a CD and encode the > file, you're creating it new and the last modified date should be when > you ripped it. > > If at a later date you tag the file using some tagging software, the > last modified timestamp will generally be updated. Some taggers let > you maintain the old timestamp so that when you fix or add new tags to > existing files you can keep them from bubbling to the top of New Music.
I'm really surprised at how bad Slim has implemented this. It's clearly very bad behavior for a piece of software to decide that "modified date" should be interpreted as "added date" when "added date" actually exists for the purpose of specifying the date the track was added to the database. And just for the record, "modified date" is there to tell when a track was - dramatic pause - modified! Does anyone know of an easy way to hack this in the code? (I'm really fed up with old tracks & albums showing up in the "new" list just because I've corrected some tags...) :water -- water http://wa.terhou.se - 'http://werock.org' (http://www.werock.org) - 'http://nunmusic.com' (http://www.nunmusic.com) - 'my last.fm' (http://www.last.fm/user/torandwat/) ------------------------------------------------------------------------ water's Profile: http://forums.slimdevices.com/member.php?userid=119 View this thread: http://forums.slimdevices.com/showthread.php?t=43093 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
