cpd73 wrote: 
> I am by no means an expert (I'll leave that to Roland0)... but, is it my
> "musly-server" that is crashing? If so I'll look into having it commit
> every (e.g.) 500 tracks. I have scanned ~20k tracks without an issue -
> but again this was on an i7 laptop.

I happened during scanning. When I searched the internet for this
failure messages, it was obvious that there were too many changes to the
database not committed, which caused a corruption of the database (tried
multiple times). Therefore my unconventional approach to split my music
directory, scan the first part of it, and then copy the rest back to the
original locaton and rescan (incremental). This approach worked.


------------------------------------------------------------------------
frankd's Profile: http://forums.slimdevices.com/member.php?userid=52885
View this thread: http://forums.slimdevices.com/showthread.php?t=114191

_______________________________________________
plugins mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/plugins

Reply via email to