It seems SLDB entry for this file is missing! (At least I couldn't find it in Songlengths.txt.)
I've found in HVSC 46:
a201d88d9c2ca0067f9e93202cfc4a30=1:34 1:57 1:02 0:44 0:40 1:07 3:05 1:08 1:09 0:22 1:10 1:21 0:04 0:02(G) 0:01(G) 0:01(G) 0:01(G) 0:18 0:18 0:18 0:18 0:02(G) 0:02(G) 0:01(G) 0:01(G) 0:01(G) 0:01(G) 0:01(G) 0:08 0:02(G) 0:01(G) 0:02(G) 0:01(G) 0:01(G) 0:02(G) 0:02 0:01 0:01 0:16 0:16 0:13 0:15 0:15 0:15 0:01(G) 0:04 0:04 0:01 0:01(G) 0:01(G) 0:01(G) 0:01(G) 0:01(G) 0:02(G) 0:02(G) 0:02(G) 0:01(G)
Right. I took the wrong database.
Anyways, you probably noticed that MD5 fingerprint from the SLDB is different to the one calculated by the plugin. That is probably because of the speed issue you also mention.
sidplay2w displays VBI for 33-44 and CIA for 45-57
I'd say sidplay2w is wrong with this.
Here's why. There are two speed setting interpretations for tunes above subsong 32. First method uses speeds from songs 1-32 for songs 33-64, 65-76, etc. Which means song 33 gets speed of song 1, song 34 gets speed of song 2 and so on. This method was used by the orignal PlaySID. When using the second interpretation, all songs above number 32 get speed of song 32. This method is used with PSID2NG sids unless a flag states the old method should be used. (Actually the first method is a result of a bug in the PlaySID. It was intended to behave like the second method!)
To make this long story short -- all PSID v2 files should use the new method unless it is explicitly specified in the header. The old method should be used also for PSID v1 files. Your file is in PSID2NG format and flags in it's header don't say that the old method is better.
I'd guess that sidplay2w and HVSC's songlength tool aren't completely PSIDv2NG compliant. (This new (correct) speed interpretation was introduced to libsidplay2 in May 2006, while the latest sidplay2w version is from June 2005.)
I know it's a bit off-topic, but I gotta tell you all sidaholics, that one guy recorded the whole HVSC into mp3 on both sidchips..
A great source of reference!
(Timbaland could've waited a bit, with this site composing would've been even easier for him.)