Michael Herger wrote:
Not while adding (already indexed) tracks to a playlist?
Oops... didn't read that log file that well :-/.
I think you put me on the right track though, that's probably what's
happening, it's doing a full scan of the subtree and only then adds them
to the playlist. It's a nice feature to be able to add files to a folder
and then playing them by clicking on the folder name under 'Music
Folder', but this could work a lot more efficiently if it just looked
for new files. ( a 'find Classical/ -type f' takes 0.2 seconds on my
system.
So this is what should happen IMHO:
- Read the existing tracks under Classical/ from the tracks db
(SELECT..FROM tracks where url like Classical/%' )
- Read the folder tree contents recursively (should be possible in under
a second in my case)
- Check to see if there are any new files that should be added to the
tracks table.
- Add the new files to the tracks table (churn, churn) and delete files
that have disappeared from the tracks table.
- Generate the playlist.
The files on the disk don't change much, so this should speed up
playlist generation hugely in 99% of all cases by eliminating the churning.
Regards,
Peter
_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
