Re: [Musicpd-dev-team] Database backend

2009-07-11 Thread Stefan Monnier
Asking mpd to do an 'update' on its music directory has never completed for me - on an NFS-mounted 100GB+ music library. This points to a real problem that needs to be fixed. My library is about the same size, tho it likely has far fewer files (I keep it all in Flac format), but I've never had

Re: [Musicpd-dev-team] Database backend

2009-07-02 Thread Jonny
Thanks for the suggestions all. Rasmus: A full database update on my setup seems to take forever (literally: I've left it running for 3 or 4 days before). J. Alexander Treuman: Yes I've thought in the past of doing something like your suggestion, using symlinks. I also have an 'unsorted'

Re: [Musicpd-dev-team] Database backend

2009-07-02 Thread Rasmus Steinke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonny wrote: Thanks for the suggestions all. Rasmus: A full database update on my setup seems to take forever (literally: I've left it running for 3 or 4 days before). hmm.. i am not sure what you are doing wrong then... an UPDATE should only

Re: [Musicpd-dev-team] Database backend

2009-07-02 Thread Jonny
hmm.. i am not sure what you are doing wrong then... an UPDATE should only apply CHANGES to the database. this measn if you have removed 2 folders, only 2 folders will be removed, the rest stays as it is. 30k songs here, but NFS mounted, which is almost certainly the reason. Plus there are a

Re: [Musicpd-dev-team] Database backend

2009-07-01 Thread Jonny
Max once thought about using SQLite as backend. He even was clear that, if done right, there shouldnt be ANY regression in speed. Not sure what the plans are for now. I guess there are more important things :) Fair enough. :) In the meantime, is there any way of selectively removing

Re: [Musicpd-dev-team] Database backend

2009-07-01 Thread Jeffrey Middleton
I agree that it's sometimes awkward that the update is modification time based - for example, if you add replaygain tags to your whole library you don't really want it all to end up with the same modification date. Perhaps it's worth looking into adding a feature there, since something a lot

Re: [Musicpd-dev-team] Database backend

2009-07-01 Thread J. Alexander Treuman
On Wed, Jul 01, 2009 at 09:31:43AM -0500, Jeffrey Middleton wrote: if you add replaygain tags to your whole library you don't really want it all to end up with the same modification date. Why not? If all files were modified at the same time, they should all have the same modification time.

Re: [Musicpd-dev-team] Database backend

2009-07-01 Thread Rasmus Steinke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Why dont you just move the files to a non-mpd directory and do a database update? Jonny wrote: Max once thought about using SQLite as backend. He even was clear that, if done right, there shouldnt be ANY regression in speed. Not sure what the

[Musicpd-dev-team] Database backend

2009-06-29 Thread Jonny
I know that people have asked why MPD doesn't use an SQL database in the past, and I know also that the reason has been performance. I'm not disputing this, and I don't want to start any kind of flame war, but aside from performance the use of SQL does allow for more features (or for making such

Re: [Musicpd-dev-team] Database backend

2009-06-29 Thread Rasmus Steinke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Max once thought about using SQLite as backend. He even was clear that, if done right, there shouldnt be ANY regression in speed. Not sure what the plans are for now. I guess there are more important things :) Regards, Rasi Jonny wrote: I know that