songlength.txt includes every file in the STIL. I do not plan to write a way to modify the STIL documents. Storing the length in the tag only makes sense if I also offer a means to edit the length in the first place.Ah, makes sense.
I wasn't thinking about writing THE length tag, though- My guess in how this works is that when the file is playback you check its checksum against the database, right? In that case I understand why is that proper length is only displayed when files are played. Loading that on boot would be a bottleneck if there were a lot of songs.
What I was wondering is, to be more exact, if you could make another tag ($SIDLength or something like that) that the plugin checks for upon loading SIDs into playlists, which you could add a menu option to write- either from Songlength.txt or with an user-inputted duration. That should use way less CPU time than checksums, right?