use file modification as import date

[anarcat]

When supysonic does its original scan, all files have the same timestamp: when the file was originally scanned. This is fine for later scans, but it would be great if supysonic would recognize file modification dates when doing its first mass scan and use that as the creation date in the database.

This would not need to be a special case for the original scan either: incremental scans could use the file modification dates as well, as it is likely they are close to the scan dates as the files will have been created at the right time...

Thanks!

[spl0k]

Is this for the "recently added" listing on clients or is there another use case where this bothers you?

[anarcat]

Is this for the "recently added" listing on clients

Yes.

I was actually thinking of looking at the database and just hacking that straight in there, but I wonder if it might be a good thing to have on import anyways...

[spl0k]

It should now use the modification date when scanning the first time.
If you don't want to recreate your whole library you can update values directly in the database: on the table track change the column created to a something matching column last_modification (the former is a datetime while the latter is a timestamp). Unfortunately that can't be done for folders.

[anarcat]

wow thanks! this works great!