Quoting oiler1fan <[EMAIL PROTECTED]>: > > kdf > > Your help and that of others is valued and appreciated. I have just > reached a threshold of frustration where I don't want to continue any > longer. After two months of struggle I consider I have given it a fair > shot. Please remember, there are those of us that don't know perl or > linux or redhat, how to use the debugging logs or what mtime means. > When I played my vinyl yesterday it still sounded pretty good.....
understandable, but at the same time, it is impossible to fix something that does not happen on a developer's system without those logs. When you first mentioned earlier that the iTunes scan was not handling the disabled tracks properly, I disabled a few tracks and ran a scan. This worked, so I have no idea what the problem is, so cannot fix. If you have refused to spend any more time, then quite simply, I can do nothing more. If you are happy with 6.0.2, that is really great. Honestly, I'm really pleased to hear that. If only everyone had 6.0.2 working perfectly. My apologies for being confusing about mtime. It simply means, modification time. In order to please the users who expressed frustration over what they percieved to be overly long iTunes scan times, the server only deals with tracks that have changed. Since iTunes doesn't seem to consider marking a track disabled as a change, the server can only disable. Unfortunately, I am not actually one of those people with far too much free time. If you do feel like giving the details on your prefs for ignored tracks, and snips of the log, that would be most helpful. Having looked at this a bit over lunch, it looks like the logic maybe backward, 'ignoredisabled' becoming a bit of a double-negative. I'll try a few tests, and will fix it tonight. I realise this is only a small part of the issues you are having, but every little bit helps. -kdf _______________________________________________ Discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
