Corrupt timestamps tool doesn't work

[kaatinthehaat]

Hi Abu.

I have found a problem with the "fix corrupt timestamps" tool. Recently, I bought a new computer and uploaded all my music from my iPod onto it and created a new ML in winamp. I noticed that for some reason all (>3000) the datestamps in the Winamp ML from this action were "06/02/2106 10:28:15 PM". The date is set correctly in my ipod and on my PC.

So I ran the "Fix corrupt timestamps" tool and a message said that 29 datestamps were fixed. But there are still >3000 songs with last played dates in the year 2106.

The date does change once a song is played but I have found that syncing my ipod again seems to mess up some of the dates again. Interestingly, the corresponding last played datestamps in the ipod ML are blank.

I thought this tool was supposed to correct future dates. It wouldn't matter that much but it is messing up a lot of my smart playlists which are date sensitive.

Also, a message saying which songs had been corrected would be helpful to figure out what is going on.

Thanks again for all your help on this otherwise fantastic plugin.

[abu]

Wow, Kaat,
you've find every problem that might be possible...!

Actually we have a change in Winamp again, which leads to this problem. "06/02/2106 10:28:15 PM" is the date that represents the numerical value "-1" in the timestamp. And "-1" is what ml_iPod writes for invalid fields. Winamp 5.2x did not display these fields, -1 was treated as a special value. Obviousely 5.32 handles this differently.

The problem is: The Winamp API gives no way to remove an invalid timestamp from the ML. It only gives possibility to change it to another value. -1 used to be a good value, but it's not any more. I'm lost. I don't know what to do, Winamp just does not let me do the right thing...

[kaatinthehaat]

If a problem with any software or hardware can happen it usually happens to me, LOL. Well at least I'm not going insane which is what I originally thought before I noticed the invalid timestamps.

A workaround may be just to play everything in winamp to allow natural resetting of the datestamp to a valid number. Winamp sets the datestamp after the first second of playing if I'm not mistaken so I could just skip through my library periodically. I'll just have to ignore the weird dates for now.

Another option, I suppose, would be to go back to Winamp 5.2x and fix the timestamps with your tool and then reinstall winamp 5.32 but I think that may be asking for more trouble than it's worth.

Thanks for looking into this, Abu. It's much appreciated.

[Stupifier]

Nice freakin iPod there Kaat! Sorry, I don't anything else to contribute LOL. 80GB 6th Gen....I will definately need the storage increase when the next iPod comes out. I'm using the 5th gen 60GB right now. Just waiting for the 100GB or something. Maybe 7th Gen

[abu]

Hi Kaat,
I think (or better: hope) I found a workaround. Try 2.00p22, and do the FixCorruptTimestamps again.

The fixed files are listed in the main debuglog (but only until the next Winamp start, then it gets overwritten. So copy it if you are interested in the list)

[kaatinthehaat]

Thanks Abu. I'll try it right now and get back to you....

[kaatinthehaat]

Unfortunately Winamp crashes during the process. A message appears saying "Checking song #### of 3904" #### being a counter. #### gets to "1080" then winamp crashes. Crash occurs at the same point each time. I tried to attach the debug log but even zipped it was too big.

[abu]

Crash? Bad!
I can't see any evidence for that, so I put together a special debug version 2.00p23. Please try that, and then send the debuglog (only the main debuglog is needed). If it is too big, simply send the last 1000 lines of debuglog.txt(after the crash happened). Hope that can help me.

After that, try the 2.00p24. Still crashing? Again, the main debuglog would help (even if it does not crash now)

[kaatinthehaat]

Thanks Abu.

Version 2.00p23 gives same crash at song #1080. See attached buglog.

[kaatinthehaat]

Version 2.00p24 causes no crash but says "0 files altered" and timestamps still say year 2106. See attached buglog.

I'll be interested to hear what you discover.

[abu]

Thanks! I've got an idea what the problem could be. One more try where I would like to see the debug log: 2.00p25

[kaatinthehaat]

Here's the debug log for p25. It's in 2 parts due to size. Crash occurs consistently at song 2553.

[kaatinthehaat]

part 2.

[kaatinthehaat]

BTW, I noticed you have posted another patch, p26. I tried it and still get a crash at song 2553.

[abu]

Ok, so we passed the problem with song 1080. This was a Winamp bug that I reported for 5.23 already, but it has not been fixed. ML items with a "Unique Track ID" (TUID2) can not be written properly without crash.
I worked around this, and song 1080 really has a TUID2 (as I can see in the debuglog).

Song 2553 must have a different prolem. Maybe it's another Winamp bug, I don't know yet. Hard to find!

Could you zip your whole plugins\ml folder and upload it to some webspace (see FAQ for free filespace)? Then I might be able to reproduce this here, would make things easier.