Comment 3 for bug 135942

I can confirm that it doesn't always sort correctly. It sorts tracks under a minute, follow by tracks 10 minutes or over, followed by tracks greater than a minute but less than 10. See the attached image. The problem is it's sorting track length as a string, so 10:35 comes before 9:35, since it just checks the first character. I wrote a quick patch that solves the problem, although there might be a more elegant solution.